Status & lifecycle
Every project has a status that reflects where it is in its life. A project is Active the moment it's created and moves through the lifecycle from there.
Project statuses
| Status | Meaning |
|---|---|
| Active | The normal working state — the default for a new project. |
| On Hold | Paused for now, but not finished. |
| Completed | Work is done. The project is locked (see below). |
| Archived | Closed out and tucked away, out of your active lists. |
Completing a project
When a project is finished, you complete it — and Bluprint asks for a reason, which is recorded in the audit trail. Completing does something important:
Completed projects are locked
Once a project is marked Completed, it's locked from further edits. This keeps a finished project as an accurate record of what happened, rather than something that can be quietly changed after the fact.
Reusing a completed project
Often the next project looks a lot like the last one. Instead of rebuilding it, you can export a completed project — Bluprint clones it into a brand-new Active project so you can pick up where you left off.
The clone copies across:
- Tasks and their subtasks
- Documents
It deliberately leaves behind the things that belonged to the original run — its chat history, attachments, and audit trail — so your fresh project starts clean.
Archiving and deleting
- Archive / soft delete — removes the project from your active views while keeping it recoverable.
- Permanent delete — removes the project for good, along with its tasks, task dependencies, and documents.
Permanent delete can't be undone
Permanently deleting a project also deletes its tasks, dependencies, and documents. If you might want the work later, archive it instead.
Ask the Associate
Before you complete a project, ask the Associate for a wrap-up — a health summary and report drawn from everything that happened — so nothing important is lost once the project is locked.
Next
Last updated: 2026-05-31
.png)