Change Request
Infrastructure and application changes need formal documentation for change advisory boards. This template captures the change description, business justification, affected systems, risk level, implementation window, rollback plan, and approvers needed, turning a Slack message into a proper change request record.
See it in action
What users type
What you get
Maria Santos
Postgres RDS instance upgrade (db.r6g.xlarge to db.r6g.2xlarge)
Migrate primary Postgres database from RDS db.r6g.xlarge to db.r6g.2xlarge with approximately 6 minutes downtime during failover
85% CPU utilisation during peak hours with increasing query latency
Main API, analytics pipeline, webhook processor
Medium
Saturday April 12th, 2:00-4:00am ET
Fail back to old instance within 10 minutes; old instance kept warm for 24 hours
Extracted fields
| Field | Type | Required |
|---|---|---|
| Requester | text | Required |
| Change Title | text | Required |
| Change Description | text | Required |
| Business Justification | text | Required |
| Affected Systems | text | Required |
| Risk Level | select | Required |
| Implementation Window | text | Required |
| Rollback Plan | text | Optional |
Use this template
Sign up and select “Change Request” from the template gallery. Customise any field before going live.
Start with this template — freeRelated
Templates
Parse bug reports from users or QA into structured tickets with reproduction steps and severity.
Incident PostmortemStructure incident postmortem narratives into timeline, root cause, impact, and action items.
Deployment RequestParse deployment requests capturing version, environment, dependencies, and approval status.