A construction progress report summarises where a project stands over an agreed period and what the team needs to decide next. It is different from a daily site diary: the diary captures individual events, while the report selects and explains the information relevant to the review.
For a small UK project, start with a clear reporting period and an agreed audience. The outline below is an editorial example, not a contractual reporting form. Confirm the project’s required format and approval route before adopting it.
State the period and the comparison
Put the report date, period covered, author and project reference at the start. Identify the programme or plan being used for comparison, including its revision or issue date. Otherwise, two people can describe different levels of progress while referring to different versions of the plan.
Explain how progress was assessed. A statement that a work package is “almost finished” gives the reader little to check. Describe the completed activity, the area inspected or the remaining item, and link to the relevant record.
A compact report structure
- Summary of the reporting period and important developments.
- Work completed, with relevant locations and evidence.
- Work planned for the next period and its dependencies.
- Open information, decisions and coordination questions.
- Issues requiring review, with an owner and next action.
- References to the programme and supporting project records.
Keep headings consistent between reports so readers can compare periods. Add a short explanation when the basis of reporting changes. Do not allow an attractive dashboard to hide uncertainty about what the figures mean.
Separate facts, forecasts and requests
Use different wording for what happened and what is expected. For example, “the first-floor partitions were inspected on Tuesday” reports an event. “The next area is expected to be ready on Friday, subject to the outstanding information” is a forecast with a dependency.
This distinction helps the reader decide what needs attention. If a date or quantity has not been confirmed, say so and identify the person responsible for checking it. Do not turn an estimate into an apparent commitment by leaving out its assumptions.
Use an action table people can follow
| Issue | Information needed | Owner | Next review |
|---|---|---|---|
| Example: conflicting opening information | Reply to the referenced project query | Named responsible role | Agreed review date |
| Example: forthcoming delivery | Confirm timing and the receiving arrangements | Named coordinator | Before the planned activity |
These are fictional examples. Use real references and agreed owners in an actual report. A list of concerns without ownership is unlikely to help the next meeting reach a decision.
Link the summary to controlled evidence
Point readers to diary entries, photographs, inspection records and current information rather than duplicating uncontrolled copies. The UK BIM Framework’s September 2020 guidance on information management emphasises defined activities and responsibilities. A small project can still benefit from explicitly assigning its reporting tasks.
Agree who prepares the report, who checks factual content and who receives it. Keep the issued version identifiable. If a correction is needed, make the amendment clear so readers know which version they should use.
Finish with the decisions needed
Ask a colleague to read only the summary and action table. Can they identify the decisions required before the next review? If not, simplify the wording and move background detail into linked records. A report earns its space by helping the team understand and act.
Related project information guides
Read our construction RFI guide and advice on writing a construction project brief. For related records, see our site diary, progress report and drawing register guides.