Separate physical progress from billed and certified progress

Illustrative example: a simple package contains 1,000 metres of identical work under one assumed rate. At the same cutoff, 600 metres are installed, 500 are accepted, 450 have been claimed and 400 are certified. There are no variations or rate differences in this teaching example.

The 100 metres between installation and acceptance need inspection or acceptance follow-up. The 50 metres between acceptance and claim may need measurement or bill preparation. The 50 metres between claim and certification need commercial review of the certificate difference.

Those are useful operating queues. Averaging 60%, 50%, 45% and 40% produces 48.75%, but that figure has no defined purpose. It does not tell anyone which action to take.

In a real contract, certified progress may be a value percentage against contract price rather than a quantity percentage. Label it accordingly. The simple example works only because scope and rate are deliberately uniform.

It also assumes each stage is a subset of the preceding one. That need not hold for a contract paying for approved design milestones, off-site equipment or materials before installation. In those cases, financial progress can exceed installed progress without an error. Reconcile the payment components to their contractual evidence instead of subtracting two percentages with different bases and calling the result an installation backlog.

For each reported measure, specify the numerator, denominator, unit or weighting method, as-of date and scope version. State whether installed quantities are gross installation or net retained work after removals. Define which acceptance status qualifies for accepted progress.

For a commercial measure, identify whether value includes approved variations, taxes, advances or deductions. An advance payment should not silently appear as physical progress. Retention affects cash and payment presentation; it does not mean an equivalent proportion of work is uninstalled.

Oracle’s P6 WBS reference exposes multiple earned-value calculation methods. This is a product-level example of why “percent complete” needs a defined method. It does not make any one field a universal measure of construction completion.

Illustrative example: package A has an approved progress weight of 20% and is 100% complete. Package B has a weight of 80% and is 25% complete. Weighted progress is:

20% × 100% + 80% × 25% = 40%

The simple average of the two completion percentages is 62.5%, which overstates progress under the agreed weighting method. The weights might be based on budget, labour effort or an approved milestone structure. The project-controls owner should choose and document the basis that fits the reporting purpose.

Do not add metres of pipe, cubic metres of concrete and equipment counts into a single physical quantity. For a multi-discipline project, retain the underlying measures and use approved weights for the roll-up. Show major package exceptions so the overall percentage does not conceal a critical incomplete system.

Milestones need defined completion rules. A 0/100 milestone and a partially earned milestone can both be valid methods in different contexts, but changing between them mid-report will alter the result without any physical change on site.

Suppose the illustrative 1,000-metre scope increases to 1,200 metres through an approved change while installed work remains 600 metres. Installed progress against the current scope becomes 50%. The project did not remove 100 metres; the denominator changed.

Show the previous-scope and current-scope views where needed, with a bridge explaining the change. Do not freeze the old denominator to preserve a favourable percentage, or silently replace it and leave management to infer that productivity collapsed.

Keep baseline, current approved scope and forecast scope distinguishable. Proposed changes may matter for forecasting while remaining outside approved contract value. The commercial and planning owners should agree how each appears in the report.

Revisit roll-up weights through the same controlled process. If package B grows, retaining its old weight while reporting its new scope changes the meaning of the total. Preserve the weights used in each issued report, document the authorised revision and separate its effect from progress earned during the period.

The site lead owns the reported physical work. Quality owns the relevant acceptance decisions. The QS and commercial team own measurements and applications under the contract. The client’s authorised representative owns certification, and finance owns receipt allocation.

Use a common package or item mapping to connect their records, but preserve their independent decisions. A planner should not mark work accepted merely because the installation report is complete. A billing tool should not treat every accepted quantity as already claimed.

Autodesk’s payment-application workflow distinguishes application and later approval/payment states. The equivalent project report should keep those stages visible, using the business’s actual definitions and source records.

Age the gaps. A recent acceptance backlog may be expected within the review cycle. The same quantity open for several periods needs attention. Separate ordinary waiting time from missing evidence, disputed scope or rejected work so the queue has a useful owner.

Show the stage measures side by side, then identify the largest or oldest differences. Add the relevant need dates where a pending acceptance affects follow-on work. For cash planning, use the certification-to-receipt forecast instead of assuming certified percentage converts immediately to cash.

Measure consistency as well as progress: missing mappings, unexplained denominator changes and records that cannot be traced to evidence. A stable reporting process should allow the team to reproduce last month’s number using last month’s scope and cutoff.

Different progress figures become useful when their definitions are clear and their gaps are explained. The objective is an agreed interpretation, not forced equality between operational and commercial records.

1. Define installed, accepted, claimed and certified measures for one package.
2. Align their cutoff dates and document each denominator.
3. Reconcile the quantities or values between stages.
4. Assign the oldest gaps to the relevant owners.
5. Roll up only with an approved weighting method and an explicit scope-change history.