What a daily log actually is
A construction daily log (also called a daily report, daily field report, or jobsite diary) is a dated record of what happened on a project on a given day. Made every working day, it captures the conditions, labor, equipment, materials, and events on site — and it is created contemporaneously, meaning at the time the work happened, not reconstructed weeks later.
That last point is what gives a daily log its power. A note written the day work stopped because the slab wasn't ready carries weight; the same fact "remembered" three months later in a dispute does not. Courts, arbitrators, and project owners treat contemporaneous daily records as far more credible than after-the-fact recollection, which is precisely why disciplined contractors keep them every single day, even on the quiet ones.
Why daily logs matter more than contractors think
Daily logs do four jobs at once, and most contractors only consciously use them for the first one.
- Legal and contractual record. When there is a dispute over delays, change orders, defects, or payment, the daily log is the primary evidence of what conditions existed and what work was performed. Many subcontract and prime contract forms explicitly require daily reports.
- Delay documentation. If a site was rained out, the slab wasn't cured, an inspection was late, or another trade wasn't finished, the daily log is where you record the delay, its cause, and who it affected — the foundation of any legitimate time-extension or delay claim.
- Time-and-materials (T&M) backup. On T&M and cost-plus work, the daily log of labor hours, equipment, and materials is what you bill from and what the owner audits against. No log, no defensible invoice.
- Progress tracking and job costing. Logged crew size, hours, and quantities placed each day tell the office whether the job is on pace and whether the labor matches the bid — before the loss shows up in the final numbers.
What belongs in every daily log
A complete daily log answers the questions someone will ask months later when they were not there. The core fields are consistent across the industry:
- Date, project, and who wrote it. Obvious, and the first thing that is missing on weak logs.
- Weather. Temperature, conditions, and especially anything that affected work — rain, wind, heat, cold. Weather is the single most common documented cause of delay.
- Crew on site. Who was there, from your company and from subs, and how many of each. Headcount drives both labor cost and the credibility of the rest of the log.
- Equipment on site. Owned and rented machines present and in use — the backbone of equipment cost tracking and idle-equipment delay claims.
- Work completed. What got done, where, and how much — described concretely (locations, quantities) rather than "worked on the building".
- Quantities / production. Units installed, yards placed, linear feet run — the numbers that turn a log into a progress record.
- Delays, issues, and notes. Anything that slowed or stopped work, plus visitors, inspections, deliveries, safety incidents, and instructions received.
- Photos. Dated images of conditions and completed work — covered in depth in the jobsite photo guide.
Paper logs and where they fail
The traditional daily log is a carbon-copy book in the foreman's truck. It works, barely, and it fails in predictable ways: the book gets filled out Friday for the whole week from memory; entries are illegible; photos live on a phone disconnected from the report; the office never sees the log until something has already gone wrong; and when a dispute hits, half the days are blank.
The deeper problem is that paper logs are not timestamped in any way a third party trusts. A handwritten "6/12" proves nothing about when it was actually written. A digital log created on site with an automatic timestamp and GPS-attached photos is contemporaneous in a way a carbon book never can be — which is exactly the property that makes a daily log worth keeping.
In Vexor
In Vexor, the daily log lives inside the job itself rather than in a separate book. The foreman opens the job on their phone, captures weather, crew on site, equipment, work completed, quantities, and any delays or notes, and attaches photos — all in one entry. Each log is automatically timestamped, so it is genuinely contemporaneous, and it is visible to the office and GC the moment it is saved.
How to make daily logs a habit, not a chore
Logs only protect you if they exist every day, so the system has to be fast enough that the foreman actually does it. The contractors who keep good logs share a few habits: they log on site before leaving (not from the couch that night), they keep the entry short but complete, they photograph everything, and they make one person per crew clearly responsible for the entry every day.
The other half is the office actually reading them. A daily log that nobody reviews is just storage; a log the PM reads each morning catches a brewing delay, a missing sub, or a slipping production rate while there is still time to act. Treat the log as a daily communication loop between field and office, and it pays for itself long before any dispute.
In Vexor
Because Vexor logs are timestamped and visible to the office and GC as soon as they are saved, the field-to-office loop is automatic — the PM sees today's conditions, crew, and production the same day, not at the end of the month. Logs sit in the same workspace as the schedule, time tracking, photos, and invoicing, so a logged delay or crew count lines up with the hours and the job cost without re-keying. It works on iOS and Android and is offline-capable, so a foreman on a dead-signal site still captures the entry on time and it syncs when they reconnect.