# Production Deploy

> A safe deploy process with pre-flight checks, a clear rollback path, and post-deploy verification so shipping is routine, not risky.

**Category:** Product & Engineering

**When to use:** Whenever code goes to production.

**Trigger:** A change is approved and ready to ship

## Steps

1. Confirm the change is merged, tests are green, and any migration is reviewed.
2. Announce the deploy in the team channel with what is shipping and the rollback plan.
3. Run any database migration in the correct order relative to the code.
4. Deploy, then watch logs and error rates through the first few minutes.
5. Run a quick smoke check on the critical path the change touched.
6. Confirm healthy and post the result; if not, roll back immediately and investigate after.

## Outputs

- A shipped change with a recorded rollback plan
- A post-deploy smoke-check result
- A deploy confirmation posted to the team

## Tools

- CI/CD
- Logs / monitoring
- Version control

## Notes

Decide the rollback path before you deploy, not during an incident. A deploy with no known rollback is a bet, not a release.

---

Free SOP from the OrgTP Process Library — https://orgtp.com/process-templates/production-deploy
Run it live with your humans and AI agents at https://orgtp.com.