The daily field report is the most consistently undervalued document in construction. On most projects it is filled out grudgingly at the end of a long day, with vague entries like "grading" or "installed pipe." Then a delay claim or payment dispute arrives, and everyone discovers that the project record cannot support the narrative. The report habit you build now determines whether you can defend yourself later.
What are the required elements of a contractor daily field report?
A complete contractor daily field report must include: project identification (name, number, location); date and day of week; weather conditions with temperature range and precipitation; labor — crew members by name or classification and hours worked; equipment — each piece on site, hours operating, and what activity it was performing; work performed — specific description of work accomplished by location (station, area, building section) and activity type; materials received or placed; subcontractor work performed; site visitors and inspection results; delays or disruptions with cause, duration, and crew affected; verbal directions or changes from the owner, engineer, or inspector; safety incidents and corrective actions; and signature of the reporting superintendent with date and time.
The work description is where most daily field reports fail. Entries like "grading" or "installed pipe" are useless for claims or payment support — they tell a reviewer nothing about the scope, location, quantity, or difficulty of the work.
Compare these two descriptions of the same day's work:
Weak Description (Useless)
"Grading in the north section. Crew of 5. Two dozers and a scraper."
Strong Description (Defensible)
"Rough grading station 10+00 to 22+50 on the north service road alignment. Cut material from approximately 0.5 to 1.2 ft per stake — material is native clay, wetter than optimum, requiring two passes per area. Moved approximately 1,800 CY loose. Encountered soft subgrade at station 14+75 to 16+00 — material proof-rolled at 0930 with loaded belly dump, failed (5+ inches of deflection). Engineer notified at 1015 (John Smith, per phone log). Area staked off pending direction. Lost approximately 2.5 hours of dozer time at this area. Compaction testing performed by ABC Testing at Stations 10+00, 14+00, 18+00, and 22+50 — all pass at 95% per test reports attached."
The strong description takes three minutes longer to write and provides complete protection in a claim — it documents quantity, material condition, a differing site condition, notification to the engineer, and the time impact.
Delays are where the daily field report earns its keep. A delay that is properly documented — cause, duration, crew and equipment affected, notification provided — is a recoverable event. A delay that is not documented is generally not recoverable in a claim.
Required elements for delay documentation in a daily field report:
| Common Omission | Claim Impact |
|---|---|
| Weather not recorded | Cannot prove weather-related delays without contemporaneous record; owner challenges delay claims |
| Equipment hours not recorded | Cannot support equipment idle time claims or standby rate billings |
| Verbal instructions not documented | Owner denies giving verbal direction; contractor has no record of authorization |
| Differing site conditions not noted same day | Claim appears manufactured if first documented weeks after the event |
| Crew size omitted or rounded | Labor cost claims cannot be verified; owner disputes crew count |
| Inspector visit not noted | Cannot prove work was inspected and accepted on a given date |
| Subcontractor work not described | Subcontractor schedule claims cannot be supported by prime contractor record |
Digital daily reports offer four advantages over paper:
Sitemark links field documentation — grade shots, inspection records, photos, and daily logs — into a timestamped project record that supports payment applications and resolves disputes. Start free.
Start Free Trial