One log entry per project per day. It auto-generates a summary of the current stage, the day number and what was ticked off, then asks for work done, blockers, blocker type and crew count. Past entries are kept as history, and generated prompts nudge for what is missing.
Also called: daily report · end of day log · what did the crew do today · site diary
The daily log is mostly written before the crew lead opens it
It names the stage in progress, what day of that stage this is, the boxes ticked today, the photos taken and any missing or damaged material already reported. Daily reporting dies when it is pure typing — a crew lead at the end of a ten-hour day is not going to retype what the schedule already knows, so the logs came back blank and then stopped coming back.
It asks only for the part the man on site can supply
Work done, what is in the way, which kind of blocker it is — weather, materials, equipment, crew, permits — and how many men were there. Four answers against a summary that wrote itself. That is the difference between a log that comes back every day and one that comes back for a week.
It points at what's missing instead of letting the day close over it
No photos today. Framing running with the posts set but the trusses and bracing still unticked. A material delivery finished with no damage or shortage check done. No log at all yesterday. Each becomes a prompt on the day's entry with the action beside it, so the gap gets closed while somebody is still standing on the site.
A day-by-day record of the job, for the argument that comes later
Every day is kept, so a build that slipped four weeks can be walked through a day at a time rather than reconstructed out of group texts. A delay claim, a back charge, or a customer asking what happened in the last week of June all need the same thing: what was done, who was there, and what was in the way.
- 1Opening the log for today either loads the existing entry or creates a blank one with an auto-summary already written
- 2The auto-summary names the current in-progress stage, the day number since its actual start, and the toggles completed on it
- 3Prompts are generated for missing photos, unchecked toggles, no materials check, no log yesterday, and a stage running behind
- 4History from previous days feeds the prompt generation
Daily reporting dies when it is pure data entry — a crew lead at the end of a ten-hour day is not going to retype what the schedule already knows, so the logs came back blank or stopped coming back. The log arrives mostly written from the day's stage and checkpoint activity, and asks only for the part nobody else can supply: what actually happened on site, what is in the way, and what is needed tomorrow.
- Daily reporting abandoned because it's all typing
- No day-by-day record for disputes or claims
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →