GuidesProjects
Change project status
Move a project between Draft, In review, Finalised, and Archived.
The project status sets the tone for the whole project, most importantly, it controls whether edits require a change reason. See statuses and lifecycle for the conceptual overview.
Steps
Open the project.
Click the status pill in the project header.
Pick the new status from the dropdown.
If you're moving away from Finalised or Archived, type a change reason in the dialog and confirm.
When each status applies
| Status | Use when… |
|---|---|
| Draft | The project is new or being actively built out, most editing happens here. |
| In review | The customer is reviewing decisions. Lets the team flag projects that need eyes-on rather than active editing. |
| Finalised | The customer has signed off. Edits now require a reason; sign-off is committed. |
| Archived | The build is complete and out of active rotation. The project drops out of the default project list. |
Reason requirement
You'll be prompted for a change reason when transitioning away from Finalised or Archived (e.g. Finalised → Draft, Archived → In review). Other transitions don't require one.
Audit trail
Every status change shows in the audit log with the user, the timestamp, the from/to statuses, and the reason if one was given.
Tips
- Don't stack-rank statuses too rigidly, they're a tool, not a contract. If your team uses In review as "ready for the supervisor to walk through," great; if you skip it entirely and go Draft → Finalised, also fine.
- Use Archived instead of deletion. Archiving keeps the audit log and exports recoverable; deletion is harder to undo.