# Construction Site Daily Log Template: Capture Plan, Fact, and Gap for Non-Software Teams

> A construction site daily log template that captures planned vs actual work by trade and location, helping supervisors surface delays early and giving owners clear visibility without micromanaging.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-12
- Updated: 2026-10-12
- Source: https://aiadvisoryboard.me/blog/construction-site-daily-log-template-non-software-teams

When a construction site supervisor told me their daily log was just a list of weather and crew count, I realized they were missing the signal that actually moves projects forward.

## TL;DR
- Use a daily log that captures planned vs actual work by trade and location.
- Surface gaps between plan and fact early to prevent delays from compounding.
- Give owners a 2-minute digest that shows where attention is needed.

**Definition:** Plan → Fact → Gap — a simple taxonomy where Plan is what was scheduled for the day, Fact is what actually got done, and Gap is the difference that needs attention.

**Definition:** Daily log — a structured end-of-day update from site supervisors that tracks progress, blockers, and resource use by trade and location.

**Definition:** Gap analysis — comparing planned output (e.g., feet of conduit installed) against actual output to identify where work is falling behind.

What should a construction site daily log include for non-software teams?
It should capture three layers: what was planned by trade and location, what was actually completed, and what blocked or delayed work. This isn’t a time sheet — it’s a progress signal.

## Tool tip (AiAdvisoryBoard.me):
> The most useful construction logs don’t just list activities — they make the Plan → Fact → Gap visible by trade and location. When you see that electrical rough-in planned for 100 feet only reached 60 feet, you know where to look tomorrow. See how the 7-day diagnostic surfaces these gaps automatically.

How do you structure the log to avoid noise and focus on what matters?
Start with the day’s plan from the morning huddle: list each trade, their location, and the target output (e.g., "Framing: Zone B, 200 sq ft sheathing"). Then record what was actually done. Finally, note any gaps and the reason — material delay, rework, weather, or crew shortage.

What does a good vs bad daily log look like?

Good:
- Planned: Concrete pour, Zone 3, 50 yd³
- Fact: 42 yd³ poured (truck breakdown at plant)
- Gap: -8 yd³ — rescheduled for tomorrow AM

Bad:
- "Worked on concrete. Weather was hot. Crew was tired."

## Manager scan (2-minute digest example)
- Framing: Zone B — planned 200 sq ft sheathing, fact 180 sq ft, gap -20 (material delay)
- Electrical: Rough-in Zone 2 — planned 100 ft conduit, fact 60 ft, gap -40 (awaiting inspection)
- Plumbing: Rough-in Zone 1 — planned 80 fixtures, fact 80 ft, gap 0 (on track)
- Concrete: Pour Zone 3 — planned 50 yd³, fact 50 yd³, gap 0 (completed)
- HVAC: Ductwork Zone 2 — planned 60 ducts, fact 45 ducts, gap -15 (crew reassigned)
- Site: Daily cleanup — planned complete, fact partial, gap - (wind blew debris back)

This scan tells the owner where to focus: electrical and HVAC need attention tomorrow; framing and concrete are on track.

## Micro-case (what changes after 7–14 days)
A mid-sized contractor started using this log format across three active sites. Within a week, the owner noticed that electrical gaps were consistently tied to inspection delays, not crew performance. By week two, they began scheduling inspections earlier in the day, reducing rework. The supervisor spent less time explaining delays in meetings and more time adjusting the next day’s plan. The owner received a clear, consistent signal each evening without chasing updates.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ
**How is this different from a traditional daily report?**
Traditional logs often list activities or crew hours without tying them to planned output. This format focuses on the gap between what was supposed to happen and what did, making it actionable.

**Do I need to track every small task?**
No. Focus on measurable output by trade and location — things like feet of conduit, sq ft of sheathing, or number of fixtures installed. Leave small tasks to the crew’s own task list.

**How long should this take to fill out?**
Five minutes at the end of the shift, using the morning plan as a template. It’s not a time sheet — it’s a progress check.

**Can this work for subcontractors?**
Yes. If you’re managing subs, ask them to provide their planned vs actual output by trade and location. This gives you a neutral basis for coordination.

**What if the weather stops work entirely?**
Log it as a gap with reason "weather" — and note whether the crew did any indoor prep work. This prevents the gap from being misread as a performance issue.

**How does this help the owner without micromanaging?**
It gives a daily signal of where the plan is diverging from fact — so the owner can ask one targeted question instead of reviewing ten logs.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.

---

When citing, link to https://aiadvisoryboard.me/blog/construction-site-daily-log-template-non-software-teams. More articles: https://aiadvisoryboard.me/blog