Model-based Percent of Completion for project controls
The method connects progress to the same model the team updates every day: project items in the task panel, phase bars on the timeline, category weights for the project and completion status for phases relevant to each item.
Percent of Completion in PHASI is configurable for engineering, construction, infrastructure, manufacturing, audits, services and other structured workflows. It gives project teams a progress signal grounded in the plan, not only in a manual status field.
Project structure
The task panel describes what is being planned or delivered: assemblies, modules, assets, zones, documents, supplier packages, service deliverables, audit scopes or other project items.
Relevant phases
Each item can have only the phase bars it needs. Work is measured by phases present on the item, not by a generic checklist.
Category weights
Admins weight phase categories for a project, such as Requirements, Engineering, Procurement, Construction, Manufacturing, Testing or Approval.
Calculated completion
PHASI combines category weights and completed relevant phases into item, parent item and project-level Percent of Completion.
Deliverable-based completion with phase weighting
Percent of Completion in PHASI combines deliverable-based progress with phase weighting. The method is inspired by Earned Value Management, but it is grounded in the project’s own deliverable structure and phase bars.
Teams define which phase categories matter, how they are weighted and which phases are relevant for each item. The completion value is derived from the configured model rather than stored as a detached opinion.
Phase Weight
Phase Weight = Category Weight / Relevant phases in that categoryIf Engineering has a 10% weight and five relevant engineering phases, each relevant engineering phase contributes 2%.
Item PoC
Item PoC = sum((Category Weight x completed relevant phases) / Relevant phases in category)A project item becomes complete through the weighted phases that are relevant to that item.
Project PoC
Project PoC = sum(top-level item PoC) / Number of top-level itemsChild items are included inside their parent items before the top-level project result is calculated.
How the calculation works
Category weights
Admins define how much each phase category contributes to completion. The total category weight should not exceed 100%.
Relevant phases
If a work package does not require procurement, procurement is not treated as missing work for that item.
Parent items
A parent item can be calculated from child items. If it also has its own phase bars, the parent itself becomes an additional calculation unit.
Project-level result
The project-level completion value is calculated from top-level items to keep the summary readable while detail remains available below.
Configuration concepts
- Weight phase categories for the project.
- Count only phases that exist for a project item.
- Roll parent completion up from child items and, where relevant, from the parent’s own phase bars.
- Use milestones as schedule context without replacing factual phase completion.
The more accurately a team maintains the project structure and timeline, the more accurately PHASI reflects the project’s current state. The result is configurable, but less arbitrary than a detached manual percentage.
Connect completion to the planning model
Use PHASI to keep project structure, phase planning, completion and project discussion in one shared project-controls workspace.