Rollback plan exists

Every production deployment carries the risk of introducing a regression. Without a documented rollback mechanism, a bad deploy becomes a multi-hour incident requiring manual intervention with no defined process. NIST CSF 2.0 RC.RP (Recovery Plan Execution) and ISO 27001:2022 A.5.29 both treat recovery procedures as mandatory controls. The operational reality: Vercel instant rollback takes 30 seconds and requires no technical expertise; discovering you have no rollback path during a production incident adds panic on top of an already stressful situation.

Confirm the hosting platform supports instant rollback (Vercel, Netlify, Fly.io all do) and document the procedure. Tag the pre-launch commit for a clear recovery reference point.

# Vercel — instant rollback via CLI
vercel rollback

# Or from the Vercel dashboard: Deployments > previous deploy > Promote to Production

# Tag the pre-launch state in git
git tag v1.0.0 && git push origin v1.0.0

For projects with database migrations, rollback is more complex: a code revert does not revert schema changes. Verify your migration tool supports migrate down (Prisma does with some caveats), and test the rollback path on staging before launch. Add a 5-line rollback note to your README — even "go to Vercel dashboard > previous deploy > Promote" is enough to prevent a panic.