Template · 9 min read
Construction daily report template: five minutes at the end of the day
The daily report is the most skipped piece of paperwork in construction — and the one that decides arguments. Delay claims, change-order disputes, "that damage was already there": months later, these come down to who wrote things down on the day. This template is the ten fields worth recording, with the reason each one exists, plus a shortcut that most crews haven't tried yet: talk your notes into your phone, and let AI turn them into the clean report — and into a job-progress page your client checks instead of calling you.
Why the daily report matters more than it feels like it does
On the day, a daily report feels like bureaucracy. Ninety-nine days out of a hundred, nobody will ever read it. The problem is you don't get to know in advance which day is the hundredth.
Disputes are decided by records. When a job ends up in an argument — a delay claim, a payment fight, a "you never told us about that" — the strongest position belongs to whoever has a consistent, dated, written account from when it happened. A report that says "Rain until 11, crew of 5 moved to interior work, told the owner's rep" written that evening carries a weight that the same sentence reconstructed from memory eight months later simply doesn't. That's a general truth about how disagreements get resolved, and every contractor who's been through one knows it.
The boring days are the point. The temptation is to log only eventful days. But a record with gaps invites the question "so what happened on the days you didn't write down?" — and an explicit "safety: none, delays: none" is a fact in your favor that an empty page is not. Same format, every work day, including the short ones.
Two quieter payoffs while you're at it: problems surface while they're still small and cheap (a materials shortage noted Tuesday is a plan; discovered Friday it's a delay), and anyone can pick up the job cold — a new foreman, or you, back from a week away.
The template, field by field
Ten fields. Most take one line. The reasons matter more than the labels:
- Project + report number. Numbered reports prove the record is continuous — report #47 following #46 shows a habit, not a document written for an argument.
- Date + weather. The field that looks like filler and isn't: weather is the backbone of most delay documentation. "Rain until 11:00, site unworkable until 13:00" — with times.
- Site conditions. Access, ground, anything unusual you found on arrival. This is where "that was already damaged when we got there" gets its date stamp.
- Crew on site. Your headcount plus each sub and theirs. Labor records back up both your invoices and your delay math — a delay costs "5 crew × 2 hours", and this field is where those numbers live.
- Work completed, by area. Specific enough that someone could walk the site and check: "second-floor framing, east wall complete" — not "made progress on framing". This is also what makes the client-facing version worth reading.
- Materials. Delivered, used, short, or wrong. Wrong-and-returned deliveries noted today explain schedule slips next week.
- Equipment. On site, working, or down. Idle rented equipment is money; the note is what gets it resolved instead of re-billed.
- Delays and issues. What happened, time lost, who was notified. The notification part matters most: many contracts require prompt notice of delays, and "noted in daily report #47, owner's rep informed same day" is the sentence you want available later.
- Safety. Incidents, near-misses, toolbox talks — or an explicit "none". Never leave it blank; blank and "none" read very differently in a record.
- Photos. Phone photos with one-line captions, including of work about to be covered up — the wall cavity before the drywall is the photo you'll wish you had. Timestamped by your phone automatically.
Close each report with a "notes for tomorrow" line — first task, anything needed on site. It costs ten seconds and it's what turns the report from a record into a plan.
The upgrade: one job link the client bookmarks
updated after each site day · same link all job
- Wed 17:30
Posted change order: rotted subfloor, cost + 3 days
- Wed 19:12
Client opened · 2m 40s
- Thu 07:45
Opened again before your call
- Thu 08:00
They've seen it — the call starts from yes/no, not surprise
Here's what the daily habit buys you beyond protection: a job-progress page the client checks instead of calling you. One link per job — today's photos, what got done, what's next, and any change orders — updated after each site day. The client bookmarks it once. The "any update?" calls mostly stop, because the update is always one tap away, and a client who can see steady progress is a calmer client at invoice time.
The tracked-link part earns its keep the week something goes wrong. Post the change order on the job page and you can see the client opened it Wednesday night — so Thursday's phone call starts from a decision, not from surprise, and "nobody told us about that" has a harder time getting off the ground. Keep the page password-protected: it's the client's job, not the neighborhood's. And the honest caveat, same as always: an open shows the link was opened, not who read it or how carefully — it's a better conversation-starter than it is a courtroom exhibit. Your signed paperwork remains your signed paperwork.
The AI shortcut: talk it in, paste, done
The reason daily reports get skipped is that after ten hours on site, nobody wants to format a document. So don't. Talk the day into your phone's voice notes on the drive back — rough language, half sentences, doesn't matter. Paste that into ChatGPT or Claude with the prompt below, and it comes back as a clean, numbered, dated report with your photos listed. Your job is a thirty-second read-through to check nothing got mangled. That's the whole trick: you supply the facts, the machine supplies the formatting.
Copy this once, keep it in your notes app, and reuse it every day with fresh notes:
Turn my rough end-of-day notes into a clean construction daily report as a single, self-contained HTML file. MY NOTES — replace everything in brackets, rough language is fine: - Project: [job name / address] - Report number: [e.g. 47] · Date: [date] - Weather: [what it was like, and if it affected work] - Crew on site: [your crew count + any subs and their counts] - Work done today: [rough notes by area — what got finished, what got started] - Materials: [what was delivered, what was used, anything short or wrong] - Equipment: [what was on site, anything down or idle] - Delays or problems: [what happened, time lost, who was told — or "none"] - Safety: [incidents, near-misses, toolbox talk — or "none"] - Photos: [short description of each photo, e.g. "framing on second floor, east wall"] - Notes for tomorrow: [what's first, what's needed] RULES: - Keep every fact, number, and time exactly as I wrote it. If something is missing, put [TBD] — never fill in a guess. - Write "none" explicitly where I said none — an empty field and a "none" are different things in a record. - Clean up my wording into short, plain sentences, but do not add anything I didn't say and do not make the day sound better or worse than my notes. - Layout: project header, then the fields in the order above, photos as a captioned list at the end. - Self-contained HTML: inline CSS, no external scripts, easy to read on a phone, prints on one or two pages. Date and report number big and clear at the top.
- 1 Paste the prompt (with your details filled in) into Claude or ChatGPT. You get a finished, self-contained HTML document — review it, correct anything, iterate until it's right.
- 2 Publish it as a permanent tracked link: with the Pagelive connector in Claude, say "publish this page" and the link comes back in chat — next cycle, "update it" replaces the content at the same URL. Or paste the HTML at app.pagelive.io.
Two rules baked into the prompt worth knowing about: the AI is told to keep every fact exactly as you said it and mark anything missing as [TBD] rather than guessing — a record only protects you if it's yours. Read it before you file it; if the report says something you didn't say, fix it. It's your name on the day.
What to build it in
The carbon-copy book still works and courts of every kind understand paper. Its weaknesses are practical: no photos, one copy, hard to search, and the client never sees it.
Construction management platforms (Procore, Buildertrend and peers) have daily logs built in, tied to schedules, RFIs, and budgets. If you're a GC running multiple crews and the budget for per-project software, they're the professional answer. For a small crew or an owner-operator, they tend to be more system than the problem needs.
The notes-plus-AI-plus-link pattern above is the lightweight middle: your phone for capture, a free AI chat for formatting, and Pagelive for the client-facing side — one password-protected job page per project, updated after each site day, with view tracking so you know the change order was seen. Honest limits: it's not a project-management system, it doesn't do schedules or budgets, and the internal record you file is still yours to keep wherever you keep records. It replaces the formatting and the phone calls, not your paperwork discipline.
Frequently asked
A short written record of one day on one job site: date, weather, who was on site, what work got done, what materials and equipment moved, any delays or problems, safety notes, and photos. Filled out by the foreman, superintendent, or owner-operator at the end of each work day — five minutes that create the job's official memory.
Ten fields: project and report number; date and weather; site conditions; crew on site (yours and subs, with headcount); work completed by area; materials delivered and used; equipment on site and whether it worked; delays and issues with time lost; safety (incidents or an explicit 'none'); and photos with captions. Weather and crew matter more than they look — they're what delay claims get argued with.
Because when there's a disagreement months later — about a delay, a change, damage, or payment — the side with a dated, consistent, written record from the day it happened is in a far stronger position than the side working from memory. Daily reports also catch problems while they're small and make handoffs between crews clean. The habit feels bureaucratic right up until the day it saves you.
Whoever ran the site that day: the foreman or superintendent on a crewed job, the owner-operator on a small one. What matters is that it's one person, same format, every work day — including short days and days where 'nothing happened', because a gap in the record is exactly what gets questioned later.
Yes — the structure on this page is free to copy, and the AI prompt below turns your rough end-of-day notes into a clean, formatted report you can file or send. No app subscription needed: talk the day into your phone, paste it into a free AI chat with the prompt, and publish or print the result.
Related: project status report template · the always-live client report · how to know if someone opened your document
One job link per project. Updated after every site day.
Talk the day into your phone, let AI format the report, and publish it to a password-protected page the client actually checks. Free for 5 pages, no card.