A daily log is a record of what happened on the construction site that day: who was there, what got built, what the weather was, and what blocked progress. Daily logs fail to get filled out for one reason. They take too long. The fix is not exhortation or quarterly retraining. The fix is making the log a 90-second task that completes from the truck before the field lead drives off the site.
What a daily log is for
The log earns its keep in three places:
- Disputes. When an owner asks why drywall slipped two days, a log entry from the relevant week showing rain and a sub no-show ends the conversation in five minutes. No log, the conversation lasts an hour and ends without resolution.
- Insurance and warranty. A claim that a crawlspace was wet at framing inspection is supportable with a photo and a weather record from the day in question. Without contemporaneous logs, claims rely on memory and memory is contested in court.
- Lender draws. A draw package improves dramatically when accompanied by a series of dated, photo-attached daily logs covering the period billed. The lender stops asking for progress photos because the progress photos are already attached to the log entries.
The four fields that matter
Every log we have seen fail had ten or twelve required fields. Every log we have seen succeed had four. The four:
- Site and date. Pre-filled from the project the user opens. Zero typing.
- Crew on site. A multi-select of the subs scheduled for the day, with a free-text override. The field lead taps the trades that showed up. Five seconds.
- Hours worked. A single number. If the crew was on site for a normal day, the field lead taps a default of 8. Variance is rare and easy to type.
- One sentence on what got built. Free-text, optional but almost always filled. Examples from the field on 926 Stratford: “Framing crew topped out the second-floor walls. Sheathing tomorrow.” “Plumber roughed in the master bath. Inspection scheduled Thursday.”
These four fields take ninety seconds. Everything else is optional. The moment a daily log requires the field lead to think, it stops getting filled out.
What to skip
The fields we have removed from log templates and never missed:
- Detailed crew hours per person. Unless the project bills time and materials, per-person hours are payroll’s problem, not the log’s.
- Equipment used. If the equipment shows up in a daily rental log or an internal asset tracker, do not duplicate it in the daily log.
- Material deliveries. Capture these on the transaction or the receiving record where they belong. A copy in the daily log is data drift.
- “Visitors” field. Owner walkthroughs, inspector visits, and supplier reps already have their own records (inspection, sales rep notes). The daily log is for the crew.
Photos and weather
Photos and weather are the two fields where automation pays for itself. Weather pulls from the project address and a public forecast API; the field lead reviews and edits if the on-site reading is different. Photos upload from the phone the field lead is already holding, geotagged and timestamped, attached to the log without a separate upload step.
The minimum is three photos a day: two of completed work, one of any unexpected condition. On 926 Stratford the canonical day looks like a photo of the framed wall section, a photo of the next-day’s prep, and a photo of a small water intrusion at the foundation that is now noted in the log. Three photos take 45 seconds.
The submission ritual
Logs filed from the truck before the field lead drives away have a 95% completion rate. Logs filed from the office that evening have a 40% completion rate. The difference is the ritual.
The mechanics:
- The log opens in one tap from the home screen of the field tool.
- The four required fields are visible without scrolling.
- The submit button is large enough to find with one thumb in glove weather.
- A submission confirmation is silent (no celebratory animation). The field lead just sees the next day’s log queued for tomorrow.
How the log connects to the rest of the project
A log is not a destination document. It is a record that other surfaces pull from. On a properly connected project:
- The punch list can attach a photo from the daily log rather than re-photographing the same condition.
- The inspection record for a given week pulls weather and conditions from the relevant logs.
- The draw package can attach the log entries covering the billing period as appendix, demonstrating progress without an extra photo-collection step.
- The change-order narrative for a delay caused by weather or sub no-show cites the specific log entries on the affected days.
The log is the cheapest, most repeatable data the project produces. The single design rule that makes it work is: shorten the form until the field lead does it without thinking, then put the log content to work everywhere else so the field lead sees the value.