M1.4 — Progress Measurement

M1.4 — Progress Measurement

1. Practical outcome

By the end of this section, the learner should be able to design, apply and challenge progress-measurement rules that convert evidence of completed work into a credible statement of physical accomplishment. They should be able to choose an appropriate measurement method for different types of work, define the evidence needed to claim progress, calculate and aggregate progress consistently, and explain how progress information connects to schedule status, cost and integrated performance analysis.

The objective is not to produce a percentage because the reporting cycle requires one. It is to answer a much more useful question: “How much of the authorised work has genuinely been accomplished at the data date, on a basis that another competent person could understand and verify?”

Where progress rules are established and used

M1.4 owns the design of measurement methods, denominators, weights, completion criteria, evidence and correction rules. M1.3 approves the relevant rules within the integrated baseline; M1.5 preserves source records and their lineage. M2.4 applies the approved rules during schedule updates and independently forecasts remaining duration. M5.1 selects decision measures; M5.3 converts eligible accomplishment into earned budget value; M5.4 and M5.5 use the resulting evidence for forecasts and decisions. These uses should reference the M1.4 rule rather than create competing definitions of progress.

2. Core concepts

Progress is evidence of physical accomplishment

Physical progress represents work actually accomplished against defined scope. It is not the same as elapsed time, money spent, labour hours consumed, invoices received or a subjective feeling that the team is “about two-thirds done”. Those measures may provide useful supporting information, but none is automatically proof of physical completion.

This distinction matters because projects can spend money without creating equivalent value, consume time without completing deliverables, or appear almost finished for many reporting periods while difficult residual work remains. A credible progress system therefore starts with the work itself and asks what observable evidence demonstrates accomplishment.

A useful rule is: progress should be earned by completing defined scope, not by consuming the resources that were expected to complete it.

The measurement method should fit the nature of the work

There is no single correct progress method for every work package. The method should reflect how the work is physically produced, what can be objectively observed and the level of precision justified by the importance and duration of the work. A repetitive installation may be measured by units complete; a design package may need weighted deliverables or milestones; a short task may justify a simple fixed formula; genuine support activity may be level of effort.

Selecting the method is therefore an exercise in professional judgement. The practitioner should be able to explain why a method represents accomplishment reasonably and why a more convenient method would be less reliable.

Common progress-measurement methods

Define the unit of measure before measuring

The practitioner needs to decide what is being measured. “Install furniture” might mean individual items, completed rooms, accepted room packages or weighted zones. The choice changes the reported result. Where units differ significantly in complexity, treating every unit as equal can distort progress and a weighted approach may be needed.

The denominator matters as much as the numerator. If a package contains 1,000 defined units and 420 have met the acceptance criterion, the basic units-complete measure is 42%. If the scope later changes to 1,100 authorised units, the denominator changes only through controlled scope/change processes; it should not drift informally to make performance look better or worse.

Weighted milestones should represent real accomplishment

Weighted milestones are useful where work progresses through identifiable stages but does not produce simple repetitive units. For example, a procurement package may move through specification approval, order placement, manufacture, delivery, installation and acceptance. Each milestone receives an agreed weight before performance begins.

Weights should reflect the relative significance of the accomplishment, not the ease of claiming it. Front-loading large weights onto early administrative steps can create apparently strong progress while the difficult delivery work remains outstanding.

Where these milestones generate earned value, their budget weights must be consistent with the planned resources and cost basis of the work. A milestone’s strategic importance or a supplier payment percentage is not, by itself, a budget-weighting method. Label a differently weighted physical-progress index separately.

Progress rules should be defined before results are known

The measurement basis should be agreed at or before baseline, not invented during a difficult reporting period. Predefinition reduces bias, supports consistency between periods and makes later challenge easier. Where a rule genuinely needs to change because authorised scope or the delivery method has changed, the reason, approval and effective date should be recorded.

The data date and evidence cut-off are part of the measurement system

