What the project lifecycle is
The project lifecycle is the set of states a project moves through from the day it is opened to the day it is closed. In a project execution system those states are not a diagram on a wall — they are a live status on the project record that decides which projects appear on which screen, drives the roll-up of cost and progress, and tells everyone at a glance whether a project is running, paused, finished or shelved.
For a business that builds to order, the practical lifecycle has four states — Active, On Hold, Completed and Inactive — and every project carries both a status and the date it entered that status. Understanding what each state means, what happens inside it, and how a project moves between them is the difference between a clean portfolio and a list where finished and stalled jobs are impossible to tell apart.
The four lifecycle states
Each state answers a different management question, and a project sits in exactly one at a time:
| State | What it means | What is happening |
|---|---|---|
| Active | Running now | Tasks are being executed, resources consumed, progress and actuals accruing against budget |
| On Hold | Paused, will resume | Work stopped for a reason — awaiting client approval, material, funds — but the project is not abandoned |
| Completed | Delivered and closed | All tasks at 100%; final estimated-vs-actual reviewed; project archived as a reference |
| Inactive | Shelved or cancelled | No longer being pursued; kept for the record but out of the live portfolio |
The value of an explicit status is that it separates the three things a flat project list constantly confuses: a job that is genuinely moving, a job that has stalled and needs a decision, and a job that is done. Without states, an "On Hold" project awaiting a client sign-off looks identical to an Active one that is quietly slipping — and both hide among the Completed jobs nobody has archived.
The states also drive who looks at what. A project manager works the Active list every day; an owner reviews the On Hold list weekly to chase the blockers releasing stalled work and cash; finance mines the Completed list for the estimated-versus-actual variances that should sharpen the next quotation. One flat list serves none of them well, because it forces every reader to mentally filter out the projects that are not their concern. Tabs bound to status do that filtering automatically, so each role opens straight to the projects that need its attention — which is why lifecycle state is a management tool, not just a label.
What happens in each phase
Within the Active state, a well-run project also moves through the familiar execution phases — define, plan, execute, close — which map onto the lifecycle like this:
On Hold sits across the top of execution: a project can move to On Hold from any point in the plan-execute cycle and back to Active when the blocker clears, without losing its place. Inactive is the exit for work that will not resume. The point is that the lifecycle state and the execution phase are two dimensions of the same record — one says is this project live?, the other says how far through delivery is it?
Budget, actual and progress through the lifecycle
What makes the lifecycle useful rather than decorative is the numbers that ride along with it. Every project — and every task within it — carries both a plan and an actual:
- Budget vs actual budget — the estimated cost set at Define against the cost actually incurred as work proceeds, so the gap is visible at every stage
- Finish date vs actual finish date — the planned close against the real one, the schedule half of the same story
- Progress % — per task, rolled up to a single project completion figure that moves the project toward Completed
- Status and status date — which state the project is in and when it entered it, so an On Hold job’s age is on the record, not in someone’s memory
Because these travel with the status, a project's position is always a roll-up of real work: an Active project shows live estimated-vs-actual; an On Hold one shows exactly when and where it stalled; a Completed one preserves the final variance as a reference for quoting the next similar job. Read more on the estimate side in the Bill of Resources & costing feature.
Want to see the lifecycle running on real projects?
In a 30-minute demo we show the Active, On Hold, Completed and Inactive tabs with live budget-vs-actual and progress — on projects like yours.
One record, four states, always reconciled
A fabricated structure is opened with a budget and dates — it enters Active and its WBS, Gantt and Bill of Resources are built. Mid-way, the client pauses for a design change: the project moves to On Hold with the status date recorded, so its two-week stall is on the record rather than lost. Work resumes, it returns to Active, progress climbs to 100%, the final RA bill is raised, and estimated-vs-actual is reviewed — then it is set Completed and drops out of the live portfolio into the archive. A sister enquiry that never gets funded is opened and set Inactive, kept for the record but off the working list. Every move is one status change on one record; the cost, progress and billing stay reconciled throughout.
How Fast Project Software implements the lifecycle
Fast Project Software implements the lifecycle as tabbed project lists — Active, Inactive, On Hold and Completed — each bound to the project's status, so a project appears under the tab that matches its state and moves between tabs as its status and status date change. Every project header carries owner, customer, type, start and finish dates, budget, actual finish and actual budget, progress % and status, and every WBS task mirrors the same fields at task level.
That means the lifecycle is not a separate tracker to maintain — it is the same project record that carries the WBS, the Gantt, the Bill of Resources and billing. Move a project to Completed and its final cost, progress and bills are all already on it. It is the natural way to run a portfolio of ETO, fabrication, EPC or construction jobs at once, with Dhruv AI summarising status, cost and slippage across the portfolio.
Frequently asked questions
What are the phases of the project lifecycle?
In a build-to-order execution system the project lifecycle has four states: Active (running now, with tasks executing and actuals accruing), On Hold (paused for a reason but not abandoned), Completed (all tasks at 100%, reviewed and archived) and Inactive (shelved or cancelled, kept for the record but out of the live portfolio). Within Active, a project also moves through the execution phases of define, plan, execute and close.
What is the difference between On Hold and Inactive?
On Hold means a project is paused but will resume — work has stopped for a reason such as awaiting client approval, material or funds, and the project keeps its place so it can return to Active when the blocker clears. Inactive means a project is shelved or cancelled and will not be pursued; it is kept for the record but removed from the live portfolio. The status date on each records when the project entered that state.
How is budget versus actual tracked through the lifecycle?
Every project and every task carries both a plan and an actual: a budget set at Define against the actual budget incurred as work proceeds, and a planned finish date against the actual finish date. Progress percent per task rolls up to one project figure. Because these numbers travel with the status, an Active project shows live estimated-versus-actual, an On Hold one shows where it stalled, and a Completed one preserves the final variance for future quoting.
Why does a project need explicit lifecycle states?
Explicit states separate the three things a flat project list confuses: a job that is genuinely moving, one that has stalled and needs a decision, and one that is finished. Without states, an On Hold project awaiting sign-off looks identical to an Active one that is slipping, and both hide among un-archived Completed jobs. A status and status date on each project keep the portfolio clean and make each project's position unambiguous.
How does project management software manage the lifecycle?
It stores a status and status date on each project header and lists projects in tabs bound to that status — Active, On Hold, Completed and Inactive. A project appears under the tab matching its state and moves between tabs as its status changes, while the same record carries the WBS, Gantt, Bill of Resources and billing. So moving a project to Completed automatically brings its final cost, progress and bills with it — nothing is re-keyed.