Construction Progress Reporting: Best Practices for Site Managers [2026]

Progress reports are how you communicate the state of your project to everyone who needs to know: the client, the project manager, the commercial team, and your own management. A good progress report builds confidence, manages expectations, and provides an early warning system for problems. A poor one creates confusion, erodes trust, and can contribute to disputes. Here is how to get it right.

Why Progress Reporting Matters

Progress reporting is not just administrative overhead. It serves several critical functions on a construction project:

• Client communication: Keeping the client informed reduces anxiety and builds the trust that leads to repeat business
• Programme management: Regular progress assessment against the programme identifies delays early, when they can still be mitigated
• Commercial management: Progress data underpins interim valuations, variation assessments, and extension of time claims
• Risk management: Documenting progress and issues creates a contemporaneous record that is invaluable in the event of disputes
• Resource planning: Understanding actual progress versus planned progress allows you to adjust resource levels and sequences

What to Include in a Progress Report

Executive summary

Start with a one-paragraph summary of the overall project status. Is the project on programme, ahead, or behind? Are there any critical issues? This should give the reader a clear picture of the project health without needing to read the full report. Be honest. If the project is behind programme, say so. Trying to hide bad news in a progress report always backfires.

Programme status

Report progress against the construction programme. For each major activity or section, state the planned progress, the actual progress, and any variance. Use percentage completion consistently and make sure your percentages are based on measurable criteria rather than subjective estimates.

Works completed this period

List the significant works completed since the last report. Be specific: "Completed first fix M&E to block A, floors 1-3" is more useful than "M&E works progressing well." Include photographs where they add value, particularly for works that will be covered up by subsequent trades.

Works planned for next period

Set out the works planned for the next reporting period. This manages expectations and allows the client and project manager to plan their own activities (site visits, design decisions, approvals) accordingly.

Issues and risks

Document any issues that are affecting or may affect the programme, cost, or quality of the project. For each issue, state the impact and the action being taken to resolve it. Do not wait for problems to become crises before reporting them. Early visibility of issues allows early intervention.

Health and safety

Include a summary of health and safety performance including any incidents, near misses, and the results of any inspections or audits. This demonstrates your commitment to safety and provides a record of safety management activity.

Quality

Report on quality management activities including inspections carried out, snag list status, and any quality issues identified and resolved. Proactive quality reporting demonstrates professional management and reduces the risk of unpleasant surprises at handover.

How Often to Report

The reporting frequency should be defined in the contract or agreed with the client at the start of the project. Monthly reporting is standard for most projects, with weekly reporting during critical phases. Some clients require weekly reports throughout.

Whatever the frequency, consistency is key. Reports should be issued on the same day every period, in the same format, covering the same content. This allows the reader to quickly find the information they need and compare performance across reporting periods.

Common Reporting Mistakes

Being too vague

"Good progress made across all areas" tells the reader nothing. Be specific about what was done, where, and by whom. Quantify progress wherever possible.

Hiding bad news

If the project is behind programme, report it clearly along with the recovery plan. Concealing delays never works because they eventually become visible, and by then the trust damage is far worse than the delay itself.

Inconsistent format

Changing the report format every month makes it difficult for readers to find information and impossible to track trends. Establish a template and stick with it.

The best progress reports tell a clear story: where we were, where we are now, what happened in between, and where we are going next. If you can answer those four questions clearly and honestly, you have a good progress report.

Using AI to Improve Progress Reporting

AI tools can significantly reduce the time spent on progress reporting while improving the quality of the output. By feeding in the key data points (activities completed, programme status, issues encountered), AI can generate a structured progress report that follows your standard format and includes appropriate detail. The site manager then reviews and customises the draft, adding professional context and judgement that the AI cannot provide.

The time saving is particularly valuable at the end of a reporting period, when the site manager is already under pressure from multiple demands. Spending 30 minutes reviewing and refining an AI-generated report rather than two hours writing one from scratch frees up time for the work that matters most: managing the project.