Progress is always measured at a defined point in time. Evidence received after the reporting cut-off should not be backdated casually into the period. The team needs a clear data date, collection timetable and rule for late evidence so that schedule, cost and performance information refer to the same reporting position.

Evidence should be proportionate but auditable

Evidence may include approved drawings, signed inspection records, accepted deliverables, system records, photographs, quantities, test results, configuration status, delivery receipts or other objective records. The evidence burden should be proportionate to the importance of the work, but the basis for claimed progress should be reproducible rather than depending entirely on the person reporting it.

Physical progress, schedule progress and financial progress are related but different

Schedule software may calculate duration percent complete, physical percent complete or work percent complete using different rules. Finance systems record cost. Procurement systems record commitments and invoices. None should be assumed to equal physical accomplishment. The project should define which field or calculation represents the approved progress measure and reconcile other indicators to it rather than allowing competing percentages to circulate.

Completion criteria determine what progress means

An installation activity can finish when installation meets its defined criterion while separate test and acceptance activities remain open. A package defined as installed, tested and accepted cannot finish merely because installation is complete. Use the scope dictionary and measurement specification to establish this boundary before reporting. A delivery receipt, inspection pass or test attempt is evidence of its own state; it is not automatically evidence of the next state.

For each material measure record the scope identifier, unit and denominator, completion criterion, eligible evidence, weighting, data date, accountable validator and treatment of rejection or late evidence. Duration percent complete and financial spend remain separate measures unless an explicit approved relationship applies.

Aggregation requires controlled weighting

Progress at a higher level should be built from lower-level measures using a defined weighting basis. A simple average of child percentages is usually inappropriate because the child packages may represent very different amounts of scope. Weighting may be based on budgeted value, planned labour hours, quantities or another approved scope weighting, provided the basis is stable, transparent and appropriate.

For example, if four work packages have agreed control weights of 15%, 40%, 30% and 15%, and their physical progress is 90%, 35%, 60% and 10%, the parent progress is 47%: (0.15×90) + (0.40×35) + (0.30×60) + (0.15×10). The result is not obtained by simply averaging four percentages.

Rework, rejection and incomplete acceptance need explicit treatment

Progress should not become irreversible merely because it was reported once. If work is rejected, materially reworked or found not to meet the agreed completion criterion, the project needs a defined rule for correcting previously claimed progress. This can be uncomfortable, but preserving an inaccurate achievement figure is worse. The same principle applies where delivered items are later found unusable or a design submission is rejected.

Distinguish an original overstatement from additional rework arising after valid completion. Correct the physical status and forecast openly, but apply the adopted EVMS rules before changing previously reported earned value. Preserve the original report, the correction or new-work basis, its approval and the reconciliation; do not automatically erase valid historical credit whenever rework arises.

Level of effort should not conceal discrete performance

LOE is appropriate for genuine support activity whose effort is expected to continue with time, such as some project-management or routine coordination work. It should not be used as a convenient substitute for measuring deliverables. A project can report 100% of planned LOE for a month while the physical outputs that the support function exists to enable are materially late.

Progress measurement supports, but does not replace, forecasting

A package can be 80% physically complete and still require more than 20% of its original duration or cost to finish. Progress describes accomplishment to date; forecasting estimates what remains. The two should inform one another, but the project should not assume that percent complete automatically determines remaining duration, remaining cost or completion date.

3. Step-by-step method — how to design and operate progress measurement

1. Confirm the authorised scope and control structure. Start with the WBS, work packages, control accounts and current authorised scope. Progress can only be meaningful if the work being measured has a clear boundary. Resolve ambiguous ownership, duplicated scope or undefined work before designing percentages.

2. Identify the measurable work within each package. Break the package into the deliverables, quantities, stages or acceptance points that represent genuine accomplishment. Avoid measuring administrative activity when the real output can be measured directly.

3. Classify the nature of the work. Decide whether the package is repetitive/quantity-based, milestone-based, short discrete work, apportioned effort, genuine LOE or another special case. This classification guides the measurement method.

4. Select the most appropriate measurement method. Choose the method that best represents physical accomplishment with proportionate effort. Document why it is suitable and where it may be misleading.

5. Define the measurement denominator and boundaries. For units complete, define the total units and whether units require weighting. For milestone methods, define the complete set of milestones. For other methods, define what constitutes the full authorised scope represented by 100%.

6. Define milestone or component weights before performance begins. Where weights are needed, set them using a defensible scope basis. Check that weights total 100% and do not front-load progress onto easy early steps.

7. Define objective completion criteria and evidence. State what must be true before each unit, milestone or portion of progress can be claimed and what evidence demonstrates that condition. Clarify whether “installed”, “tested”, “approved” and “accepted” mean different things.

8. Align progress rules with schedule activities and status conventions. Identify how progress will be recorded in the schedule. Define actual start/finish criteria, physical percent fields, remaining-duration updates and any relationship between the progress measure and earned-value calculations.

9. Define aggregation and roll-up rules. Agree how lower-level progress contributes to control-account, WBS and project totals. Use controlled weights and prevent double counting. Document how changes to scope weights will be governed.

10. Separate discrete, apportioned and LOE work. Keep genuine deliverable progress visible. Confirm that LOE cannot dominate or artificially improve the apparent performance of discrete work.

11. Establish the data date, cut-off and reporting calendar. Define when evidence must relate to, when it must be submitted, who validates it and how late information is treated. Align this with schedule and cost reporting where possible.

12. Collect progress evidence from the source. Obtain quantities, acceptance records, approvals, test results or other evidence. Do not rely solely on narrative percentages supplied by package owners.

13. Validate and challenge reported accomplishment. Check samples against source evidence, compare with schedule actuals and remaining work, inspect unusual movements and challenge repeated unchanged percentages or large jumps.

14. Calculate progress using the approved rule. Apply the defined formula consistently. Retain the underlying quantities, milestone status and weights so the result can be reproduced.

15. Reconcile progress with other control information. Compare physical progress with schedule status, actual cost, commitments, earned value, productivity and forecast. Differences may be legitimate, but significant inconsistencies should be explained rather than ignored.

16. Control corrections, method changes and history. Correct errors transparently, retain reporting-period history and use formal change where the authorised scope or measurement basis changes. Avoid rewriting prior periods simply to create a smoother trend.

4. Worked Reference Project example — Community & Learning Centre

The Community & Learning Centre Reference Project contains several different kinds of work, which makes it useful for showing why one universal progress rule would be poor practice. The examples below use the same 24-month, 50 million CU reference project and its six Level-1 WBS elements.

Example A — Design & Approvals: weighted deliverables

A design package under 1.1 Design & Approvals contains five agreed outputs. Before work starts, the project assigns weights: requirements confirmed 10%; concept design approved 20%; detailed design issued 35%; statutory/authority approval obtained 20%; construction information released 15%.

At the data date, requirements and concept design are complete, detailed design is assessed as fully complete against its issue criterion, but authority approval and construction release have not occurred. Physical progress is therefore 10 + 20 + 35 = 65%. The team does not add extra progress merely because approval discussions are “well advanced”; the next milestone earns its weight only when the defined criterion is satisfied.

Example B — Furniture & Specialist Equipment: staged procurement progress

For a specialist-equipment package under WBS 1.3, the agreed weights are: specification approved 10%; purchase order placed 15%; manufacture complete 35%; delivered to site 15%; installed 20%; accepted 5%. At the data date the first two milestones are complete and manufacture is 50% complete using a separately defined manufacturing quantity/evidence rule. Progress is 10 + 15 + (0.50×35) = 42.5%.

The supplier has invoiced 60% of the order value. That does not make physical progress 60%. The invoice may reflect payment terms, advance payments or material procurement. Cost and physical progress should be compared, not treated as the same measure.

Example C — External Areas & Access: units complete

