Before the window
- Identify the code revision and tested build output.
- Record required runtime and configuration differences.
- List data steps, background services and scheduled work.
- Name the authorized release and stop decision owners.
Release preparation
What needs to be clear before the change goes live?
Use this list to agree on a particular release. It does not inspect the application or authorize production commands.
Faith Forge Labs ยท Reviewed October 16, 2026
Acceptance checks
- A representative customer or staff task reaches the expected saved result.
- Relevant permissions and invalid inputs are checked.
- Background work runs under the intended release.
- External failures are tested with controlled substitutes, without unintended messages or charges.
Recovery
- Write down the condition that stops the release.
- Rehearse the relevant recovery away from production.
- Explain what happens to new records after a data change.
- Confirm who can make the recovery decision.
After release
- Keep the actual release identity and check results together.
- Review relevant application errors and background failures.
- Record remaining gaps and follow-up responsibility.
- Update the operating instructions with the steps that were verified.