Key takeaways
- Lead with status against the baseline: percentage complete, planned versus actual, forecast finish.
- Report by deliverable or phase, using the same numbering as the plan and scope.
- Separate issues (happening now, needs a decision) from risks (may happen, needs watching).
- Record the cause and owner of every delay on the day it occurs — this is the evidence for an extension claim.
- End with a short list of decisions or inputs required, each with a date needed.
The structure of a progress report
| Section | Content | Length |
|---|---|---|
| Header | Project, reporting period, report number, prepared by | A few lines |
| Status summary | Overall status, percentage complete, forecast finish, cost position | One short paragraph |
| Planned vs actual | Deliverable-level comparison against the baseline | A table |
| Completed this period | What was finished and accepted | Bullets |
| Planned next period | What will be finished and by when | Bullets |
| Issues | Live problems, impact, owner, required decision | A table |
| Risks | Potential problems, likelihood, impact, mitigation | A table |
| Variations and delays | Approved and pending changes, delay events and causes | A table |
| Actions required | What the client must decide or supply, with dates | Bullets |
Measuring progress honestly
Percentage complete is only meaningful if it is measured the same way every period. Choose one method and state it in the report.
- Deliverable-weighted: each deliverable carries a weight; progress is the sum of completed weights. Best for professional services.
- Quantity-based: units installed against total units. Best for construction and installation work.
- Milestone-based: progress recognised only at milestone acceptance. Hardest to game, least granular.
- Effort-based: hours spent against hours estimated. Useful for cost, misleading for completion.
Never report progress above the last accepted deliverable without saying so. A 90% figure followed by two months of work destroys the credibility of every later report.
Delays, issues and the paper trail
Most extension-of-time and additional-cost claims in the region are decided on contemporaneous records, not on later reconstruction. The progress report is where that record is created.
- Describe the delay event factually: what happened, on which date, on which deliverable.
- State the cause and the party responsible — access, approval, information, weather, third party.
- Quantify the impact in days on the affected task and on the critical path.
- Record the mitigation attempted and its outcome.
- Reference the notice sent, if the contract requires notification within a set period.
Cadence and audience
Weekly internal reports keep the team honest; fortnightly or monthly client reports keep the relationship calm. Keep both from the same data set — the timesheets and the plan — so the internal and external stories never diverge. At the end, the accepted progress reports make the completion certificate straightforward to issue.
How to write a project progress report
Step 1: Set the period and reference
Number the report and state the reporting period and the baseline it compares against.
Step 2: Summarise status
Give overall status, percentage complete, forecast finish and cost position in one paragraph.
Step 3: Compare plan to actual
Table each deliverable with planned and actual progress and the variance.
Step 4: List completed and upcoming work
Record what was finished and accepted, then what will be delivered next period.
Step 5: Log issues, risks and delays
Capture each with impact, owner, mitigation and the date it arose.
Step 6: Ask for decisions
Close with the approvals or inputs required and the date each is needed by.
Frequently asked questions
How long should a progress report be?
Two to four pages for a monthly client report, one page weekly internally. If it is longer, move detail to annexes and keep the status, issues and actions at the front.
What is the difference between an issue and a risk?
An issue is already happening and needs a decision now. A risk has not happened and needs a mitigation and an owner. Mixing them hides the things that require action today.
Who prepares and signs the progress report?
The project manager prepares it; the client's representative or engineer acknowledges receipt. Where the contract makes reporting a condition of payment, keep the acknowledgement.
How do I report bad news?
State the position, the cause, the impact in days or money, and the recovery plan, in that order. Reports that soften the position lose the ability to claim later.