Construction progress is useful only when a reported percentage can be traced to a measurement basis, a defined data date, and a programme activity that represents the same work. A progress figure copied from a meeting slide may look precise while still mixing installed quantities, procurement status, weighted milestones, and planner judgment. This control-sheet workflow helps planning engineers, quantity surveyors, and site managers reconcile those inputs before they are used in a programme update.
The method is a practical governance workflow, not a universal measurement rule. The contract, approved progress procedure, bill of quantities, activity coding, and project-specific reporting rules govern where they differ.
What the control sheet must answer
For every reported activity or work package, the control sheet should answer five questions: what work is being measured; what quantity or milestone defines completion; what was true at the data date; how the reported percent complete was calculated; and what evidence supports the entry. It should also show who prepared and checked the status. Those fields convert “the activity is 60% complete” into a reviewable record.
Keep the baseline and the current update separate. The baseline is the approved reference plan. The update records status and forecast at the new data date. A revised baseline is a separate governed decision, not a convenient way to remove an adverse variance.
1. Fix the reporting cut-off and activity scope
Start with the previous data date and the new data date. Confirm the project, WBS, activity codes, calendars, and reporting period. Extract the activities and work packages included in the period; do not allow the list to change informally while percentages are being collected. If the schedule contains a single activity for several physically different work fronts, record that limitation and consider whether the activity structure needs a governed review.
Use one row per measurable item where practical. Useful columns include activity ID, WBS, description, unit, total planned quantity, quantity installed to the previous data date, quantity installed this period, cumulative quantity, remaining quantity, planned value or weight, physical progress, evidence reference, and checker.
2. Define the approved measurement basis
Do not switch between duration percentage, physical quantity, weighted milestones, and earned value without recording the change. A concrete pour may be measured by accepted volume; a submittal may be measured by approved milestones; a long-lead item may require separate procurement and installation activities. The measurement basis should reflect what the activity represents and should be applied consistently from one update to the next.
For quantity-based work, state the unit and the source of the total quantity. Distinguish installed and accepted work from delivered material, stored material, inspected work, and work awaiting test results. A delivery record may support procurement progress but does not automatically prove installed physical progress.
3. Reconcile quantities before calculating percent complete
Check the opening cumulative quantity against the prior approved update. Add the current-period quantity, subtract any approved correction or rejected work, and calculate the new cumulative quantity. Compare cumulative quantity plus remaining quantity with the controlled total. Any mismatch should be explained before the number is sent to P6 or the progress report.
| Control | Review question | Typical evidence |
|---|---|---|
| Total quantity | Is the denominator approved and consistent with the activity scope? | BOQ, IFC quantity, take-off, or approved measurement sheet |
| Current quantity | Was the work installed during the reporting period and accepted under the project rules? | Inspection request, quantity record, survey, test or approval |
| Cumulative quantity | Does the opening balance plus this period reconcile to the closing balance? | Prior update and signed control sheet |
| Remaining quantity | Does the balance agree with site conditions and the schedule forecast? | Planner/site review and look-ahead |
| Activity status | Do actual dates and remaining duration represent the same work measured by quantity? | Daily report, inspection record, and P6 activity status |
4. Calculate and review the reported percentage
For a quantity-based item, a simple physical progress calculation is cumulative accepted quantity divided by the approved total quantity, multiplied by 100. The formula is only valid when the numerator and denominator use the same scope and unit. Do not use a physically measured percentage as a substitute for an earned-value calculation unless the project’s approved method says how the two relate.
As a separate arithmetic illustration, an activity with 12 planned workdays, 7 verified actual workdays, and 5 workdays remaining gives 7 ÷ (7 + 5) × 100 = 58.3% duration progress. This is a check on the arithmetic only; it is not a universal rule for physical progress, earned value, or contractual entitlement. The project’s approved measurement basis remains controlling.
5. Map the control sheet to the programme
Before entering progress, confirm that the activity ID, description, WBS, calendar, and progress type match the control sheet. Enter actual dates only when supported by project records. For in-progress activities, review actual start, physical progress, remaining duration, and remaining quantity together. A high physical percentage with a large remaining duration may be correct for a late testing or commissioning stage, but it should be visible and explained.
Primavera P6 supports estimating progress as of a new data date and also supports individual activity or resource updates when work has deviated from plan. Its Update Progress documentation describes how actual dates and remaining durations are applied according to the selected data date and settings. Use the automatic route only when its assumptions match the evidence; otherwise update and review the affected activities deliberately.
6. Test the forecast and variance logic
After status entry, reschedule using the approved options and compare the forecast with the previous update and baseline. Review the critical path, total float, free float, remaining duration, relationships, constraints, lags, calendars, and any negative float that appeared. Trace a changed forecast to its status input, logic change, remaining quantity, calendar, or constraint. A progress percentage by itself does not explain a completion-date movement.
Record exceptions rather than hiding them. Examples include a quantity that exceeds the controlled total, physical progress that is ahead of the activity’s actual start, an activity marked complete with remaining quantity, out-of-sequence work, or a narrative that reports progress not visible in the schedule. Each exception should have an owner and a resolution or qualification.
7. Issue the progress narrative with evidence
The narrative should state the data date, work completed, work planned next, material variances, forecast effect, and unresolved measurement exceptions. Link important statements to the control-sheet row, inspection record, approved quantity, or schedule comparison. Separate observed progress from forecast judgment. If the subject affects a delay or claim, describe the schedule evidence without asserting contractual entitlement; notice, causation, criticality, concurrency, mitigation, and entitlement depend on the governing contract and project records.
Pre-submission checklist
- The data date, project, WBS, activity scope, and reporting period are recorded.
- The baseline is identified and has not been replaced merely to reduce variance.
- Every percentage has a stated measurement basis, unit, numerator, denominator, and evidence reference.
- Opening, current, cumulative, and remaining quantities reconcile.
- Physical progress, actual dates, remaining duration, and forecast are reviewed together.
- Critical path, total float, free float, logic, constraints, lags, and calendars were checked after rescheduling.
- Exceptions are assigned, explained, and carried into the narrative.
- The control sheet, native schedule, exports, approvals, and supporting records are stored under document control.
Related EngineersBlog reading
- How to Update a Primavera P6 Programme: A Practical Monthly Workflow
- Updated Programme in Project Management: Keeping the
- Method statement for progress override in primavera p6
- Method statement for physical weightage percent
References
Conclusion
A reliable progress percentage is the end of a controlled chain, not the beginning: define the data date and scope, agree the measurement basis, reconcile quantities, map the status to the programme, test the forecast, and issue a narrative that a reviewer can reproduce. This is how progress data becomes useful project-controls evidence instead of an isolated number.
