The construction daily log: what to record, and a template you can copy

By Adam Chandler, founder of Pangea · August 24, 2026

A construction daily log is the dated, same-day record of what happened on a jobsite: the weather, who was there, what equipment ran, what work got built and where, what was delivered, what was inspected, who visited, and what stopped. A usable daily log template captures all fourteen of those things in a fixed order, gets signed by the person who saw them, and gets written the same day — because a log written three days later is a memory, and a log written today is evidence.

Below is what to record, a template you can copy as-is, what your contract probably does and does not require, and the writing habits that decide whether the log helps you or gets used against you.

What is a construction daily log?

It is the project's diary — one entry per calendar day, kept by whoever is running the site, describing conditions and events factually rather than interpreting them. The general contractor's superintendent keeps the primary log; the owner's representative and the design team's field observer usually keep their own, and on a well-run job those versions agree.

The names get used interchangeably, so here is the plain separation:

"Daily log" and "daily report" are the same document; teams that use both words usually mean the informal field version and the formal one submitted to the owner. If your contract names one, use that word everywhere and stop maintaining two.

What should a construction daily log include?

Fourteen sections cover essentially every project, commercial or residential. The first four establish the conditions of the day, the middle six record what happened, and the last four are the ones nobody thinks about until a claim makes them matter:

1. Identification — project name and number, date, day of week, sequential report number, and who prepared it.
2. Weather — high and low temperature, conditions, precipitation, and wind. Record it at the same times every day, not once when you remember.
3. Site conditions — access, mud, standing water, utility outages, road closures. This is what makes a weather entry mean something.
4. Hours worked — start and stop time on site, plus any overtime or extra shifts.
5. Labor — every company on site by name, trade, headcount, hours, and work area. One line per subcontractor, not a single "35 workers" total.
6. Equipment — each unit, its ID number, and hours operating, idle, or down for repair. The idle and down columns turn a standby claim from an assertion into a number.
7. Work performed — by location and, where you run a CPM schedule, by activity ID. Include quantities: "placed 84 CY at footings F-12 through F-19," not "concrete work."
8. Materials and deliveries — what arrived, quantity, supplier, accepted or rejected, and where stored. Items delivered but not installed are a stored-materials pay request later.
9. Inspections and tests — who inspected, what, the result, and any deficiency with its corrective action.
10. Visitors — name, firm, purpose, and times on and off site.
11. Safety — toolbox talk topic, incidents and near-misses, and a pointer to any separate incident report.
12. Delays and disruptions — cause, exact start and stop times, and which crews were affected.
13. Verbal instructions and directions received — who said what, to whom, at what time. The most valuable and most often skipped section.
14. Sign-off and attachments — signature and date, plus photo file names with location and subject.

Construction daily log template

Copy this into a document, save it as your firm's blank, and fill one per day. It is written as a form rather than a spreadsheet row because a daily log is not one row — a job with nine subs on site has nine labor lines.

Header: Project name / Project no. / Report no. ____ / Date ____ / Day ____ / Prepared by ____ / Title ____

Weather & site: Temp high __ / low __ / Conditions ____ / Precipitation ____ / Wind ____ / Ground conditions ____ / Weather-related work stoppage: from __:__ to __:__, crews affected ____

Labor — one line each: Company | Trade | Workers | Hours | Work area / activity ID

Equipment — one line each: Equipment | ID no. | Hours operating | Idle | Down

Work performed — one line each: Location / activity ID | Description | Quantity | Performed by

Deliveries — one line each: Material | Quantity | Supplier | Accepted / rejected | Storage location

Inspections & tests — one line each: Type | Inspector / agency | Result | Deficiencies | Corrective action

Visitors — one line each: Name | Firm | Purpose | Time on | Time off

Safety: Toolbox talk topic ____ / Incidents or near-misses ____ / Separate incident report no. ____

Delays & disruptions: Cause ____ / From __:__ to __:__ / Crews and equipment affected ____ / Notice given to ____ at __:__

Verbal instructions received: From ____ (firm/role) / To ____ / Time ____ / Instruction ____ / Written follow-up sent: yes / no

Open items referenced today: RFI nos. ____ / Submittal nos. ____ / Change directive nos. ____

Photos attached: File names ____ / Location ____ / Subject ____

Signature: ____________________ Date ________

Alongside the daily forms, keep a one-row-per-day index: Date | Report no. | Weather | Total workers | Hours lost to delay | Delay cause | Prepared by | Filed?. It takes ten seconds a day and gives you two things the forms cannot — a fast answer to "was a report filed for every day," and a sortable column of delay hours you would otherwise reconstruct by reading a year of paper.

Is a daily log required by contract?

Usually yes, but not by the document most people assume. Search the AIA A201-2017 general conditions — what most U.S. commercial projects run on — for the word "daily" and you will not find it. A201 requires the contractor to keep the contract documents marked currently at the site as a record of the work as constructed (§ 3.11), but it never asks for a daily report. When your job requires one, it comes from the supplementary conditions, Division 1, or the owner's own form.

Federal work is the opposite. UFGS 01 45 00.00 10, Quality Control — the USACE / NAVFAC / AFCEC / NASA specification — requires the contractor to "maintain current records providing factual evidence that required quality control activities and tests have been performed," then lists minimum contents (§ 3.9.1) that closely track the fourteen sections above, right down to equipment hours idle or down and instructions given or received.

Three rules in that spec are worth stealing even on private work (§ 3.9.2). Reports are due daily, within a stated number of hours after the day they cover. They are not required for days with no work — but one must be filed for every seven days of no work and on the last day of a no-work period, so that all calendar days are accounted for throughout the life of the contract. And every report is signed and dated by the person responsible for it.

That "all calendar days accounted for" standard is the one that separates a defensible log from a pile of paper. A gap in the record is not neutral. It is the other side's opening.

How do you write a daily log that holds up in a dispute?

Write it the same day, in factual language, with numbers instead of adjectives. Five habits do most of the work:

• Same day, no exceptions. The log's value is that it is contemporaneous — made at the time by someone with direct knowledge. Batch-writing a week of logs on Friday destroys exactly that.
• Describe, do not characterize. "Masonry crew of 6 stood down 09:15–13:30, no hoist available" is a fact. "The GC's hoist scheduling was a disaster again" is an opinion that will be read back to you in a deposition. Record the condition, the time, and the headcount; let the conclusion draw itself.
• Time-stamp delays and quantify them. Start, stop, crews and equipment idled. "Rain delay" with no hours attached is worth almost nothing when someone tries to price it two years later.
• Get weather from a source you can produce. Your observations are the primary record, but a weather claim needs station data. NOAA's Climate Data Online gives free quality-controlled daily temperature, precipitation, and wind for U.S. stations, and NCEI issues certified hard copies for legal use for a fee. That matters because A201-2017 § 15.1.6.2 requires an adverse-weather time claim to be documented "by data substantiating that weather conditions were abnormal for the period of time, could not have been reasonably anticipated, and had an adverse effect on the scheduled construction." Your log establishes the effect; the station data establishes abnormal.
• Never alter a past entry. If you got something wrong, add a dated correction to today's log referencing the earlier report. An edited entry with no trail casts doubt on every entry you wrote.

One clock is worth knowing while you write. Under A201-2017 § 15.1.3.1, a contractor's claim must be initiated by notice within twenty-one days after the event giving rise to it, or after the claimant first recognizes the condition, whichever is later. The daily log is usually the only document that can prove when a condition first appeared — and therefore whether your notice was timely.

Who fills out the daily log, and how long do you keep it?

The superintendent or field engineer running the site writes it, because the record has to come from someone with direct knowledge of what they are describing. Foremen may feed in crew counts and quantities, but one named person signs. A daily log assembled by an office manager from text messages is not a contemporaneous record of anything.

Retention runs on your state's statute of repose, not a rule of thumb, and the spread is wide. In a 2021 construction law update, attorney John I. Mabe, Jr. recommends holding project records past the repose deadline with a cushion — three extra years, for a total of nine in North Carolina with its six-year statute and eleven in South Carolina with its eight-year statute — on the principle that "the project file should be preserved until all claims that might arise from the project have either been resolved or are legally barred." Check your own state's number and set the policy once at the firm level.

Where Pangea fits

Pangea is an AI notetaker built for project-based firms — land developers, engineers, and architects — and what it does differently is file by project rather than by meeting. It records your meetings, including in-person ones with a phone on the table and no bot in the call, reads the project email and files you connect, and keeps a living record for every job: minutes, decisions, deadlines, and action items, each traceable back to the moment someone said it.

It does not write your daily log, and it is not a field app. What it fixes is the section people leave blank — verbal instructions received. The direction on the coordination call, the owner's rep saying to hold off on the north bay, the utility company's date over the phone: those get captured and filed to the project with a timestamp, so whoever writes tonight's log has the exact words and the time instead of a half-memory. Same for what the log feeds — Tuesday's delay surfacing in Thursday's OAC meeting, or the question a field condition just raised landing on the RFI log with the date attached.

If the project's history lives in eleven people's heads and three inboxes, the project brain page is the closer read. Otherwise start at pangeanotes.com — the trial is 14 days, no credit card.