A good daily log reads like a clear account of the day, not a list of disconnected field values. The example below shows how project identity, work by location, labor, conditions, events, photos, and follow-up fit together so the office can understand what occurred.
Project and work summary
Example: Level 2 electrical rough-in continued in Areas B and C. Crew installed branch conduit above Rooms 210 through 218 and completed feeder pulls from Panel LP-2 to the east corridor junction boxes. Area C ceiling work stopped at 1:20 p.m. because another trade occupied the lift access route.
Labor and conditions
Example: One foreman and six electricians worked eight hours. Morning temperature was 64°F with dry access. Heavy rain began at 12:45 p.m. Exterior material staging was suspended for 2.5 hours due to standing water at the east gate.
Use the example during field review alongside the Complete field checklist.
Events and evidence
Example: Delivery of light fixtures arrived at 9:35 a.m. Two cartons showed visible corner damage and were photographed before acceptance. GC superintendent inspected above-ceiling rough-in in Rooms 210 through 214 at 3:10 p.m. and requested correction of two support locations.
Submission and review
The author submits the log the same day. The office reviews work descriptions, crew totals, event details, and photo captions. If clarification is needed, the record returns for correction before approval.
Why this example works
The entry identifies areas, activities, crew size, times, weather impact, a delivery problem, an inspection, and required correction. It distinguishes completed work from disruption and gives photo references. A reviewer can understand the day and decide what follow-up is needed.
Example of a weak entry
Weak entry: “Electrical crew worked second floor. Rain delay. Fixtures delivered. GC looked at work.”
This version omits locations, progress, crew counts, duration, actual weather impact, delivery condition, inspection result, and next steps. It may be quick to write, but it provides little value to the office.
How the office should review it
Confirm that labor totals align with the crew narrative. Check whether the access restriction or damaged delivery requires notice, a backcharge response, or a potential change. Verify that the inspection correction is assigned and completed on a later log. Approve the record only after material questions are answered.
Expanded event example
Example: At 10:15 a.m., the GC superintendent directed the electrical crew to stop installation in Rooms 216 through 218 because revised equipment locations were expected. One foreman and three electricians moved to Area B rough-in at 10:35 a.m. The office was notified at 10:42 a.m., and potential change PC-014 was opened with photos of the existing route and marked-up sketch.
This event record identifies the instruction, responsible party, affected area, timing, labor response, mitigation, office escalation, and related change reference. It avoids guessing about responsibility or final cost.
Set the standard with the complete toolkit
Use the completed sample with the blank template and writing guidance to set a consistent reporting standard:
Common questions
Frequently asked questions
What makes this daily log example strong?
It identifies work, location, labor, times, conditions, events, evidence, and follow-up clearly enough for an off-site reviewer.
Should a daily log state who caused a delay?
Record objective facts, involved parties, instructions, and timing. Avoid unsupported conclusions or emotional language.
How should the office review a completed log?
Check consistency among the narrative, labor, events, photos, and any notice or change-order follow-up.
Compare a real report with the example section by section. Correct vague descriptions, unexplained photos, missing locations, and open issues before they become the company standard.