A paving package contains 1,000 square metres of equivalent, accepted paving. At the data date 420 square metres have been laid and passed inspection. A further 260 square metres of materials are on site but not installed. Under a units-complete rule, physical progress is 42%, not 68%. If different paving zones have materially different effort, the project should define weighted zones rather than assume every square metre is equivalent.

Example D — Operational Readiness: completed tests rather than elapsed time

Operational Readiness includes 120 defined readiness and system-acceptance tests. Eighty have been attempted, but only 72 have passed and been accepted. If the agreed rule is accepted tests complete, progress is 60% (72/120). Failed tests remain incomplete until the acceptance criterion is met. This prevents apparent progress being earned for activity that has not yet produced the required result.

Example E — Project controls support: genuine level of effort

Some project-control and coordination activity may be authorised as LOE across the 24-month period. Progress for that support package may follow time, provided the scope genuinely has no discrete measurable output. The LOE package should be reported separately enough that it cannot mask poor progress in Design, Building, Technology or Handover deliverables.

Worked aggregation example

Assume a control account contains four child packages with approved scope weights of 15%, 40%, 30% and 15%. Their measured physical progress is 90%, 35%, 60% and 10%. The control-account progress is 47%: 13.5 + 14 + 18 + 1.5. A simple average would be 48.75%, which is not the authorised weighting basis. The difference becomes much larger when package sizes vary more significantly.

The learner should also compare that 47% physical accomplishment with the schedule and cost position. If 60% of planned time has elapsed and 58% of the control-account budget has been spent, the response should not be to change physical progress. It should be to investigate productivity, phasing, payment terms, rework, delayed outputs or other causes of the mismatch.

Example F using different completion states

A separately defined Technology subset contains 100 equivalent points. At the cut-off, 78 are reported installed; installation evidence is available for 70; 68 have passed the specified test; and 64 are formally accepted. The reported installation ratio is 78%, evidence coverage of the installation claim is 70/78 = 89.7%, passed-test completion is 68% and accepted completion is 64%. The 70 evidenced installations are not automatically all accepted. Confirm the relationship between records, reconcile the eight unsupported installation claims, and do not average the four states into one percentage.

If the agreed measure is accepted points, claim 64% for that subset and retain the other states as diagnostics. M5.1 uses this teaching subset for performance indicators. It is separate from the 240-point installation exercise in M2.4 and does not redefine that exercise denominator.

5. Interpretation and professional judgement

The arithmetic of progress measurement is usually simple. The difficult part is deciding what deserves to count as accomplishment and building rules that remain credible under delivery pressure.

Is the method measuring the output or merely the effort?

A package that reports progress from labour hours consumed can appear healthy while productivity collapses. Prefer evidence of completed deliverables where practicable.

Is the measurement level proportionate?

Measuring every minor component can create an expensive reporting system with little decision value. Measuring only at a very high level can conceal problems until late. Select enough granularity to support control of material work.

Does the method front-load progress?

If 60% of a procurement package is earned by specification and order placement, the project may look advanced while manufacture, delivery, installation and acceptance remain. Challenge the weights against where the real delivery effort and risk sit.

What counts as complete?

“Delivered”, “installed”, “tested”, “approved” and “accepted” are not interchangeable. The rule should reflect the point at which the project has genuinely achieved the relevant part of scope.

How should design progress be measured?

Design work often tempts subjective percentages. Use defined deliverables, maturity gates, document status or other evidence where possible. If judgement remains necessary, use a rubric rather than an unsupported percentage.

How should rework be handled?

If previously completed work is rejected or materially undone, progress may need to reduce. A reluctance to reverse progress is not a technical justification for leaving the measure wrong.

Can software-generated percentages be trusted automatically?

No. Duration percent complete may simply measure elapsed duration; work percent complete may reflect resource hours; physical percent complete may be manually entered. The practitioner must know which field represents the approved rule.

Does progress still make sense beside remaining duration?

A package can legitimately be 80% physically complete with 50% of its duration remaining if the residual work is slower or more complex. But the inconsistency should be understood, not ignored.

Are incentives distorting the measure?

