Progress Report Template Clients Actually Read

Clients don’t read progress reports. They scan them

Watch a client open a weekly progress report. They do three things: look at the photos, hunt for the word “done”, and check whether anything threatens the date they’ve already promised someone else. Everything else — the methodology preamble, the paragraph about scaffolding logistics — gets skimmed at best.

A good construction progress report is built for that reader. Not padded to look thorough, not defensive, not vague. This guide walks a free progress report template that puts what clients read first — and keeps the percentages honest.

Download the progress report template: PDF

Structure: done first, everything else after

The template’s order is the whole trick:

• Period and project header. Which week, which site, who wrote it.
• Executive summary — 3 to 5 sentences, maximum. What moved, what’s at risk, what you need from the client. If they read nothing else, this paragraph did the job.
• Completed this period. The “done” list, specific and photographed. Lead with it — it’s what they came for.
• In progress. What’s underway and where it stands, by zone or trade.
• Risks and blockers — each with an owner. Not a weather report: a list of named items, who’s on them, and what happens if they don’t move.
• Next period. What “done” should look like in next week’s report.

One or two pages. A report that takes longer to read than the week took to happen has failed.

Honest percentages, or none

“73% complete” impresses exactly once. The third time the number doesn’t reconcile with what the client saw on their walk, every future number is discounted.

The honest framing is to anchor percentages to something countable: of the logged items in this phase, X are closed. “14 of 19 apartments tiled” survives scrutiny; “78% finishes” is an argument waiting to happen. If you can’t count it, describe it — never let the percentage imply schedule precision the underlying data doesn’t have.

Photo discipline: highlights, not dumps

Two or three photos per completed item — the ones that show the state, wide enough to recognise the location. Not forty pages of every angle of the same slab: the 40-page photo annex is where credibility and patience go to die. If the client wants everything, give them access to the full record; the report carries the highlights. (The technique for making each photo carry its own context — where, when, what state — is the subject of our construction photo documentation guide.)

Risks with owners, not weather forecasts

The risk section fails when it’s written as atmosphere (“supply chain conditions remain challenging”). It works when every line has a name and a consequence: lift delivery unconfirmed — with supplier, chasing; if not confirmed by Friday, shaft closure slips a week. Clients respect named risks; they punish surprises that were vague warnings three reports ago.

Where the data should come from

The real reason progress reports take a painful Friday hour is that they’re written from memory. The week is over; the author scrolls a camera roll and a WhatsApp thread, reverse-engineering what happened.

The alternative: the report assembles from the week’s captured records. If findings and milestones are logged as they happen — a pin on the plan with a photo and a voice note (auto-transcribed), an owner, a status on the Kanban board — then Friday is a review of what’s marked done and what’s still open, not an act of recollection. The daily site report is the same idea at daily grain: honest dailies make the weekly a ten-minute assembly.

One template, a steady rhythm

Send it the same day each week, in the same format, even in slow weeks. Rhythm is what turns a report from a document into a signal: the week a risk appears in the summary line, a client trained by consistent reports actually reads it. The construction report types guide shows how this weekly sits on top of the rest of the site paperwork.

FAQ

What should a construction progress report include? Period header, a 3–5 sentence executive summary, completed work with photos, work in progress, risks and blockers each with an owner, and the plan for the next period. One to two pages.

How often should progress reports be sent? Weekly on active sites, monthly for slower phases — but the interval matters less than the rhythm. Same day, same structure, every time.

How do I report progress percentages honestly? Anchor them to countable items — “14 of 19 units tiled” — and say what the denominator is. Never present a percentage with more precision than the underlying records support.

What PinMy is NOT

PinMy is where the week’s field records accumulate — located pins with photos, voice, owners and statuses. It does not write your progress report: the narrative, the percentages and the promises stay yours, and our web PDF export is useful today but still maturing. It doesn’t replace your programme or your planner. It just means Friday’s report starts from records instead of recollection.

This Friday, try the order

Write one report with “done” first, three photos per item, and every risk owned by a name. Then send this to whoever writes the 40-page photo annex.

• Start free: pinmy.co
• Book a 15-minute walkthrough: tidycal.com/pinmy