The Superintendent Daily Log: What to Record and How to Keep It Up on a Busy Job
A superintendent daily log is the general contractor's running record of the job for a single day: weather, every company on site with headcount and hours, work in place by area, delays and their causes, inspections and visitors, safety events, instructions given or received, and decisions made. It backs up the formal daily report, feeds the schedule and pay app reviews, and is often the first document pulled in a dispute. The best logs are written in short entries through the day, not reconstructed at night.
For a general definition of a daily report and why it matters, see what is a construction daily report.
What belongs in a superintendent daily log
The superintendent sees the whole job, so the log covers more than any single sub's report.
Site conditions
- Weather at start, midday and end of shift
- Ground and access conditions (mud, snow, blocked gates)
- Utility outages and site logistics changes
Manpower and hours by company
- Every subcontractor and sub-tier on site, headcount and hours
- General contractor self-perform crews
- Companies that were scheduled but did not show
Work in place
- Progress by area and schedule activity
- Planned versus actual where they differ
- Work started, completed, or covered up that day
Coordination and constraints
- Trade conflicts and stacking
- Open RFIs and submittals holding work, with day counts
- Material shortages and late deliveries
Inspections, tests and visitors
- Inspector, result, and any corrections required
- Testing agency activities
- Owner, architect and engineer visits
Direction and decisions
- Verbal instructions from the owner or design team, and who gave them
- Instructions you gave to subs
- Decisions reached in meetings
Safety
- Pre-task plans collected
- Incidents, near misses and corrective actions
A daily routine that keeps the log current
| Time | Log entry |
|---|---|
| Before start | Weather, site conditions, expected crews |
| 7:00 AM huddle | Pre-task plans, crew counts, today's plan |
| Mid-morning walk | Headcount by company, work started, problems spotted |
| After meetings | Decisions, direction, open items |
| After inspections | Result, corrections, photos |
| Mid-afternoon walk | Progress, delays, deliveries |
| End of day | Tomorrow's plan, final headcount and hours, sign off |
Five or six short entries beat one long one written at 6 PM. Memory fades fast, and the details that matter in a dispute (times, names, quantities) are the first to go.
Sample superintendent daily log entry
Tuesday, Report #117, Westgate Senior Living, Building 2 6:45 AM. 41 F, frost on deck, clear. East gate blocked by city water crew until 9:00 AM; deliveries rerouted to north gate. 7:00 AM. Huddle. Frost on decks flagged; sweep and salt before access. Pre-task plans received from 6 of 7 subs; Ridgeline Framing PTP missing, foreman submitted at 7:25 AM. 9:30 AM. Walk. Ridgeline 9, Northline Electric 6, Summit Mechanical 5, Delta Drywall 8, Apex Fire 3, general contractor 3. Apex scheduled 5, 3 on site. 10:15 AM. OAC meeting. Owner approved alternate LVT at corridors pending price. Architect to answer RFI 064 by Thursday. 11:40 AM. City inspector passed Level 3 framing, units 301 to 308. Units 309 to 312 corrections: missing hold-downs at 3 locations. Photos attached. 2:30 PM. Delta Drywall stopped Level 2 east corridor; Summit still hanging duct. Third day of this conflict. Delta moved to units 205 to 208. 3:45 PM. Final count 34 workers, 272 hours. Tomorrow: Level 3 hold-down corrections, Apex adding 2, Delta continues Level 2 units.
Using the log for more than record keeping
Lookahead planning. The "tomorrow" line and constraint entries are the raw material for a three-week lookahead.
Manpower conversations. A week of logs showing Apex at 3 of 5 scheduled workers is a factual basis for a manpower request. See construction manpower tracking.
Delay documentation. Daily counts of open RFIs and repeated conflicts build the record you need if a delay claim comes later.
Common mistakes
- Writing "subs on site" without names and counts
- Recording a delay once and never again
- Mixing opinions into the record
- Copying yesterday's log forward and changing a few words
- Waiting until Friday to fill in the week
What PMs and owners look for in the superintendent's log
When a PM or owner's rep reads the log, they usually want three things fast: who was on site and whether crews matched the plan, what got done against the lookahead, and what is at risk this week. Putting a short summary at the top of each day's log, with total workers, the biggest progress item, and the biggest risk, saves everyone time and makes the log more useful than a long narrative.
How Cascade keeps the superintendent log current
Superintendents and foremen already text all day. Cascade is SMS-first field intelligence for general contractors and subcontractors: superintendents and foremen text in their day, along with their subs, and Cascade builds the daily report and the running record behind it. Coverage: Daily reports, manpower and hours by sub, photos, toolbox talks, pre-task plans (JHA), safety incidents and corrective actions, project + schedule planning, automatic sub reminders, analytics and plain-English answers. Ask "how many Apex workers were on site last week?" and get a plain-English answer.
Subcontractor access is free, and general contractors see 95%+ sub daily report compliance. Onboarding and integration are free, with a one-month pilot on the general contractor plan and no contract lock-in. We beat Raken, Procore and ACC on price, guaranteed. See why Cascade.
Frequently asked questions
What is the difference between a superintendent daily log and a daily report?
Many firms use the terms interchangeably. Where they differ, the daily report is the formal record sent to the PM or owner, and the superintendent daily log is the running record behind it: notes, conversations, decisions and observations captured through the day.
Is the superintendent daily log a legal document?
It is a business record that can be requested in a dispute, so treat it as one. Keep it factual, dated and complete, and do not edit old entries. If something needs correcting, add a dated correction.
Should superintendents include sub manpower they did not count themselves?
Yes, but note the source. Record the headcount you observed and the headcount the sub reported. Gaps between the two are worth knowing about.
How do superintendents keep the log current on big jobs?
Capture entries during the day in short bursts, right after a walk, a meeting or an inspection, instead of writing everything at the end of the shift. Phone notes, voice-to-text or texting entries to a reporting system all work better than memory.