General Contractor Daily Log Template: What to Include and Why

As a general contractor, you're responsible for everything that happens on your job site — and you're expected to prove it. The daily log is how you prove it. Courts, arbitrators, bonding companies, and insurance adjusters all treat contemporaneous records as the most credible form of evidence in a construction dispute. A daily log written the same day beats any reconstruction written months later.

This guide covers what a GC daily log should include, why each section matters legally and operationally, and how to build a habit of completing it in under ten minutes.

Section 1: Project and Date Information

Every daily log entry should begin with the project name, project number, date, and the name of the person completing the log. This seems obvious, but many paper logs are submitted without proper headers, making them difficult to organize and nearly worthless in a dispute where the date of specific events is critical.

Include the day of the week as well as the calendar date. This helps when reviewing logs sequentially — "Monday, April 7, 2026" is easier to contextualize than "4/7/26."

Section 2: Weather Conditions

Weather is one of the most commonly disputed factors in construction delay claims. Document temperature (high and low), precipitation (type and estimated amount), wind conditions, and sky conditions (clear, overcast, fog). Note the time of any significant weather events.

This matters because contracts typically include force majeure provisions for "unusually severe weather." When you claim a weather delay, you need contemporaneous weather records — not a printout from Weather.com pulled three months later. Your daily log entry, combined with a weather service report for the same date, is far more credible.

Section 3: Workers on Site

Record every worker on site, their trade or role, and the hours they worked. Include your own crew and any subcontractors' workers. For subcontractors, note the company name and worker count even if you don't know individual names.

This data serves multiple purposes: it supports payroll, it documents your compliance with labor requirements, it establishes site access records in case of an incident, and it gives you a running total of labor hours against your budget.

Section 4: Work Completed

This is the core of the daily log. Describe what work was accomplished during the day in enough detail that someone unfamiliar with the project could understand what progress was made. Vague entries like "framing" or "rough-in" are insufficient. Better: "Framed exterior walls, north and east elevations, ground floor. 2x6 studs at 16 inches OC. Layout per drawing A-102 Rev 3."

Include location references (grid lines, floor, room numbers, elevation names), specification references where relevant, and quantities where measurable. This level of detail takes an extra two minutes to write but creates a record that can support change order claims, progress billing, and dispute resolution.

Section 5: Materials Delivered and Used

Note significant material deliveries: what arrived, quantity, supplier, and any delivery issues (damaged goods, incorrect quantities, wrong specification). Also note materials consumed during the day's work if they're critical to the work log description.

Material delivery records support payment application backup and help identify when a delay in materials caused a delay in work — which is directly relevant to delay claims and schedule impact analysis.

Section 6: Equipment on Site

Record major equipment present on site — cranes, excavators, concrete pumps, lifts. Note downtime or breakdowns. Equipment records support rental cost claims and document equipment-related delays.

Section 7: Visitors and Inspections

Log every visitor to the site: owner representatives, architects, engineers, inspectors (city, county, or third-party), insurance adjusters, and material testing technicians. Note what they inspected, observed, or required. Document any inspection results — passed, failed, held pending correction.

This section is critical when disputes arise over whether work was approved, inspected, or accepted. An owner who claims they weren't aware of a defect has a harder argument when your log shows their representative visited the site and observed the relevant work.

Section 8: Incidents, Delays, and Issues

Document anything that disrupted the planned work: safety incidents (any injury, near-miss, or property damage), weather delays, utility conflicts, RFI issues awaiting response, design conflicts discovered in the field, and unforeseen site conditions. For each incident or delay, note the impact on that day's work and the expected duration.

This section is the foundation of every delay claim and change order request. Without contemporaneous records of what caused a delay and when you discovered it, delay claims are nearly impossible to support. With them, you have a paper trail that drives change order approvals and schedules extensions.

Section 9: Photographs

Reference any photos taken that day. If you're using a digital reporting tool that attaches photos directly to the daily report, this is automatic. If you're using paper, note the file names or photo numbers and what they depict. Photo documentation of progress, conditions, and incidents dramatically strengthens any claim or dispute.

How Long Should This Take?

A properly completed GC daily log should take 5–15 minutes to fill out from the field. If it's taking longer, your format is too complex or you're writing narrative prose where bullet points would serve equally well. The goal is a complete, accurate record — not a polished document.

Digital tools like ConstruTrack speed up the process by structuring the form for you. Work logs, time cards, photos, notes, and incidents each have their own section. When you submit, a PDF is generated automatically and emailed to your project recipients. The free plan covers one project with unlimited daily reports — no credit card required.