Project management

How to write a construction daily log

Write a construction daily log the same day, every day, with facts only: weather, manpower by company, work performed by area, deliveries, visitors, problems, and photos, so the log can prove what happened if the job ends in a dispute.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

A construction daily log is a dated record of what happened on site that day. To write a good one, fill it out before you leave the site, use the same sections every day, and record facts you saw rather than opinions: weather and site conditions, each company on site with headcount and hours, work completed by area, equipment, deliveries, inspections, visitors, safety events, delays, and any direction given or received. Attach photos with the date and location. Keep it short enough that you will actually do it every day, and specific enough that a stranger could read it in two years and understand the day.

That stranger may be an arbitrator. When a schedule or cost dispute comes up, daily logs are often the best contemporaneous record of who was on site, what was blocking them, and when the contractor first raised a problem.

What to include in a construction daily log

Daily log sections and what to write
SectionWhat to recordExample
WeatherConditions at start, midday, and end; rain, wind, temperature; site conditionsRain 6 a.m. to 10 a.m., site muddy, no exterior work until 11
ManpowerEach company, trade, headcount, hoursABC Drywall, 6 hangers, 8 hrs
Work performedActivity, location, quantity where usefulHung board level 2, grid C to F, east side
EquipmentMajor equipment on site and whether it workedScissor lift down 2 hrs, hydraulic leak
DeliveriesMaterial received, supplier, condition, shortagesDoors from supplier, 3 of 42 damaged
Inspections and testsWho, what, resultCity framing inspection level 1, passed
VisitorsOwner, architect, inspectors, sales repsArchitect walked level 2, 1 to 2 p.m.
SafetyToolbox talk topic, incidents, near misses, corrective actionsTalk on ladder use; no incidents
Delays and problemsWhat stopped work, who was affected, what was donePlumber idle 3 hrs waiting on RFI 14 answer
Direction and changesVerbal or written direction from anyone, with nameOwner rep asked to relocate outlet at reception

How to write the daily log in 6 steps

  1. Use one format for every job. A standard daily report template or app form means nobody forgets a section and logs from different supers can be compared.
  2. Capture notes during the day. Jot manpower at the morning huddle, snap photos as work happens, and note times when something stops work. Writing it all from memory at 5 p.m. is where details get lost.
  3. Write facts, not feelings. "Electrician arrived 10:15 a.m. with 2 of the 4 workers scheduled" is useful. "Electrician was late again and useless" is not, and it will be read aloud in a deposition.
  4. Tie problems to the schedule. When something stops work, say which activity was affected, for how long, and whether it is on the critical path. Reference the RFI, submittal, or change number.
  5. Record direction and notice. If an owner rep, inspector, or architect tells the crew to do something different, write who said it, what they said, and when. Then follow up in writing. Many contracts require prompt written notice of changes and differing conditions.
  6. Sign and submit the same day. A log finished three days later is less credible and less complete. Lock entries after submission and add corrections as dated amendments.

Why the daily log matters for notice and claims

Contracts usually tie your right to extra time or money to giving notice on time. On federal jobs, for example, the differing site conditions clause, FAR 52.236-2, requires the contractor to give written notice promptly and before the conditions are disturbed, and says no adjustment will be allowed unless that notice was given (the contracting officer can extend the time). A daily log is not the notice itself. But a log entry that records the condition, the time it was found, and the photo is the evidence that backs up the letter you send the same day.

The same goes for weather delays, owner-caused stoppages, and late information. If the log shows rain each day with exterior work stopped, a time extension request is a matter of counting. If the log says "weather" with no detail, it is a negotiation. For more, read how to document construction delays for claims.

Sample daily log entry

Here is an example entry for a fictional two-story medical office building, day 64.

  • Weather: Clear, 48 degrees at 7 a.m., 61 at 2 p.m., light wind. Site dry.
  • Manpower: GC 3 (super, 2 laborers, 8 hrs). Framing sub 7 (8 hrs). Plumbing sub 2 (8 hrs, idle 1 to 4 p.m., see delays). Electrical sub 4 (8 hrs).
  • Work performed: Framing completed interior walls level 2, rooms 201 to 214. Electrical rough-in level 1, exam rooms 101 to 106. Plumbing rough-in level 2 restrooms started.
  • Deliveries: Hollow metal frames, 38 received, 2 bent (photos 112 and 113), supplier notified 11:20 a.m.
  • Inspections: None.
  • Visitors: Owner rep J. Lee, 9 to 10 a.m., walked level 1.
  • Safety: Toolbox talk on silica dust control, 16 attended. No incidents.
  • Delays: Plumbing stopped at 1 p.m. at level 2 restroom wet wall. Waste line conflicts with beam at grid D4. RFI 22 sent to architect 1:40 p.m. Plumbing crew moved to level 1 at 4 p.m. Critical path not affected today.
  • Direction: Owner rep asked for an added data outlet at nurse station 1. Told rep it requires a change order. Change request emailed 3:15 p.m.

Mistakes to avoid

  • Blank or copy-paste days. "Same as yesterday" is not a record. A log that never changes looks unreliable.
  • Leaving out subs' headcount. Manpower by company is what proves a sub under-staffed the job or that your crew was stacked waiting on someone else.
  • Skipping the bad news. A log that only shows progress is useless when you need to prove a delay.
  • Untagged photos. A photo without a date, location, and short caption is hard to use later.
  • Opinions about people. Stick to what happened. Discoverable records should be professional.
  • Logs nobody reads. The PM should review logs weekly and pull out RFIs, changes, and delays before they go stale.

Templates, terms, and tools

Start with the construction daily report template. Pair it with the RFI log and change order log so items noted in the field get tracked to closure. Related terms: daily report, field report, delay claim, and toolbox talk. For automation ideas, see how to automate construction daily reports.

Smart Business Automator keeps daily logs, photos, and manpower attached to each job and can summarize a week of logs for the PM, flagging delays and owner direction that need follow-up. See construction workflow automation.

Frequently asked questions

Who writes the construction daily log?

Usually the superintendent or site foreman. Subcontractors often keep their own logs too, and many general contractors require subs to submit a daily report so the GC log can be checked against it.

Is a daily log the same as a daily report?

The terms are often used interchangeably. Some companies use daily log for the superintendent's internal record and daily report for the version sent to the owner or architect.

How long should a daily log entry be?

Long enough to cover every standard section with facts. On a quiet day that can be half a page. On a day with a delay, an incident, or a change, write more and attach photos.

Can daily logs be used as evidence?

They are commonly used in disputes, claims, and litigation as records made at the time of the events. That is why they should be dated, factual, written the same day, and not edited after the fact without a dated amendment.

How long should contractors keep daily logs?

Keep them at least as long as your contract, warranty, and claim periods run, and longer if your state's statute of repose or your insurer requires it. See construction document retention guidance for your business.

Sources

  1. Acquisition.gov: FAR 52.236-2 Differing Site Conditions
Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment