Define the launch gate
Start with the approved release checklist, target time, scope, and the person who owns the decision. Include the evidence required for each gate. "Testing complete" is weaker than a named check with a result and timestamp.
If launch criteria differ by release type, supply the right version. Nema should not borrow a lighter checklist from a small update for a change with broader risk.
Match status to evidence
Ask Nema to compare owner updates with the linked records. A completed task should show what was checked, by whom when available, and when. A verbal assurance can remain an update, but it should not be converted into documentary proof.
Conflicting statuses belong in the open section. When a tracker says complete and an engineer reports a failed retry, both should remain visible until the owner resolves them.
Focus on decision-changing gaps
Group open items by their effect on the launch: required gate, accepted follow-up, or unresolved scope question. Name the owner and deadline only when confirmed. Show dependency chains so the release owner can see which single issue blocks several checks.
The packet can include options the owner has already defined, such as holding the launch or removing a feature from scope. Nema should not invent a risk tolerance or approve an exception.
Record the human decision
Review the packet in the launch Slack channel. Specialists correct their evidence, and the release owner records go, hold, or a scoped alternative with the reason. Nema can summarize that choice and its conditions for the team.
This workflow prepares and records coordination. It does not deploy code, change production, or declare safety on behalf of the accountable owners.
Rehearse with a past release
Use a completed launch to see whether the packet would have exposed the issues that mattered. Verify every status and timestamp. Refine the gate definitions before using the workflow for a live decision.
Questions from product teams
Does a green checklist mean we should launch?
It means the supplied gates appear satisfied. The release owner still weighs context and makes the decision.
What if an owner cannot confirm in time?
Keep the gate unresolved and show the affected scope. The owner decides whether to hold or change the launch plan.
Can Nema deploy the release?
No deployment is part of this workflow. Nema prepares the review and captures the authorized decision.