Project Managementlifecycle
Completion & Failure Records
What happens in the system when a project finishes — or fails?
A continON project does not just stop — it closes with an outcome record. Completion captures the actual end date, a client satisfaction score, a closing description, and a cost-benefit analysis; failure captures a documented reason with files attached.
The sequence
4 stepsReach the outcome
Work concludes or is halted; the project record is opened on its completion or failure branch.
Record a completion
Set the actual end date, score client satisfaction, write the closing description and cost-benefit analysis, and attach closing documents.
Or record a failure
Mark the project failed, write the failure description, and attach the documents that evidence the decision.
Keep the history
The outcome stays on the register entry, with task-level failed branches preserving line-level reasons.
How it works
The completed branch writes closure data onto the project record: the actual end date alongside the original estimate, a client satisfaction score, a description of the outcome, and a cost-benefit analysis text. Closing documents upload with the completion, and the record stays in the register as delivered history rather than disappearing.
The failed branch is explicit. A project can be marked failed with a failure description, and failure documents attach to the record, so the reasons survive as evidence rather than folklore. Tasks carry the same failed branch with their own descriptions and documents, which keeps line-level reasons under a failed project.
Both branches are permission-gated edits to the same project record, so the register remains the single history of what was delivered, what it was worth, and what went wrong.
Worth knowing
- Client satisfaction on the recordCompletion captures a satisfaction score for the delivering organization to keep against the customer relationship.
- Cost-benefit analysis textThe closing record includes a cost-benefit analysis field, written at completion while the facts are fresh.
- Documented failure branchFailed projects carry a failure description and attached failure documents, distinct from the completion fields.
- Task-level failure detailIndividual tasks can be set to failed with their own descriptions and documents, preserving granular reasons.
What this touches
- Task Management
Task failed branches mirror the project’s, so a failed project keeps line-level reasons on its tasks. - Document Management
Closing and failure documents are stored as files through the shared document layer. - Contract Management
The contracts a project was delivered under stay linked to the closed record.
See completion & failure records running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.