System sign-off is formal approval that the system has been designed and implemented compliantly. The sign-off role belongs to a stakeholder who can evaluate the system against organizational requirements and may veto the project outcome. Treat sign-off as an explicit delivery checkpoint, not as an informal assurance. section 2.3.2
Run sign-off as a governed project activity:
- Identify the person responsible for system sign-off alongside security, data protection, QA, budget, business, and user stakeholders. section 2.3.2
- Determine what the sign-off stakeholder requires and confirm that the project team is authorized to engage with that person. section 2.3.2
- Present the system design and implementation for approval, recording the decision and any conditions rather than relying on verbal agreement. section 2.3.2
- Keep system sign-off distinct from risk or budget sign-off: an accountable officer may accept proposed project risks, while the system sign-off role approves compliant delivery. section 3.2.3 section 2.3.2
Recorded approval checkpoint
Before committing to delivery, identify the system sign-off stakeholder and obtain agreement that the proposed design and implementation meet organizational requirements. Record the decision and circulate the supporting presentation after the sign-off meeting. Track unresolved risks separately in the risk register and revisit them with project stakeholders during regular review meetings. section 3.2.3 section 2.3.2
