Standards
Project Closeout Standard
Define exactly what CLOSED means, so a project is never marked Closed just because Installation finished — Closed requires the full chain, not the loudest part of it.
- Owner
- Project Manager
- Governs
- What the closeout package must contain.
- Applies to
Requirements
Each requirement must eventually be verifiable — not policy prose.
Installation execution and commissioning must be complete and signed off.
The documentation package must be complete per the Documentation Standard.
Customer acceptance must be captured — signed or acknowledged per the Customer Acceptance Process, based on project stakes.
The final invoice must be issued and payment recorded, or explicitly waived by the General Manager.
Any known outstanding item must be documented with an owner and a target resolution date before Closed status is set.
- Future system rule
Project can't move to Closed status without a complete closeout package.
Compliance measurement
Projects closed with all five closeout requirements satisfied ÷ projects marked Closed.
Required data
- Per-requirement completion flag
- Closed date
Exceptions
- Approver
- General Manager / Executive
- Reason required
- A recorded justification for closing with a documented outstanding item (e.g. a warranty punch-list item).
- Evidence required
- The outstanding item, its owner, and its target resolution date.