An update is more than a percentage complete
A weekly or monthly report needs to distinguish what has happened from what is still expected. Actual starts, actual finishes and remaining durations tell different parts of that story. Nexora brings schedule updates into the same workspace as the planning programme.
Before updating, agree the reporting cut-off and collect progress evidence from the site team. Keep the approved baseline available for comparison and distinguish a forecast update from an approved baseline revision.
Build a repeatable reporting cycle
- Set the data date. Use the agreed cut-off for all packages in the reporting cycle.
- Record actual progress. Reconcile starts, finishes and quantities against the site records.
- Reassess remaining work. Review durations, crew availability, access, approvals and procurement.
- Review the forecast. Inspect milestone movement, critical-path changes and logic around incomplete work.
- Explain the movement. Write a narrative that connects the date change to evidence and an action owner.
Worked example: one extra remaining day
Illustrative single-chain example, with one working calendar and no parallel work or additional constraints.
The baseline chain is excavation, three days; reinforcement, three days; concrete, two days. At the data date, excavation is finished. Reinforcement has not started, and the revised crew assessment gives it four remaining days.
| Activity | Original remaining duration | Revised remaining duration |
|---|---|---|
| Reinforcement | 3 working days | 4 working days |
| Concrete | 2 working days | 2 working days |
| Total remaining chain | 5 working days | 6 working days |
The simplified completion forecast moves by one working day. In a real programme, another path or a constraint may govern completion, so examine the network rather than adding durations across unrelated activities.
A useful update narrative
Report the data date, changed milestones, progress achieved, causes of slippage and the next actions. Separate observed facts from assumptions about future output. A clear explanation should let a project manager understand why the finish date moved and what decision is needed.
- Which work package drives the current forecast?
- Which remaining durations changed, and why?
- What approvals or resources are needed in the next reporting period?
- Is recovery being assessed, or is the movement part of a delay event?
Use recovery planning to compare corrective scenarios, and delay analysis when an event needs a separate assessment.
Common questions
What is the data date?
It is the cut-off separating recorded progress from the remaining forecast. Use one agreed cut-off and consistent evidence for the update.
Does a progress update change the approved baseline?
An update should preserve the distinction between actual progress, the current forecast and the approved baseline. Baseline revision requires the applicable project approval process.
Can a high percentage complete still hide a late finish?
Yes. The remaining critical work and its dependencies can drive completion even when much of the total quantity is finished.
Explore the workflow in Nexora
Bring a representative work package and review the assumptions with your project team.