The deployment is not the end of a change. It is the moment when a change begins interacting with live permissions, data volumes, integrations, and real people.
A useful checklist should be short enough to complete, but concrete enough to catch the issues that unit tests cannot see.
Before deployment
- Confirm the target org, release window, approver, and rollback owner.
- Review permission sets, record types, page layouts, flows, Apex jobs, and integration credentials—not only the metadata in the deployment package.
- Identify any data migration, backfill, or feature-flag step and rehearse it in a representative environment.
Immediately after deployment
Verify one happy-path user flow with the intended permission set. Then check debug/error monitoring, queue depth, scheduled jobs, and the receiving system for any changed integration. A deployment that succeeds technically can still leave a user unable to see a field or a downstream system unable to parse a message.
Decide when to roll back
Write the rollback threshold before the release starts. For example: an authentication failure affecting a critical integration, an irreversible data corruption risk, or a broken primary user journey. This prevents a stressful discussion from becoming the decision process.
The checklist is not bureaucracy. It is a compact record of what the team has learned is expensive to forget.