The daily log and the daily report are not the same thing.
A daily report is a formatted document. It has a structure — date, weather, crew count, work completed, issues, materials received. It gets compiled, reviewed, and sent to the GC. It’s a communication artifact.
A daily log is the raw record. It’s what the foreman captures in the field throughout the day as the work happens. It’s the basis for the daily report, and for a lot more: progress payment backup, punch list defense, change order documentation, incident records. The daily report is the summary. The daily log is the source.
Most foremen have a daily log. It lives in their head. At the end of the day, they reconstruct it from memory — what was completed, who was where, what came up — and compile it into the daily report. Sometimes that reconstruction is accurate. Sometimes it’s “floor 3 rough-in, made good progress” because the details of Tuesday afternoon are gone by 5 PM Friday.
The difference between a useful daily log and a foreman’s memory is when it gets captured and how specific it is. Here’s what that looks like in practice.
What Goes in a Daily Log Entry
A daily log entry answers three questions about a specific piece of work at a specific time:
What happened? Not “worked on rough-in” — which crew, which zone, which specific task. “East wing conduit run complete, Floor 3” is a log entry. “Worked on Floor 3” is not.
When did it happen? Time of completion or time observed. Not the time you wrote it down at the end of the day — the time it happened. “East wing conduit complete, 10:15 AM” gives you a progress timeline. “East wing conduit complete” gives you a checklist.
Was there anything notable? Delay, conflict, substitution, damage, inspection result, weather impact. If the answer is nothing notable, the entry doesn’t need a note. If the inspector showed up and found a deficiency, that’s in the log when it happens, not reconstructed from memory two days later.
The log entry is not a narrative. It’s a timestamped fact. Short, specific, captured at the point of work or immediately after.
Why Timing Matters
The most common daily log failure is end-of-day reconstruction. The foreman finishes at 5 PM, pulls out his phone or a notebook, and tries to remember what happened since 6 AM. Eleven hours of work compressed into five minutes of memory.
What comes out is accurate at the broad level — the crew was there, the zone was worked, no major problems — and inaccurate at the detail level. The specific sequence of tasks. The time the inspector arrived. The fact that the pump ran short on Floor 2 and the crew had to hand-place the last section. The subcontractor conflict that got resolved without an RFI.
Those details matter when:
- A change order is disputed and the GC asks when the crew was impacted
- A progress payment is questioned and you need to show what was complete as of a specific date
- An inspection deficiency comes back three weeks later and you need to know exactly what was in place when
- A punch list item is disputed because nobody knows whether the damage was there before or after the finishers came through
The log entry captured at 10:15 AM is a record. The log entry reconstructed at 5 PM from memory is an approximation. For most purposes, the approximation is fine. For the disputes and the documentation requests — which come unpredictably, weeks or months later — the record is what you need.
What Different Trades Should Be Logging
The specific content of a daily log entry varies by trade because the work varies. Here’s what a useful daily log looks like for three trades.
Electrical
Electrical rough-in has clear completion units — a zone is either roughed in or it isn’t. Log entries map to those units:
- Zone complete: “Floor 3 East — conduit run complete. 10:15 AM.”
- Zone started: “Floor 3 West — wire pull started. 2:30 PM. Estimated complete EOD.”
- Inspection: “Pre-rough-in inspection, Floor 2. Inspector Johnson. Passed. 11:45 AM.”
- Issue: “Panel room, Floor 1 — conflict with mechanical duct at grid line C4. RFI submitted. 3 PM.”
The foreman doesn’t need to write sentences. He needs to mark zone completions as they happen and note anything that deviated from the plan. If the day was a normal production day, five log entries cover it. If something went wrong, the log entry captures it at the moment, not from Friday afternoon memory.
Concrete
Concrete logging is pour-centric. Every pour has a start time, an end time, and specific records that go with it:
- Pour start: “Floor 2 elevated deck pour started. 7:02 AM. Truck 1 of 8 on site.”
- Conditions: “Air temp 58°F, wind calm. No admixtures added.”
- Cylinder breaks cast: “4 cylinders cast, 9:30 AM. Lab ticket #4471.”
- Pour complete: “Floor 2 deck pour complete. 11:47 AM. Finish crew on.”
- Issue: “Truck 6 short load — 0.4 CY short. Accepted as placed. 10:22 AM.”
The pour log is the critical daily log for concrete. It’s also the record the structural engineer will ask for when the 28-day break comes back low and everyone wants to know what happened the day of the pour. If it exists in real time, it’s a legal record. If it’s reconstructed, it’s a guess.
Drywall
Drywall logging tracks phase completions by area — because the relay race between hanging, taping, and finishing means the PM needs to know exactly where each phase stands in each zone:
- Phase complete by zone: “Floor 4 West — hanging complete. 3:45 PM.”
- Fire-rated assembly: “Stairwell shaft wall, Level 3 — board type 5/8” Type X, 2-layer, photo taken before close. 1:20 PM.”
- Damage noted: “Level 2 corridor — finish damage in three areas near north elevator. Photo documented. Not crew-caused — other trade. 4:30 PM.”
- MEP clearance: “Floor 5 East — MEP rough-in inspection cleared. Ready to board. 2:15 PM.”
Photo documentation is part of the drywall daily log because the photos are the record that fire-rated assemblies were built correctly and that finish damage predates the punch list walk. The photo and the log entry go together — time and location both captured at the point of work.
What Makes a Log Entry Useful (and What Doesn’t)
A useful log entry is specific enough that someone reading it three weeks later — an owner’s rep, a project manager, an attorney — can reconstruct exactly what happened without asking follow-up questions.
Useful: “Floor 3 East conduit run complete. 10:15 AM. Zone ready for wire pull.”
Not useful: “Good progress on Floor 3.”
Useful: “Pre-pour inspection, Floor 2 elevated deck. Inspector Garcia. Deficiency noted: #4 rebar at grid C3-C4 not tied per drawing. Corrected same day. Re-inspection 2:30 PM, passed.”
Not useful: “Inspector came by, had some comments, resolved.”
The specificity requirement isn’t about writing more — it’s about capturing the right facts. Zone, time, person, outcome. A specific entry takes fifteen seconds to write. A vague entry takes the same time and is useless when you need it.
The Difference Between a Log and a Report
The daily log is raw capture. The daily report is the compiled summary. They serve different audiences:
The log is for the foreman and the PM — internal record of what happened, when, and whether anything deviated from plan. It’s working documentation.
The daily report goes to the GC and sometimes the owner — a formatted summary of crew, work completed, and any issues that need to be communicated up the chain. It’s a communication document.
When the daily log exists, the daily report writes itself. The PM pulls the crew count from the time tracking system, the work completed from the task log, the photos from the documentation feed, and the issues from the foreman’s field entries. The report is a byproduct of the day’s work — not a separate task.
When the daily log doesn’t exist — or exists only in the foreman’s memory — the daily report is reconstructed, which means it’s an approximation, and the source data for disputes and documentation requests doesn’t exist.
In a Tool vs. On Paper
Paper daily logs have one advantage: zero friction. The foreman writes what he wants, when he wants, in whatever format makes sense.
They have two significant disadvantages: the record can’t be searched, and it can’t be shared in real time.
When the GC asks what was complete as of a specific date, finding the answer in a paper log means physically locating and reading through the foreman’s notebooks. If the foreman isn’t available, you may not be able to find it. If the notebook was left on site, you definitely can’t.
A field reporting tool that the foreman uses throughout the day — task completions, photos, notes — creates a searchable, timestamped, location-tagged record that the PM can access without a phone call. The foreman’s workflow is the same: he notes completions as they happen. The difference is that the notes are in the system rather than in a notebook.
The daily log discipline — capture it when it happens, be specific, don’t reconstruct — is the same regardless of paper or tool. The tool just makes the record accessible and searchable when you need it. For what that tool specifically needs to do for the foreman to use it at the point of work — not at 5 PM from the job trailer — see construction foreman app.
What to Start Logging Tomorrow
If the foreman’s current daily log is “what I remember at 5 PM,” the improvement is simple: log zone completions at the time of completion, not at the end of the day.
That one change — task complete when the task is complete, not when the crew wraps — produces a timestamped progress record that didn’t exist before. Everything else (inspection results, issues, photos) can be added gradually as the habit builds.
The record that matters most is usually the one you didn’t think you’d need. Log it when it happens.
See how LogLoon’s field reporting works for specialty contractors, or check the pricing — it’s on the website.