Close deficiencies and issue an accepted handover manifest
Keep accountable corrective work, independent closure verification and mandatory readiness decisions separate from test completion counts.
Current Revision 3 Reviewed Oct 26, 2026
On this page
Before you beginCurrent capability and authorityClearly labeled synthetic exampleInputs and terminologyProcedureVerify the resultWhat happens nextTroubleshootingBefore you begin#
- Commissioning capabilities appropriate to recording, verification and designated acceptance.
- Published plans, exact evidence, prerequisite delivery stages and authorized acceptance owners.
Current capability and authority#
Keep accountable corrective work, independent closure verification and mandatory readiness decisions separate from test completion counts.
Clearly labeled synthetic example#
Synthetic acceptance gate HG-01 remains incomplete with nine of ten valid required tests. Its missing tenth test has an owner and action; no 90%-energized state is produced.
Inputs and terminology#
| Term | Meaning |
|---|---|
| Deficiency | An issue with severity, responsible owner, due date, required action and independently verified closure. |
| Readiness gate | A specified configured scope whose mandatory tests, evidence, prerequisites and designated decision must be satisfied. |
| Handover manifest | An immutable issued revision containing exact source references/hashes, plan/results, equipment history and acceptance basis. |
Procedure#
Record accountable work
In Deficiencies, choose Record deficiency and enter equipment, severity, required action, owner, due date and evidence. Link a delivery stage when appropriate.
Verify closure
After corrective work, propose closure with exact evidence. A different authorized verifier records Verify closure. Completing the linked action alone cannot close the deficiency.
Configure the gate
An authorized commissioning approver uses Readiness gates → Configure gate. Select applicable plans, required completed stages, evidence, mandatory state and the designated acceptance owner. Explicitly decide whether approved waivers may satisfy this gate.
Record current acceptance
Resolve the listed missing tests, prerequisites and deficiencies. The designated owner records acceptance only when the current basis is ready; a later invalidation makes the displayed gate incomplete again.
Issue the package
Choose Handover → Issue handover, select accepted gates and exact source documents, and record the owner and issue reason. Download the private manifest.
Inspect a retained issue
Open History to download an earlier manifest revision. Current authorization and source access are checked even for retained packages.
Verify the result#
The issued manifest retains its own evidence and revision basis. Missing mandatory evidence blocks acceptance and current handover issuance.
What happens next#
Readiness is a software evidence assessment, never available MW or authorization to energize.
Changing configuration does not rewrite an already issued manifest; its current access can still be revoked.