Planned progress is the achievement expected from the baseline by a cut-off date. Actual progress is verified achievement by that same date. Their variance is a useful signal, but two percentages cannot describe the complete health of a project. The result depends on the baseline, weighting method, cut-off discipline, and update quality.
Start with a controlled baseline
Planned progress must reference a clearly identified baseline. If the baseline is changed every time performance slips, variance disappears along with the decision history. A revised baseline should follow an approved change process, with prior versions and reasons retained for transparency.
Align data date and measurement rules
Planned and actual values require the same data date and compatible WBS and weighting. Different work may use installed quantities, weighted milestones, or accepted deliverables. Rules should prevent excessive credit at activity start and avoid counting the same output in multiple places.
Cumulative and period performance
Cumulative progress shows the overall position, while weekly or monthly output shows the latest production rate. A project may remain behind cumulatively while its current rate is improving. Another may look close to plan cumulatively while recent output has declined. Both views are needed to understand direction.
Why percentages can mislead
- High-weight non-critical work can mask delay to a critical milestone.
- Cost progress does not always represent time progress.
- Procured material may earn weight without being ready for installation.
- Rework may not be visible in a simple completion percentage.
- Teams may use different evidence or reporting cut-offs.
Move from variance to cause and impact
When actual is below planned, identify the areas, work packages, and activities creating the gap. Then determine whether the issue affects a milestone, critical path, or available float. Causes may involve information, materials, labour, access, or sequence. A precise cause supports a useful action; a general instruction to “accelerate” may not remove the constraint.
Build a decision-ready report
Show the baseline reference, data date, planned, actual, variance, and trend. Add a concise narrative answering what happened, what it affects, what is being done, who owns the action, and what decision is required. Photographs and evidence should be connected to the reported location and period.
Use planned versus actual with discipline
The comparison is valuable when data is consistent and the team shares the measurement rules. The objective is not to make two lines look equal. It is to detect deviation early, understand its causes, and make timely decisions using information that can be traced and challenged.