Daily log or daily report: does the name matter?
Companies use the terms differently. A daily log often means the underlying entries made through the day; a daily report often means the reviewed summary sent to the office, owner or project team. On some projects they are the same document. Agree on the definition at startup rather than creating two disconnected records.
For a general contractor, the useful view is usually across all trades and site conditions. For a subcontractor, it is often a closer account of crew hours, work areas, quantities and instructions affecting that scope. Both need enough detail to explain the work without pretending that a report settles entitlement or responsibility.
Record the day in seven groups
Do not make a form so long that your foreman stops using it. Use repeatable fields for common facts and a short exception section for what changed. Keep safety-sensitive information in the appropriate controlled record, not in a public project email.
- Identity: project, date, shift, author and report revision.
- Conditions: observed weather, access, utilities and any actual work effect.
- Resources: companies, trades, crew counts, hours and equipment used.
- Production: activity, area, measurable quantity and drawing or task reference.
- Movements: deliveries, storage locations, shortages and damaged items.
- Checks and instructions: inspections, test results, visitors and directions received.
- Exceptions and evidence: interrupted work, extra-work facts, questions and linked photos.
Weather should describe the site effect
A weather entry is useful when it connects conditions to the operation. “Rain” is not the same as “exterior sealant work stopped because the substrate was wet.” Record the time, location and work affected if the conditions matter. If you use an automatically supplied weather feed, check that it reflects the project location and shift.
Never imply weather caused a compensable delay just because rain appeared in a report. A schedule effect and contractual entitlement need separate analysis. The log’s job is to preserve observed facts so that later analysis has something reliable to work from.
An example with enough detail to follow up
Downtown Office Tower | Day shift | Illustrative example Weather: Light rain observed at 7:00 a.m. Exterior unloading area wet; unloading moved to covered bay. Manpower: Drywall subcontractor, 8 workers on Level 6, 7 regular hours each. Progress: Framing completed along east corridor, gridlines E4–E8; installed quantity awaiting foreman confirmation. Delivery: Gypsum board truck arrived at 9:40 a.m.; delivery docket D-118 attached. Inspection: Firestopping inspection requested for Level 5; no result received by cutoff. Instruction: Relocate temporary partition per email from project manager; scope and pricing review pending. Photos: P-023 east-corridor framing; P-024 covered unloading bay.
A photo needs a location and a reason
A folder of images is not a usable photo record. Caption each relevant image with the project, date, area and what it shows. Keep the original file and connect the reference to the log entry. Include a wider view when a close-up does not explain location or scale.
Avoid photographing sensitive documents, personal information or people unnecessarily. Follow site rules and company retention policies. A photo showing a completed installation is evidence of what was visible at that moment, not proof that the installation passed inspection. Link the actual inspection record separately.
Correct the record without rewriting history
When a crew count or quantity is corrected, retain who made the change, when and why. An approved report should not be silently replaced with a cleaner version. Keep original messages or handwritten notes alongside the revised summary, with access limited appropriately.
Make review a short routine: check trade totals, missing locations, contradictory inspection statements and unconfirmed instructions. The project manager should not have to chase every field, but someone must own unresolved items. A good daily log makes those gaps visible.
Make field capture easier, not less accountable
With Magra, crews text or send voice notes to a project number. Magra can ask for the headcount, area, hours or delivery reference that was missing from the first update, then prepare the daily log in your format. The project’s knowledge base provides the document context for questions.
Keep the distinction between a field observation, a document reference and a reviewed conclusion. A message saying “inspection passed” should trigger a request for the result if the document is missing. Magra helps assemble the record; the responsible construction professional remains accountable for its accuracy.
Common questions
Who should complete the daily log?
Usually the superintendent or designated field lead owns the project log, with trade updates from foremen. Your company and contract determine the final reviewer.
Should I log a day when little work happens?
Record the actual conditions and activity for the required reporting period, including no-work reasons when known. Follow the project reporting requirements.
How detailed should daily log photos be?
Enough to identify the area and observation. Use captions and original references rather than unexplained image dumps.
Sources & editorial note
By Magra editorial. Examples are illustrative, not customer results. Not legal advice; executed documents, amendments and applicable law govern. Product availability can change.
Put the record to work.
Magra is the AI project manager for contractors, on your phone.
Explore construction daily logs by text · Text Magra