Weekly construction report to a client: structure and example
A weekly client report should explain what changed, what happens next and which decisions are needed. Build it from the daily records, then summarise by work area so the reader can act without reconstructing the entire week.
A structure you can copy
- Project and reporting period: start date, end date and person preparing the report.
- Completed work: location, scope and a reference to supporting photographs or records.
- Next week's plan: work, owner and prerequisites.
- Delays and changes: cause, affected work, agreed response and any unresolved impact.
- Decisions required: a specific question, decision owner and required date.
- Open quality items: status and next review.
Keep the reporting period consistent. A photograph from a previous week can provide context, but label its date so it is not mistaken for current progress.
Example of a useful progress entry
Fictional example, 14–18 September. “Level 1, grid B–D: partition setting-out completed and checked against drawing revision C. References: daily report 18 September and PHOTO-14. Next: start framing on 21 September after delivery confirmation. Client decision: confirm the door finish by 22 September; responsible contact: project representative.”
This entry distinguishes completed work from planned work and a pending decision. Avoid a percentage such as “90% complete” unless the measured scope and method are clear.
Assemble the report from the daily record
-
Review the week's daily reports
Check dates, locations and entries for missing days. Resolve conflicting descriptions with the site lead before copying them into a client summary.
-
Group facts by work area
Summarise a sequence of daily updates into the latest confirmed result. Retain the source references so the summary can be checked.
-
Make decisions easy to find
Put unresolved questions together with a named decision owner and required date. Separate the proposed response from the response already agreed.
-
Review and send one version
Have the responsible project person check the report. Record its issue date and version, and keep corrections traceable rather than circulating competing copies.
Use evidence that explains the change
Select photographs that show the relevant work area, with a clear caption and date. Link to the underlying report or item instead of attaching an unexplained camera roll. For a delay, describe the affected activity and what was done in response; do not infer a contractual entitlement from the report alone.
Start the daily collection with the free daily report template. For consistent photo references, use the guide to construction progress photos.
Doing this in TerenIQ
Use TerenIQ's daily reports and project work records as source material for your weekly summary. Review the facts, select the relevant progress and record the decisions that need follow-up. The weekly structure above is a writing method; it does not assume a dedicated automatic weekly-report feature.
Frequently asked questions
How long should the weekly report be?
Long enough to explain progress and obtain decisions. Start with a concise summary and link the detail. The reporting requirements of your project determine the final format.
Should I repeat every daily report?
No. Summarise the latest confirmed position by work area and retain references to daily records for readers who need the detail.