How to Write a Daily Report Your PM Actually Reads (Free AI Template)
Here's a daily report I've seen a hundred times: "Worked on Level 2. Weather good. No issues."
Your PM learns nothing from that. And if there's a delay claim three months later, that report is the record. It says "no issues" on the day the inspector never showed.
The daily report is the most boring thing you do all day. It's also the one thing with your name on it that hits the PM's desk every single day. Do it well and you look like a lead before anyone gives you the title. Once you have a system, it takes about five minutes, and AI can do most of the typing.
Detail matters when you write a daily report. Generic reports don't provide value. Say you've got 6 techs onsite doing multiple tasks, and you just write "commissioning." That doesn't cut it. The PM and managers need to know who performed the task and what specific tasks got completed, for tracking. Same with delays. Don't just write "delays." Give the details: the 5 Ws.
Why PMs skim your report
Most reports look the same every day, so the PM stops reading closely. The important stuff is buried in the middle. Words like "some delays" don't say anything. And a report that shows up at 9 PM doesn't get acted on until tomorrow.
Your PM might get 5 or 10 of these a day. They want three answers fast: Are we on track? What's going wrong? What do you need from me? Put those up top and they'll read the rest.
The 6 sections to use every day
Same sections, same order, every day. Your PM learns where to look.
- Heads up. One or two lines on anything that hits schedule, money, or safety. If there's nothing, write "Nothing new to flag." That still tells them something.
- Crew. Who was there and how many. "4 journeymen, 2 apprentices, 1 operator. Drywall sub with 3."
- Work completed. Who did what, where, and how much. Not "worked on conduit." Try "Ran conduit gridlines C to F, Level 2. About 60% of that floor done."
- Problems and what you did. Every problem gets an action next to it. "Waiting on stamped drawings for the pump pad. Called the office at 10, told Thursday. Moved crew to backfill."
- Safety. Tailgate topic, anything you saw, near misses. If there's an incident, follow your company's process. The daily doesn't replace an incident report.
- Tomorrow and needs. The plan, and what's in the way. "Need the lift back by 7 AM or we lose the morning."
Weather, deliveries, and visitors can go on one "site notes" line at the bottom if your company wants them.
Use the 5 Ws for delays
"Delays" tells your PM nothing. Answer these instead:
- Who: Who's held up, and who's causing it (crew, sub, inspector, supplier).
- What: What work stopped or slowed.
- When: What time it started and how long it lasted.
- Where: Which area, floor, or gridline.
- Why: The cause, if you know it, and what you did about it.
Compare "delays" to this: "Inspector no-show for 10 AM rough-in, 2nd floor east. Crew of 4 moved to west side. Office rescheduling." The second one tells them everything.
The five-minute system
Don't try to remember the whole day at quitting time. You'll forget half of it. When something happens, text yourself a few words: "10:15 inspector no show" or "mud truck 40 min late." At the end of the shift, paste those notes into the prompt below, fix what comes back, and send it before you leave the lot. Not at 9 PM from the couch.
The AI daily report prompt
Copy this and save it in your phone.
You're helping a construction field lead write a daily report for their project manager.
Turn my rough notes into a report with these sections, in this order:
1. HEADS UP: 1-2 lines on anything affecting schedule, cost, or safety. If nothing, write "Nothing new to flag."
2. CREW: headcount and roles.
3. WORK COMPLETED: specific locations, quantities, and percent complete where I gave them.
4. PROBLEMS & ACTIONS: each problem with what I did about it. If I didn't say what I did, write "[ACTION?]" so I can fill it in.
5. SAFETY: tailgate topic and any observations.
6. TOMORROW & NEEDS: plan and anything I need from the PM.
Rules:
- Bullet points. Under 200 words total.
- Plain jobsite language. No corporate fluff.
- Do NOT add any numbers, times, names, or quantities I didn't give you.
- If something in my notes is unclear, put "[CHECK]" next to it instead of guessing.
My notes:
[paste your notes here]
What it looks like
Your notes (straight from the truck):
4 jman 2 apprentice. finished pulling wire 2nd floor east, started west side maybe 30%. inspector supposed to come 10 never showed, called office. lift had flat at 1, lost an hour. tailgate was ladder safety. need inspector rescheduled and lift fixed or swapped tmrw am. plan is finish west side wire.
What comes back:
HEADS UP: Rough-in inspection didn't happen (inspector no-show). Lift down 1 hr with a flat. Both affect tomorrow if not fixed.
CREW: 4 journeymen, 2 apprentices.
WORK COMPLETED:
- Wire pull complete, 2nd floor east.
- 2nd floor west started, about 30%.
PROBLEMS & ACTIONS:
- Inspector didn't show for 10 AM. Called office. [ACTION? Rescheduled for when?]
- Lift flat at 1 PM, about 1 hr lost. [ACTION?]
SAFETY: Tailgate: ladder safety. [CHECK: any observations?]
TOMORROW & NEEDS:
- Finish 2nd floor west wire pull.
- Need: inspection rescheduled, lift repaired or swapped by start of shift.
Those [ACTION?] tags show you where your report is weak. Fill them in before you send.
Check it before you send it
AI types fast, but it wasn't on site. You were. Take a minute before you hit send. Make sure every headcount, quantity, and time is right. Delete anything it added that you didn't give it. Make sure no [CHECK] or [ACTION?] tags are left. Stick to facts, not blame: "Sub crew arrived 9:30," not "Sub crew was lazy." This report could end up in a dispute.
What never goes into AI
Your own notes, crew counts, and things like "Building A" or "east side" are fine. Never paste client or project names, addresses, drawings, pricing, personal info, or injury details with names. Say "the GC" or "the owner" instead. Only use AI tools your company approves. If your company has its own report system, draft with AI and paste it in there.
Level up: the Friday roll-up
Once dailies are a habit, paste the week's five reports into AI on Friday and ask for a short summary. Your PM will think you're a mind reader.
Here are my 5 daily reports from this week. Write a short weekly summary for my PM:
progress in 3 bullets, top 3 risks for next week, and anything I asked for that's still open.
Don't add anything that isn't in the reports.
[paste reports]
Two more quick wins: take one photo per work item with a caption like "2F west, wire pull, 30%," and if the same problem shows up three days in a row, put it in Heads Up: "Third day waiting on X." That's how it gets fixed.
Why this gets you promoted
Supers and PMs don't promote the fastest installer. They promote the person they don't have to chase. A clear report every day shows you know what your crew did, you see problems coming, and you're already thinking about tomorrow. That's a foreman's job, and you're doing it before you have the title.
What I look for in a report from a lead: detail. Who performed the task, what specific tasks got completed, and the 5 Ws on any delay. "Commissioning" and "delays" don't tell anybody anything.
The bottom line
Same sections, same time, problems on top, and an action next to every problem. Let AI do the typing and you do the checking. Five minutes in the truck, and your PM actually reads it.
The Tech-to-Lead Playbook is coming soon, with printable daily report, tailgate, punch list, and Friday update templates.
And join The Tailgate, our free weekly newsletter for trades pros moving up. Join here