Status as live state.
Progress rules, reporting periods, revisions, and rollups on the same packages planning already owns — so sponsors read truth, not a deck rebuilt every Friday.
Overall complete
68%
vs baseline 72%
A deck is not a progress system.
Standalone tools treat % complete as a paintbrush. Delivery orgs need rules, periods, revisions, and rollups that survive audit — and match the plan.
Status as performance
When progress is a narrative, sponsors get the version that fits the room. Exceptions surface late — or not at all.
Inconsistent % complete
One package uses gut feel, another uses quantity, a third uses milestones. Rollups become fiction.
No period discipline
Updates arrive whenever someone remembers. There is no freeze, no revision trail, no trusted cut for the board pack.
Agree how complete is measured.
Versioned progress rules assign a basis per control object — publish, assign, retire. Rollups stop mixing gut feel with quantities.
MANUAL PERCENT
Manual %
Operator-entered percent with revision history.
PHYSICAL QUANTITY
Physical quantity
Installed qty vs planned qty — engineering-grade.
WEIGHTED MILESTONE
Weighted milestone
Milestone gates with weights that roll up cleanly.
DURATION
Duration
Time elapsed vs planned duration where it fits.
COST WEIGHTED
Cost-weighted
Progress that respects cost weight when finance cares.
ZERO ONE HUNDRED
0 / 100
Binary complete — no half-done theater.
A cut you can freeze.
Open a period, collect updates, lock the cut, approve the rollup. Lifecycle actions are records — not a Slack thread saying “numbers are final.”
Period opened
PMO
CompleteUpdates collected
Package owners
CompletePeriod locked
Controller
CompleteRollup approved
Sponsor · pending
Active
Every change leaves a trail.
Package updates carry revisions with who, when, and why. Controllers accept or send back — progress stops being an overwritten cell.
- Updates scoped to a reporting period
- Revision actions: submit, accept, reject
- Notes and evidence on the change
- Control objects stay linked to the plan
S. Iyer · Package lead · Mar 27 · 14:12
MEP duct route delayed — coordination hold
S. Iyer · Package lead · Mar 20 · 11:04
Quantity catch-up after weekend pour
S. Iyer · Package lead · Mar 13 · 16:40
Period open baseline update
One number sponsors can trust.
Recalculate rollups for the period from control-object updates — weighted by the rules you published, not by whoever last edited the slide.
| Structure | Weight | Complete | Contribution |
|---|---|---|---|
| 1 Civil | 35% | 82% | 28.7% |
| 2 MEP | 30% | 61% | 18.3% |
| 3 Fit-out | 20% | 44% | 8.8% |
| 4 Commission | 15% | 24% | 3.6% |
Surface risk before the board pack.
At-risk packages, overdue updates, and ahead-of-plan signals — derived from the same period state, not a separate RAG spreadsheet.
MEP coordination · at risk
Behind baseline by 4 days. Latest revision cites duct routing hold — visible without a status meeting.
Updates overdue · 4 packages
Period lock approaching. Owners who have not submitted show up before the cut, not after.
Commissioning · ahead
Milestone cleared early. Rollup credits the gain instead of hiding good news in the average.
Make status a property of the project
Measurement rules, reporting periods, revisions, and rollups — progress that sponsors can read without a weekly rebuild.