On this page
At the end of a long day, the daily log is the last thing a superintendent wants to do. Weather, manpower, work performed, a few notes. It feels like paperwork for the sake of paperwork, filed and forgotten unless something goes wrong.
Then something goes wrong. A delay claim, a disputed change order, a back-charge a sub won’t accept, a payroll question on a prevailing wage job. And suddenly everyone wants to know what the daily log says for March 14th.
The daily log is a financial document. It’s just filed in the wrong drawer.
What the log already knows
A good daily log records facts that most of the financial system depends on:
| Log entry | Financial question it answers |
|---|---|
| Manpower by trade and company | Is the sub’s billed progress consistent with their crew size? Is our labor posting to the right job? |
| Hours by cost code or activity | Is labor productivity on track with the estimate? |
| Equipment on site and hours | Are equipment charges and rentals correct? |
| Deliveries | Did the material on that invoice arrive? Is it installed or stored? |
| Work performed | Does physical progress support the percent complete we’re billing? |
| Weather and delays | Do we have a basis for a time extension or a delay claim? |
| Visitors, inspections, directions | Who told us to do what, and when? |
| Conditions found | Is there a change event we haven’t recorded? |
Every row on that list feeds a number accounting reports on: job cost, cost to complete, sub payments, change orders, billing. The log is where the fact enters the company. Everything after is a copy.
Four places the log becomes money
Change orders. On Riverside Medical, CO #14 started as a daily log entry: missing fire dampers at rated penetrations in the L3 corridor, three photos. That entry is the earliest evidence of when the condition was found, which matters for contractual notice requirements and for showing the owner the condition was hidden. When the owner’s rep asks “when did you know about this?”, the answer is a dated log entry, not someone’s recollection. That’s why change events should start from the log.
Time and materials. Work done on a T&M ticket is only billable if the hours, crew and materials are documented and, usually, signed by the owner’s representative. If the daily log shows a crew of six on that work and the T&M ticket shows eight, expect a dispute.
Sub payments and back-charges. A sub bills 60% complete on a scope. The log shows their crew on site three days out of the last ten. That’s a conversation worth having before the payment, and it’s part of the progress leg of a construction three-way match. If a sub leaves a mess another trade has to clean up, the log entry is the basis for a back-charge.
Delays and claims. Weather days, late owner decisions, inspection holds, stop-work directions. A delay claim is built from dated, contemporaneous records, and the daily log is usually the most important one. Records written at the time tend to carry more weight than reconstructions written months later.
Why logs fail as financial records
If the log is so important, why does it so often let people down when they need it? A few patterns:
- Written at the end of the day from memory, so details blur. Photos with timestamps help more than paragraphs.
- Free text only. “Mech crew working L3” is a fine note and a useless data point. Crew counts, company and area as structured fields make the log searchable and comparable.
- No link to anything. The log mentions the dampers, but the RFI, the change event and the CO don’t point back to it. A year later, nobody can find the entry.
- Filed, not used. If nobody in the office reads logs until there’s a dispute, the super learns that logs don’t matter, and quality drops.
- Retyped. The super writes the log, the PE retypes the relevant part into an RFI, the PM retypes it into the change order. Each retype loses detail.
What a financially useful log captures
You don’t need a longer log. You need a more structured one:
- Crew by company and trade, with counts. Structured, not free text.
- Work performed by area, tied to the same areas the schedule and cost codes use where practical.
- Photos with location and time attached to the entries they support.
- Deliveries with the supplier and, ideally, the PO they relate to.
- Delays and their cause, with start and end times.
- Directions received: who, what, when. Especially verbal ones.
- Conditions found that might be a change, flagged as such.
Why the connection matters
The value isn’t the log. It’s what happens to it. A log entry that becomes the first step of an RFI, a change event and a change order carries its evidence all the way to the pay app. A crew count that sits next to the sub’s billed progress makes the progress check quick. A delivery that links to its PO makes the receiving leg of the match automatic. The facts are entered once, by the person who saw them.
What we’re building
In os.construction, a daily log entry is a record on the same job as the RFIs, change orders, commitments and cost. The daily log lives on the same project as RFIs, change events, photos and T&M tickets, in the web app today, so crew counts and deliveries are available to the office the moment they’re logged. Mobile and offline capture are planned.
Projects is live. If your daily logs only matter when there’s a dispute, start a free trial and run your next daily log in it.
Share this article