Process Library

Production Deploy

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

Product & Engineering 6 steps
When to use

Whenever code goes to production.

Trigger
Runs when: A change is approved and ready to ship

The procedure

6 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/CDLogs / monitoringVersion control
Note: Decide the rollback path before you deploy, not during an incident. A deploy with no known rollback is a bet, not a release.
Download .md

Use this SOP in OrgTP

Don't just download it. Drop this SOP onto a seat in OrgTP and every AI agent under that seat inherits and runs it at runtime — with the trigger, steps, outputs, and tools already filled in.

Use in OTP → Browse more SOPs
Related searches
deploy sop release process production deployment checklist ci cd process rollback plan

Related SOPs

Product & Engineering
Code Review
6 steps
Product & Engineering
Bug Triage
6 steps
Product & Engineering
Sprint Planning
6 steps
Product & Engineering
Feature Spec
6 steps
← Back to the Process Library