Where payment, performance ratings or management attention depend on progress, people may have incentives to claim early accomplishment. Objective evidence, independent challenge and stable rules reduce this risk.

Is LOE overwhelming the project result?

Large support packages that earn progress automatically with time can make aggregate performance appear better than discrete delivery. Keep the distinction visible.

Would two competent reviewers reach broadly the same conclusion?

Perfect objectivity is not always possible, but a good measurement system should substantially reduce dependence on who performs the assessment.

A useful practitioner test is: “If the package owner changed tomorrow, could the new owner reproduce this progress figure from the agreed rule and the evidence?” If not, the method is too dependent on individual judgement or undocumented assumptions.

6. Practice diagnostic

Use this table to challenge the quality of the approach or deliverable. The rows consolidate the most important recurring red flags and checks; they are prompts for professional judgement rather than a substitute for the method above.

7. Try-it-yourself practical exercise

Using the Community & Learning Centre Reference Project, design and operate a small progress-measurement system rather than simply assigning percentages:

1. Select five different work packages from at least three Level-1 WBS elements, including one design package, one procurement/equipment package and one repetitive delivery package.

2. Classify each package by the nature of the work and select a suitable progress-measurement method. Explain why at least one plausible alternative method would be weaker.

3. For the design package, create four to six measurable deliverables or maturity gates and assign weights totalling 100%. Define the evidence required to earn each weight.

4. For the procurement/equipment package, build a weighted milestone scheme from specification through acceptance. Check whether the weights are front-loaded and revise them if necessary.

5. For the repetitive package, define the unit of measure, total denominator and acceptance rule. Decide whether all units are equivalent or require weighting.

6. Identify one genuine LOE support activity and explain why LOE is appropriate there but would be inappropriate for one of the discrete packages.

7. Create a reporting cut-off and a small evidence pack showing which milestones/units have been achieved at that date. Include one item submitted after the cut-off and decide how it should be treated.

8. Calculate physical progress for each package and then create a higher-level roll-up using pre-agreed weights. Show the arithmetic so another learner can reproduce the result.

9. Introduce three deliberate complications: a rejected design deliverable, delivered-but-not-installed equipment, and completed work for which the supporting evidence arrives late. Recalculate or explain the treatment of each.

10. Compare your progress result with a fictional schedule/cost position in which 60% of planned time has elapsed and 58% of budget has been spent. Write a short note explaining why those figures do or do not indicate a performance problem.

11. Change the authorised quantity of one package through a formal scope change. Explain how the progress denominator and historical reporting should be handled without rewriting prior performance casually.

Additional exercise on completion evidence

For the 100-point subset in Example F, identify the approved numerator for an accepted-output rule; list evidence needed to validate installation and acceptance independently; and explain how rejected or retrospectively corrected points would be recorded. State which decisions belong to measurement design in M1.4 and which belong to schedule updating in M2.4.

12. Prepare a one-page Progress Measurement Basis for the five packages containing the scope reference, method, weights/units, evidence, data cut-off, owner, validation rule and aggregation basis.

What good performance looks like

The exercise is successful when the learner can explain why each method was chosen, reproduce every percentage from evidence, distinguish physical accomplishment from time/cost consumption, deal consistently with rejection and cut-off issues, and show how package progress rolls into a credible higher-level view. The goal is not to make the percentages look smooth; it is to make them trustworthy.

8. Bridge to capability

The How-to teaches how to measure physical accomplishment. At APPLIED and above, capability assessment should test whether the practitioner can select and apply suitable rules to realistic work evidence, calculate a defensible result and challenge unsupported claims. Defined methods, weights, acceptance criteria and reconciled calculations should show how the reported progress was obtained. Supporting work products are illustrative and should be assessed with the practitioner’s reasoning. Sample learning questions illustrate the judgement at each recognition level; they are discussion prompts rather than validated assessment items.

Learning question: Do you understand how physical accomplishment should be measured?

Capability question for APPLIED and above: Can you demonstrate a reproducible progress result, justify the method and challenge evidence that does not support the claim?