Construction Progress Report Template

Progress reports are how you tell the story of your project. A good one gives the client confidence that their money is being well spent and the project is under control. A bad one either overwhelms them with irrelevant detail or leaves them wondering what is actually going on. Here is a practical template you can use, along with guidance on how to write reports that people actually read.

Why Progress Reports Matter

A progress report is not just a contractual obligation. It is your opportunity to demonstrate competence, flag risks early, and manage client expectations. The projects that run into the worst trouble are often the ones where communication broke down, and the client was blindsided by bad news that had been brewing for weeks.

Under NEC4 contracts, clause 50.2 requires the contractor to submit a report at each assessment date showing the actual progress compared to the programme. JCT contracts have less prescriptive requirements, but regular progress reporting is standard practice on any professionally managed project.

The report should be honest. If you are behind programme, say so. Explain why, what you are doing about it, and what the likely outcome is. Clients can handle bad news. What they cannot handle is surprises.

Template Structure

Here is a proven structure that works for projects of any size. Adapt the level of detail to suit your project value and complexity.

1. Cover page: Project name, report number, reporting period, date, author
2. Executive summary: One-page overview of status, key achievements, and critical issues
3. Programme update: Progress against programme, percentage complete, critical path status, forecast completion date
4. Work completed this period: Detailed description of activities by area or work package
5. Planned work next period: What will be done in the next reporting period
6. Health and safety: Statistics, incidents, near misses, toolbox talks, inspections
7. Quality: Inspections completed, non-conformances, snagging
8. Commercial: Valuations, variations, claims (if appropriate for the audience)
9. Design and information: Outstanding RFIs, design changes, information required
10. Risks and issues: Current risk register highlights, new risks identified
11. Photographs: Captioned, dated, showing key progress and issues
12. Appendices: Labour histograms, plant schedules, look-ahead programme

Writing the Executive Summary

The executive summary is the most important section because it is often the only section that senior stakeholders read. It should fit on one page and answer three questions:

• Where are we? Overall percentage complete. On programme, ahead, or behind? By how much?
• What happened? Two or three key achievements this period. One or two significant issues.
• What do we need? Decisions required from the client. Information outstanding. Risks that need attention.

Use a traffic light system: green (on track), amber (at risk), red (off track) for the key indicators. Most readers will look at the colours before they read a single word.

Programme Update Section

This section should compare actual progress against the baseline programme. Include:

• Overall progress: Percentage complete by value and by activity. These numbers often differ, and both matter.
• Critical path status: Which activities are on the critical path? Are they on schedule? If not, what is the impact on the completion date?
• Key milestones: List the next 3-5 milestones with planned and forecast dates. Highlight any that have moved.
• Delay analysis: If the project is behind programme, explain the causes. Distinguish between excusable delays (client changes, weather, utilities) and contractor delays. Reference your site diary entries for evidence.
• Recovery measures: If you are behind, what are you doing about it? Additional resources, revised sequencing, weekend working. Be specific about the planned recovery and the expected outcome.

Include a visual representation of progress. A simple bar chart showing planned vs actual for each work package is more effective than a page of text. If your project has a formal programme in Asta or Primavera, include a summary extract, not the full 200-line programme.

Health and Safety Section

The H&S section should include:

• Statistics: Hours worked, accident frequency rate, RIDDOR-reportable incidents, lost-time injuries, near misses reported
• Incidents: Brief description of any incidents or near misses, with actions taken
• Inspections: Results of safety inspections, audit scores, enforcement notices
• Training: Toolbox talks delivered, inductions completed, CSCS card checks
• Observations: Positive and negative safety observations from site walks

Present the safety statistics as trends, not just numbers. Showing that near miss reporting has increased by 40% over three months tells a better story than just saying "12 near misses reported." It suggests a safety culture that is improving. For guidance on near miss reporting, see our near miss reporting guide.

Common Mistakes

• Too much detail: The client does not need to know that you laid 47 linear metres of drainage on Tuesday. They need to know that drainage is 60% complete and on programme. Save the detail for your site diary.
• Copy-paste syndrome: Copying last month's report and changing the dates is obvious and makes you look lazy. Every report should be freshly written for the period it covers.
• Burying bad news: Putting a programme delay in the middle of page 8 does not make it go away. It makes the client angry when they eventually find it. Lead with the issues.
• No photographs: A report without photos feels incomplete. Photos provide evidence, context, and are the quickest way for a reader to understand the current state of the works.
• Late submission: A report that arrives three weeks after the end of the reporting period is almost useless. The information is stale. Establish a clear deadline and stick to it.
• Ignoring the audience: A report for a property developer is different from one for a local authority. Adjust your language, level of detail, and focus accordingly.

Tips for Better Reports

1. Use a consistent format: The same structure every month allows readers to find what they need quickly. It also makes the report faster to write because you have a framework to follow.
2. Write in plain English: Avoid jargon where possible. Not everyone reading your report is a construction professional.
3. Be specific about actions: Instead of "issue to be resolved," say "M&E coordination meeting scheduled for 12 March to resolve clash at gridline D/4. Decision required by 15 March to avoid impact on ceiling programme."
4. Include a look-ahead: A 3-4 week look-ahead programme gives the client visibility of upcoming activities, access requirements, and decisions needed.
5. Review before issuing: Read it once for accuracy, once for tone. Remove any emotional language. "The architect has still not provided the information despite repeated requests" is factual but loaded. Rephrase as "Architect's information outstanding since [date]. Third request issued [date]. Impact on programme if not received by [date]."

Site Manager AI can help you generate progress report drafts quickly by structuring the information you provide into a professional format with the right sections and level of detail. It saves hours of formatting and ensures you do not miss any important sections.

Related Reading

• How to Write a Daily Site Diary
• Construction Programme Management Guide
• How to Run a Site Meeting Effectively
• Construction Project Handover Checklist