Technical Deployment Plan

Release / version: [Version or build identifier] Service / system: [What is being deployed] Owner: [Name, role] On-call: [Name, contact] Planned window: [Date and time, with timezone] Expected duration: [e.g. 30 minutes]

---

1. Overview

[In 2-3 sentences: what is being deployed, why now, and the headline risk. Note the chosen release strategy (rolling, blue-green, or canary) and why it fits this change.]

2. Environments

[State which environments the change has cleared and what was verified in each.]

Environment	Status	Verified
Local / dev	[Done]	[What was checked]
Staging / pre-prod	[Done]	[What was checked against prod-like data]
Production	[Target]	[To be verified post-deploy]

3. Pre-deploy checklist

• Exact version / commit identified and passing CI
• Verified in staging against production-like data
• Migrations reviewed, ordered, and reversible where possible
• Config, secrets, and feature flags in place for the target
• Backup or restore point taken
• Rollback procedure written and read
• Window agreed and stakeholders notified
• Owner and on-call available for the full window

4. Deploy sequence

[The ordered steps. Each row is one action, with the person responsible and an estimate.]

Step	Action	Owner	Time
1	[e.g. Announce start of window]	[Name]	[T+0]
2	[e.g. Run database migration]	[Name]	[T+5]
3	[e.g. Deploy new version to green]	[Name]	[T+10]
4	[e.g. Flip traffic / ramp canary]	[Name]	[T+20]
5	[e.g. Run verification checks]	[Name]	[T+25]

5. Rollback plan

Trigger: [The specific condition that means abort, e.g. error rate above 2% for 5 minutes.]

Steps to revert:

1. [First revert action]
2. [Second revert action]
3. [Any data clean-up the revert requires]

Notes: [Irreversible steps, data risks, and who must authorise a rollback.]

6. Post-deploy verification

[The specific signals that prove the release worked. Define healthy in numbers.]

• [Health endpoint returns success]
• [Key user journey completes end to end]
• [Error rate at or below baseline]
• [Latency within target]
• [Relevant business metric behaving as expected]

7. Communication plan

When	Message	Audience	Channel
Before window	[Deploy starting]	[Team / stakeholders]	[Channel]
On completion	[Deploy done, verified]	[Team / stakeholders]	[Channel]
If rollback	[Reverted, impact, next steps]	[Team / stakeholders]	[Channel]

8. Owners and timing

• Deploy owner: [Name] — runs the sequence and makes the go / no-go call.
• Rollback authority: [Name] — decides whether to abort.
• On-call: [Name] — monitors verification signals after cutover.
• Window: [Start] to [End], [timezone]. Hard stop at [time] if not complete.