Construction Daily Log Examples (3 Filled-Out Samples)

It's one thing to know what a daily log should contain, and another to see one filled out well. The difference between a log that protects you in a dispute and one that's useless is all in the detail — and the fastest way to learn it is to read real examples side by side.

Below are three filled-out construction daily log examples: a strong one, a weak one for contrast, and a rained-out day (often the most important log you'll ever keep). If you want the blank structure to copy, grab our construction daily log template first, then use these examples to see how to fill it.

Example 1: A strong daily log

Project: Riverside Medical Office Building · Log #: 142 · Date: Tue, Aug 18, 2026 · By: J. Alvarez, Superintendent

Weather: AM 62°F, clear. PM 78°F, clear, wind 8 mph. No weather impact.

Labor:

• Acme Concrete — 6 workers, 48 hrs — north footings
• Bolt Electrical — 3 workers, 24 hrs — underground conduit, Area B
• Self-perform carpentry — 4 workers, 32 hrs — form stripping, Area A

Equipment: CAT 320 excavator (6 hrs), concrete pump (4 hrs), 2 skid steers (5 hrs each). No idle equipment.

Deliveries: 12 CY ready-mix (Acme, 7:10 a.m.); rebar bundle #4 (Steel Co, 9:30 a.m., 2 hrs late — no work impact).

Work completed: Poured 40 CY in north footings F-1 through F-9, 7:15 a.m.–11:00 a.m. Stripped forms in Area A slab. Bolt ran 180 LF of underground conduit in Area B.

Delays/issues: RFI-047 (beam elevation conflict, Grid C-4) still open, holding start of Area C framing. Submitted 8/14, no response yet. Flagged to PM.

Visitors/inspections: City inspector, 1:30 p.m. — footing rebar inspection passed (see photo). Owner's rep on site 2–3 p.m.

Photos: 8 attached — footing rebar pre-pour, pour in progress, inspector sign-off, late rebar delivery.

Why it's strong: Specific quantities and times, named subs and crews, the open RFI documented with its impact, weather logged even though it didn't affect work, and photos tied to the written notes. Six months from now this log answers questions instead of raising them.

Example 2: A weak daily log (what not to do)

Project: Riverside · Date: 8/18

Weather: Nice.

Work: Concrete guys poured footings. Electricians worked. Did some form work.

Notes: Waiting on RFI. Inspector came.

Why it's weak: No quantities, no times, no headcounts, no hours. "Waiting on RFI" doesn't say which one, since when, or what it's holding up — so it proves nothing in a delay claim. "Inspector came" doesn't record the result. There are no photos. This log documents that a day happened, but none of the facts you'd actually need later. In a dispute, it's close to worthless.

Example 3: A rained-out day (the one people skip)

Project: Riverside · Log #: 148 · Date: Mon, Aug 24, 2026 · By: J. Alvarez

Weather: AM 59°F, heavy rain, 1.4 in. by noon (per on-site gauge and NWS station KXYZ). Wind 22 mph. Site conditions unworkable — standing water in excavation.

Labor: Acme Concrete — crew of 6 sent home at 9:30 a.m. after 1.5 hrs (site safety). Bolt Electrical — did not mobilize (notified 6:45 a.m.).

Work completed: No production work. Crew pumped water from north excavation 8:00–9:30 a.m.

Delays/issues: Full weather day. North footing pour scheduled for today pushed to 8/26 pending excavation dry-out and re-inspection. Documented as excusable delay per contract §8.3.

Photos: 5 attached — flooded excavation, rain gauge reading, empty site, standing water at footings.

Why it matters: This is the log that wins a time extension. It records the exact rainfall, the source, the crews affected, the specific work pushed, and the contract clause — with photos. Skip the rained-out day and you lose the documentation for the delay it caused. For more on this, see documenting weather delays in construction.

What the strong examples have in common

• Numbers, not adjectives — quantities, headcounts, hours, times.
• Named parties — which sub, which crew, which inspector.
• Issues with impact — not just "RFI open" but which one, since when, holding what.
• Photos tied to words — every claim has an image behind it.
• Every day logged — including slow and rained-out days.

Make every log look like Example 1

The strong example takes effort to write by hand — which is why most field logs end up looking like Example 2. BuildLog structures every entry so the detail gets captured by default: it prompts for labor and equipment hours, pulls weather automatically, timestamps every photo, and attaches images to the day. The result is a log that reads like Example 1 without the extra half hour. It works offline and has a free tier.

Frequently asked questions

What does a good construction daily log look like? Specific and complete: quantities, crew headcounts and hours, named subcontractors, weather, any delays with their impact, inspection results, and photos tied to the written notes — like Example 1 above.

Should I log a day when no work happened? Yes — especially then. A rained-out or delayed day is often the most valuable log you keep, because it documents the cause of a delay you may later need a time extension for.

Where can I get a blank version? Use our free daily log template, or skip the spreadsheet with a purpose-built app.

---

Want every entry to look like the strong example? Start a free construction daily log with BuildLog — it captures the detail for you.