Every delay claim, change order fight, and back-charge dispute eventually comes down to the same question: what actually happened on site that day? The party with a contemporaneous written record usually wins that argument. The party reconstructing from memory usually eats the cost. Your daily report is that record — if your foremen write it like one.

The short version

  • A daily report written the day of the work, by the person who was there, is the most reliable evidence of field conditions a sub can produce.
  • Write one every working day, including uneventful ones — a gap on the day something went wrong looks like after-the-fact fabrication.
  • The two non-negotiable fields: manpower by classification and delays with names, places, and durations. Add work by location, directives received, and timestamped photos.
  • Facts, not opinions. “Super directed crew to relocate panel; no RFI issued” holds up; editorializing gets the whole record discounted.
  • The PM’s job is to read reports daily and convert delay entries into contract notice while the notice window is still open.

Schedules get revised, emails get argued about, and memories fade fast — but a daily report written the day of the work, in the foreman’s own words, is hard to impeach. Arbitrators and judges treat contemporaneous records as the most reliable evidence of field conditions. A year from now, “the GC’s plumber blocked the corridor for three days” is an assertion. Three daily reports naming the dates, the corridor, and the crew standing around is proof.

That only works if the reports exist for every working day — including the uneventful ones. A gap in the record on the day something went wrong looks like it was written after the fact, even when it wasn’t.

What every daily report needs

  • Date, project, weather, and site conditions. Weather matters even for interior trades — it drives the GC’s schedule and everyone’s access.
  • Manpower, by name or count and classification. Who was on site, doing what, for how many hours. This is the number every delay and acceleration claim gets priced from.
  • Work performed, by area. Not “continued rough-in” — say where: “rough-in, Level 2 north corridor, rooms 201–208.” Location is what lets you tie work to the schedule later.
  • Delays and interferences, in plain factual language. Who or what stopped you, where, for how long, and what your crew did instead. Name the trade or party — “waiting on framing inspection, moved crew to Level 3” beats “lost time.”
  • Directives and verbal instructions. Any time the GC or owner’s rep tells your crew to do something not in your scope, write down who said it, what they said, and when. This entry is often the only evidence a directed change happened.
  • Deliveries, equipment on site, and visitors. Inspectors, owner’s reps, and the GC’s walkthroughs all belong in the record.
  • Photos. Timestamped photos tied to the report entry are the cheapest dispute insurance there is. Progress shots of covered-up work — in-wall, underground, above-ceiling — are the ones you’ll wish you had.

How to write entries that survive scrutiny

  • Facts, not opinions. “GC’s superintendent directed crew to relocate panel; no RFI issued” will hold up. “GC is disorganized and keeps jerking us around” will get the whole report discounted. Write what happened; let the facts carry the argument.
  • Same format, every day. A consistent template — filled in daily, even when the answer is “no delays” — is what makes the record credible as a business practice rather than a claims-preparation exercise.
  • Written by the person who was there. The foreman who watched it happen, the day it happened. A PM cleaning up entries a week later turns evidence into hearsay.
  • Don’t sanitize problems. Some foremen soft-pedal delays to keep the peace with the GC’s super. The daily report is not the place for diplomacy — that’s what the cover email is for.

The habit that makes it stick

The best daily report system is the one your foremen will actually use at 3:30 with a truck to load. Keep the template short, make manpower and delays the two non-negotiable fields, and have the PM read the reports — daily, not at month-end. A foreman whose reports get read writes better reports; one whose reports vanish into a folder stops writing them. When a delay entry shows up, the PM’s job is to convert it into notice under the contract while the window to give it is still open. A perfect field record does nothing if the letter never goes out.