Template · 20 October 2026
The daily site report is the most important document nobody wants to write. Here is the one-page template we recommend, free to download.
When a project runs well, nobody reads the daily site report. When something goes wrong (a delay claim, a payment dispute, a client asking "what exactly happened in March?") it becomes the only thing that matters. And that is usually when everyone discovers the reports are vague, late or missing.
This is the template we recommend: what goes in, and what separates a useful report from a useless one.
Download the template (PDF, one page) All 8 sections, space for 6 captioned photos. Print it or fill it in digitally.
A daily site report is a factual record of what happened on site, on one day. Not an assessment, not a marketing document: a record. Work done, people present, materials moved, problems hit, weather. Written the same day, every day.
Its readers are the project manager checking progress, the client (often in another city or country), the quantity surveyor tracking variations, and future-you, in a dispute, needing proof of what happened on a specific date. If your report can't answer "what did the steel fixers actually finish on the 14th?", it is a diary entry, not a report.
Project name, date, report number, prepared by. Boring and non-negotiable: this is what makes the report searchable later.
Temperature, rain, wind, anything that affected work. "Rain 2–5pm, concreting postponed" explains more than a paragraph of excuses later.
What actually got done, by area and trade. Be specific: "Block B, level 2: slab formwork 80% complete", not "formwork in progress". Vague entries are how disputes start.
Headcount by trade and contractor, for example "12 total: 5 masons, 4 steel fixers, 2 helpers, 1 electrician". This is your productivity baseline and your evidence if labour claims come up.
Delivered today, used today, and what is running short: "20 bags cement delivered; sand stock low, reorder by Thursday." A material log catches both theft and bad planning.
What went wrong or is at risk. This is the section most reports skip, and the most valuable one: "Crane breakdown 10am–1pm; 3 hours lost on steel erection." Honest problem-logging is what separates a professional operation from a hopeful one.
Dated, captioned, tied to locations: "Block B level 2, slab formwork, east side." Photos without captions are decoration; with captions, they are evidence.
What is scheduled next. It turns the report from a history document into a management tool, and it forces the "are we actually on track?" question daily.
The common failures, from vague notes to reports written from memory at 10pm, are covered in five daily site report mistakes that cost builders money.
Everything above works on paper. The problem is not the template, it is the discipline. Filling 8 sections by hand, every evening, after a full day on site, is exactly the chore that gets skipped, rushed or copy-pasted.
SiteTab exists because the crew already produces the raw material (photos, voice notes and updates in the site WhatsApp group) all day. It is a WhatsApp contact you add to that group. It files the day's messages and drafts the report from them (work done, materials, labour, issues, photos), and the project manager reviews it before it goes out. Our guide to a daily site report from WhatsApp shows how that works. One group is $10 a month, with a 7-day free trial and nothing to install.
Start your 7-day free trial No card needed.