Operations & Project Management
Project Closeout
Formally close the project record with a complete, verifiable package rather than letting it linger open.
- Trigger
- Final payment received and all documentation filed.
- Owner
- Project Manager
- Inputs
- Final invoice status.
- Documentation package.
- Required conditions
- Final invoice paid.
Steps
- Verify the closeout checklist is complete.
- Assemble the closeout package.
- Archive documentation.
- Mark the project Closed.
Decision points
- Is the closeout package complete? → If not, return to the specific missing item rather than blocking on everything.
- Outputs
- Closed project record and closeout package.
- Handoff
- Customer Success / Account Manager
- Failure / exception path
- Closeout package incomplete — the project stays open past the Closeout stage until resolved, not marked Closed anyway.
Candidate system state transition
Project → CLOSED
All five Project Closeout Standard conditions satisfied — technical work complete, documentation complete, customer acceptance captured (or a documented exception), financial/admin handoff complete, and any open exceptions resolved or explicitly documented. CLOSED is not "installation finished" — it is the last of three distinct states: INSTALLATION COMPLETE ≠ READY_FOR_ACCEPTANCE ≠ CLOSED, each produced by a different Process.
Documented for Phase 2 — no state machine exists yet.
Related system objects
Related lifecycle stages
Related standards
Related forms
None yet
Future automation opportunity
Block the Closed status transition until every Project Closeout Standard checklist item is checked.
Required data
- Final invoice paid date
- Closeout checklist completion status
- Closed date