Scope
- The version number and change summary match the build that was tested.
- Each change in the release has a ticket or a linked decision record.
Release sign-off: a written record of what was approved and why
A release sign-off records who checked a release, what they checked, and which known risks they accepted before it went out. The form is a written record of the decision, not the decision itself, so the people who must approve the release still need to be named and must act. Ask each approver about the area they own, and put the rollback steps and the known issues in front of them before they answer.
Working checklist
Check the release before anyone signs off
Testing
- The test run is linked and dated after the last code change.
- Each skipped test is named, with the reason and the person who accepted the gap.
Rollback
- Someone who can run the rollback has confirmed the steps for this release.
- The rollback point is named: a version, a database state or a feature flag.
Customers and support
- Support has the change list and the known-issue list before the rollout starts.
- Customer-facing release notes are drafted or linked from the sign-off.
Known risks
- Each open issue has an owner and a decision: ship with it, hold the release, or fix it first.
Field blueprint
Eleven fields, one record per approver
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Release name or version | Short text | Required | Ties the record to one build. Use the version your deployment tool shows, so the release has one name everywhere. |
Environment this approval coversStagingProductionProduction, staged rollout | Single choice | Required | An approval for staging is not an approval for production. Record which one this response covers. |
Change summary | Long text | Required | What is different for users and for the team. Keep it to changes a reviewer can check against the tickets. |
Link to the test resultsPaste a link to the test run. Attachments cannot be added here. https:// | Short text | Required | The evidence the approver relied on. A link to the test run is more useful than a summary of it. |
Tests skipped or not run | Long text | Optional | Gaps are normal. Listing them is how a reviewer learns where the risk sits. |
Known issues accepted for this release | Long text | Optional | Each accepted issue needs a name beside it, so the risk has an owner after the release goes out. |
Rollback stepsTested on this releaseDocumented but not testedNo rollback plan yet | Single choice | Required | A rollback that was never tried is a plan, not a control. The record should say which of these is true. |
Area this approval coversEngineeringQuality assuranceProductSupportSecurityOther | Dropdown | Required | An approval from one area does not cover the others. Engineering, quality and support each answer for their own part. |
DecisionApproveApprove with conditionsHold | Single choice | Required | The outcome in one choice. Conditions go in the next field, so they are not lost in a comment. |
Conditions or notes | Long text | Optional | Anything that must happen before or after release, with the name of the person who will do it. |
Approver's full name | Short text | Required | Records who submitted this response. The form has no e-signature field, so the name is a record, not a signature. |
At a glance
What one approver needs to complete
11Fields
8Required fields
6Estimated time (minutes)
Estimate based on question types; actual completion time varies.
A filled example
A completed sign-off for a web app release (fictional)
Example only, not a real submission
- Release
- Version 4.8.0, production, staged rollout starting with 10 percent of accounts
- Change summary
- Adds CSV export to the reports page and fixes a timeout on invoice search.
- Test results
- https://example.com/test-runs/4.8.0 (run dated 2026-10-14, after the last code change)
- Tests not run
- Mobile Safari export was not tested. The reports page was checked on Chrome and Firefox only. Owner: Priya.
- Known issues accepted
- Exporting more than 50,000 rows is slow. Product accepted it for 4.8.1. Owner: Luis.
- Rollback steps
- Tested on this release. Redeploy 4.7.3 and clear the cache. Verified in staging on 2026-10-15.
- Area
- Quality assurance
- Decision
- Approve with conditions
- Conditions
- Support receives the known-issue list before the rollout starts. Priya confirms the Safari test by 2026-10-17.
- Approver
- Dana Ruiz
Try it
Try the sign-off as an approver would
Read the results
Read the sign-offs as a set
Look for the approvals that are missing
A release with only an engineering approval is incomplete if support or product has not answered. Compare the areas that responded with the list agreed for this release before you read the decisions themselves.
Treat a conditional approval as an open item
Approve with conditions means the release is not finished until each condition has an owner and a date. Track each condition to closure, or it stays a note that nobody checks.
Read the rollback answer first
If the rollback was documented but never tested, decide whether the release waits. An untested plan is a risk the approver should name in the notes, not a detail to skip past.
Keep the record after the release closes
Export the responses to CSV when the release closes, and store the file where your audit or incident review team can find it. The question in a later review is what was known at the time, and the record should answer it.
Frequently asked questions
Is a release sign-off the same as an e-signature?
No. The form has no e-signature field, and a typed name shows who answered, not a legal signature. If your policy requires signed approvals, use the signing process your company already has, and link to the signed record from the sign-off.
Is there a release sign-off template I can download?
The checks and fields are the template here, and they are not a Word or PDF file. Each approver answers on a web page reached through a link, and the responses stay in the form for export.
Does the form approve the release automatically?
No. The form records each response, and its creator hears about it after the hourly processing run in production. It does not start a deployment, block one, or wait until everyone has answered. Confirm the go or no-go in your deployment tool or team channel at the moment of decision.
What should happen when an approver chooses hold?
Hold is a decision, not a failure of the process. Record the reason in the notes, name the person who decides when the release reopens, and set the next review in your own calendar, because the form does not send follow-ups.
Browse by category
More checklists in Product & Engineering
Surveys
Sprint Retrospective
Surveys
Third-Party Vendor Evaluation
Applications
User Research Screener
Requests
API Access Request
Requests
Architecture Review Request
Applications
Beta Tester Signup
How to build it
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.
