A daily log (or daily report) is the official day-by-day record of what happened on a jobsite. A good one lists weather, crew counts by trade, work performed by area, equipment on site, deliveries, inspections, safety incidents, visitors, delays, and any conditions that differ from the documents, usually with photos.
Why it matters
When there is a dispute, the daily log is often the best evidence anyone has. It supports delay claims, change orders, T&M tickets, back-charges and insurance claims. It also feeds production tracking: crew hours against work in place tell you whether a cost code is trending over long before the invoice arrives.
Worked example
Illustrative: on Riverside Medical Center, the superintendent’s log for the day reads: “Level 3, grid C/4: rated wall framed, duct penetrations installed, no fire dampers shown or on site. Photos attached. RFI to be issued.” That entry dates the discovery, which supports RFI-212, the change event and eventually CO #14 at $86,400.
Common mistakes
- Copy-pasting yesterday’s log so entries stop meaning anything.
- Recording “no issues” on a day a crew stood around waiting.
- Logging by memory at the end of the week instead of daily.
How os.construction handles it
We’re building the daily log as a mobile-first record on the same data core, so a logged condition can open an RFI or change event in one step, with the photo and timestamp attached.