Construction daily report and documentation field guide

The daily report, and why it is the record that wins disputes

The construction daily report is the contemporaneous record of who was on site, what they did, the conditions they worked in, and the problems that came up on a given day. It goes by daily log, daily field report, or superintendent's log, and on a data center it is kept by the foreman or super for each crew and rolled up to a single project daily. The word that carries the weight is contemporaneous. Written the day the work happened, by the person who saw it.

Here is why it matters more than any other document the field produces. When a job goes sideways and the money is in dispute, the daily report is the first thing the lawyers and the schedulers ask for. A delay claim lives or dies on whether the delay was recorded the day it happened. A change dispute turns on whether the added work and the labor that built it were logged. A safety incident gets reconstructed from the daily and the toolbox-talk record. The daily report is the testimony of the job, written before anybody had a reason to shade it.

And here is the part crews learn the expensive way. A thin log loses. "Worked on site, 12 men, no issues" tells you nothing six months later when the owner says you were behind and you say they held you up. A back-dated log loses worse, because the metadata gives it away and once one entry is shown to be reconstructed, the whole record is suspect. The daily report is only worth something if it was real, specific, and written the same day. Everything in this guide serves that one standard.

What goes in a construction daily report?

A complete daily report captures the date, the weather and temperature, the crews and headcount by company and trade and area, the work performed by location, the equipment on site, the deliveries, the visitors and inspections, the delays and their cause, the safety items, and the photos. That is the full field. Drop any one of them and you have left a hole that the other side gets to fill with their version on the day it matters.

Think of the report as answering four questions a stranger would ask a year from now. Who was here. What did they do and where. What got in the way. What did it look like. The first question is manpower and visitors. The second is work performed and percent complete. The third is delays, conditions, and the problems. The fourth is the photos. A daily that answers all four, specifically, is a daily you can stand behind in a claim. A daily that answers them in generalities is a formality nobody can use.

The sections that follow take each field in turn, with what to write and why it ends up mattering. The order is not academic. It is the order the fields get used in when a dispute is reconstructed.

Weather and temperature, and why they are not filler

The weather line is the field everybody fills in last and needs first. The contemporaneous weather record is what backs a weather-delay claim. When you lose a day to rain, wind that grounds the crane, or a heat index that shuts down the deck, the daily report that recorded the actual conditions, with the high and low temperature, is the document that turns a lost day into an excusable delay instead of your own slipped schedule. Write what stopped the work, not just "rain." Two inches by 10 a.m., site flooded, no concrete placement, is a record. "Bad weather" is not.

Temperature does more than back a delay. It governs whether the work was even allowed to happen. Concrete placed below about 40 degrees F is in cold-weather territory and needs protection, and the daily temperature is the proof the pour was protected or the evidence it was not. Coatings and sealants have a substrate-temperature and dew-point window the manufacturer sets, and the daily record of conditions is what an inspector or a warranty claim checks against. Paving and asphalt have a mat-temperature floor that the air temperature drives. When that work is in question later, the weather line on the daily is the first thing pulled.

Record temperature from a real source, not a guess, and note the source. A site station, the nearest airport observation, a logged reading. The point is that the number can be corroborated. A weather claim built on a daily that says "cold" against a forecast service showing 55 degrees F that day is a claim that just got harder to make.

Manpower by area and trade

Manpower is the headcount by company, by trade, and by area, and it is the field that proves the labor when a change or a claim comes down to how many hours the work took. "24 men on site" is a start. "Acme Electrical: 6 in the north electrical room pulling feeders, 4 on the busway in the data hall, 2 in the yard at the switchgear" is a record you can price against a cost code. The headcount by area is what lets the office tie field labor to the work it was doing, which is the whole game in a force-account or a delay claim.

Tie the count to the cost code where you can, because that is the bridge between the daily report and the money. When a change adds scope, the labor that built it has to be separable from the base contract labor, and the only place that separation gets recorded in real time is the daily and the time it backs. The manpower by area on the daily and the T and M ticket for the change have to agree. When they do, the change is defensible. When the daily says 24 men with no breakdown and the ticket claims 6 of them on the extra, you have nothing tying the two together.

Manpower also shows production. Track the headcount in an area against what got built there and you have the rate, which is what a productivity-loss claim is built from. When stacking of trades, out-of-sequence work, or constant rework drags the rate down, the daily report manpower is the data that proves the loss was real and not just a feeling. The huddle and manpower planning guide covers how the morning count gets set and rolled up. The daily is where the actual count, against the plan, gets recorded.

Work performed and percent complete

Work performed is the field that gets written worst and matters most, because "worked on site" is the line that loses every argument it touches. Describe the actual work by specific location. Not "electrical rough-in," but "pulled 480 V feeders from MSB-2 to PDU-4 in the south data hall, terminated at PDU-4." Not "poured concrete," but "placed 60 yards on the level-2 deck, grids C through F." The location and the quantity are what make the entry usable as proof of progress on a given day.

Quantities are the part the field skips and the office needs. Linear feet of conduit, yards of concrete, number of devices set, sections of busway hung. The quantity on the daily is the production for the day, and it is what a schedule analyst maps to the as-built progress when the question is whether you were ahead or behind on a given date. A daily with no quantities forces everybody to reconstruct progress from photos and memory, which is exactly the reconstruction a clean daily was supposed to make unnecessary.

Percent complete is useful as a running judgment, but treat it carefully. A foreman's eyeball 60 percent is a feeling, and feelings drift. Where you can, anchor the percent to a countable quantity. 1,200 of 2,000 devices set is 60 percent you can defend. "About 60 percent" with nothing behind it is a number that will be argued. The daily is where the honest, quantity-backed progress lives, and that honesty is worth more than an optimistic number that the next month contradicts.

Why does documenting a delay the day it happens matter?

A delay documented the day it happens is claimable. A delay reconstructed weeks later is nearly impossible to claim, and that single fact is the most important thing in this guide. When you lose time, the daily report has to record four things while they are fresh: the cause, who or what caused it, the duration, and the impact on the work. "Lost the morning waiting on the owner's switchgear inspection, north electrical room, 4 electricians idle from 7 to 11, feeder energization pushed a day" is a delay you can claim. A blank where that entry should be is a delay you absorbed.

The reason the day-of record is everything comes down to how claims get tested. A schedule analyst and a lawyer will look for the contemporaneous evidence, the record made before anybody had a motive. A delay that shows up for the first time in a claim narrative written six months later, with no daily report behind it, reads as manufactured, and the other side will say so. The standard contracts and the change-order process both run on notice, and the daily report is often where that notice starts. The field change order and takeoff guide covers turning the impact into a priced, signed change. The daily is the record the change is built on.

Be specific about the impact, not just the event. A delay that costs nothing is a footnote. A delay that idled a crew, pushed a milestone, or forced overtime to recover is money, and the impact line is where that money gets recorded. Tie the idled headcount to the manpower field and the affected work to the work-performed field on the same daily, so the cost of the delay is traceable inside one record. The day you skip that, the delay becomes a story you tell instead of a record you show.

Photos, and why a timestamped image beats a paragraph

The daily photos are the proof the words cannot carry, and they are only proof if they are tied to the location and the work. A photo with a timestamp and a location beats a paragraph because it cannot be argued with the way a written description can. "The conduit was installed correctly" is a claim. A dated photo of the conduit, in place, in a recognizable location, is evidence. On a data center where the work gets covered, the photo taken before the wall closed or the slab poured is sometimes the only record that the work underneath was ever right.

Shoot the sequence, not just the finish. Before, during, and after tells the story that a single after photo cannot. The before photo of a differing condition, taken before you disturbed it, is the entitlement for the change. The during photo of the rebar before the pour is the cover for the inspection that was never witnessed in person. The after photo is the progress proof. The photo-documentation guidance covers framing and what to shoot. The discipline on the daily is that every photo gets tied to a place and a date, because a folder of undated images of unidentifiable gray walls proves nothing.

The failure mode is photos that live nowhere. Five hundred images on a foreman's phone, no location, no link to the day's log, is not a record. It is a liability waiting to be unsearchable on the day you need the one shot that mattered. The photo has to live with the log and the location, attached to the job, or it is not part of the daily report at all.

Deliveries and materials

Log every delivery the day it lands: what came, how much, who delivered it, and the condition. The delivery record on the daily is what proves the material was on site, which becomes the issue the moment a schedule argument turns on whether you could have started a task. When the owner says you were late and the truth is the long-lead gear showed up three weeks behind the submittal date, the delivery log is the proof. On a data center the long-lead equipment, the switchgear, the PDUs, the CRAHs, the generators, drives the whole schedule, and the date each piece actually arrived is a date worth recording precisely.

Record the damaged and the short while the truck is still there, not after. Material received damaged, or a count that came up short, is a back-charge or a replacement-lead-time problem, and the only clean record of it is made at receiving with a photo. The receiving and material-handling guidance covers the inspection at the dock. The daily is where the result of that inspection gets logged, so that a damaged unit that delays an installation a month later traces back to the day it arrived broken.

Note where it got stored, especially for anything with a shelf life or an environmental requirement. Gear that needs to stay dry and conditioned, sitting in a yard through a wet week, is a warranty and a quality problem that the daily can either prevent or document. The storage note is cheap to write and expensive to have skipped.

Inspections and visitors

Record who came to the site and why, because the visitor and inspection log ties the record to the people who were there and what they accepted. The inspector and the result, the AHJ and the scope of the visit, the owner or the owner's rep and what they saw, the test that was witnessed, the hold point that was released. Each one is a fact that anchors a date in the project history. When the question later is whether an inspection passed or a hold point was released before work continued, the daily is the contemporaneous answer.

On a commissioned job the witnessed test is the entry that carries the most weight. A functional test or an integrated systems test that the commissioning agent witnessed and accepted is a milestone, and the daily report that records who witnessed it and what the result was backs the commissioning record. The commissioning operations overview guide covers how that witnessing and the deficiency log run as a program. The daily is the field-level record that a given test happened on a given day with given people present.

Log the inspections that did not happen too. The inspector who was scheduled and did not show, the owner test that got cancelled, the hold point that held up the work because the witness was not available, those are delays and they belong in the delay field as well as the visitor log. An inspection that was your responsibility and got missed is a different record than one the owner's side dropped, and the daily is where that distinction gets made while it is still clear.

Safety on the daily report

The safety entries on the daily are the toolbox talk, the job hazard analysis, the near-miss, and any incident, and they are the first record pulled after an OSHA event. Record that the morning toolbox talk happened, the topic, and who attended, because a signed attendance is the proof the crew was briefed on the hazard that later put someone at risk. Record the JHA for the high-risk task. The huddle and toolbox-talk guidance covers running the morning brief. The daily is where the proof it happened gets kept.

A near-miss is worth recording precisely because nothing happened. The load that swung, the scaffold tag that was wrong, the energized panel found with the cover off, are the leading indicators, and a program that records and acts on near-misses is the one that keeps the recordable off the log. The contemporaneous near-miss entry is also what shows a regulator that the site was paying attention before an incident, which matters when intent and diligence are in question.

After an incident, the daily report becomes a legal document, so write it straight. Record the facts: what happened, when, where, who was involved, what conditions were present, what was done. Do not speculate about cause and do not characterize fault on the daily. That gets sorted in the formal investigation. The daily's job is the contemporaneous facts, and the discipline of recording them plainly, the same day, is what makes the daily a record a regulator and a lawyer both find credible.

The T and M ticket and the daily report are the same fight

Time-and-material work, also called force account, is work done on a cost-plus basis when the scope is not yet priced, and the signed T and M ticket and the daily report are two records of the same labor. They have to agree. The ticket lists the men, the hours, the equipment, and the material for the extra work. The daily lists the manpower by area and the work performed. When a reviewer lays them side by side, the headcount on the change has to be present in the daily's count, doing the work the ticket describes, on the same date.

Get the ticket signed the day the work is done, by the person on the owner's or the GC's side with the authority to sign it. An unsigned T and M ticket is a number you assert. A signed one is a number they agreed to. The field change order and takeoff guide covers pricing the change and the markup. The point for the daily is that the labor on the ticket and the labor on the log are the same fight, and a daily that does not back the ticket is a hole the other side will drive a denial through.

The common failure is the ticket and the daily drifting apart. The ticket claims eight hours on the extra, the daily shows the crew on base-contract work that afternoon, and now the change is in trouble because the contractor's own records contradict each other. Keep them consistent at the source. The daily report manpower and the T and M ticket should be written by the same discipline, the same day, against the same reality.

Who writes the daily report and when?

The foreman or the superintendent writes the daily report, and they write it the same day, not on the weekend catch-up. The person who saw the work writes the record of the work. That is what makes it testimony instead of hearsay. On a large data center each trade foreman keeps a gang-level daily for their crew, and those roll up into the single project daily the general contractor's superintendent owns. The gang report is the detail. The project daily is the official record.

The same-day discipline is the whole thing, and it is the thing that slips first when the job gets busy. A daily written Friday for the whole week is not contemporaneous, it is a reconstruction, and a reconstruction made under schedule pressure is exactly the record that gets picked apart in a claim. The dates do not lie. A batch of five dailies all created Friday afternoon, when the metadata shows it, tells the other side that none of them were real. Fifteen minutes at the end of each shift beats two hours on Friday, and it produces a record that holds up instead of one that invites the question.

Build the time into the day. The crews that keep good dailies are the ones where the foreman fills it in at the gang box before they leave, while the day is still in their head and the photos are still on the phone. The crews that keep bad dailies are the ones treating it as paperwork to be caught up later. The difference shows up nowhere until the day there is money on the line, and then it shows up as everything.

The daily report as a contract requirement

On most large jobs the daily report is not optional and it is not just good practice. The contract requires it, and often it is a condition of payment or a condition of a claim. The general conditions and the Division 01 specifications, the administrative requirements that govern how the project is run, commonly spell out the daily report: what it must contain, how often it is submitted, and to whom. Read that section at the start of the job, because the contract, not this guide, controls what your daily has to include and when it is due.

When the daily is a condition of payment, a pay application can be held for missing dailies, and that is a real lever owners use. When it is a condition of a claim, the contract may say that a delay or a change not recorded in the daily report within a stated number of days is waived. That clause turns a missed daily from a paperwork gap into a forfeited claim. The notice deadlines in the standard agreements run on the same clock, and the daily is frequently where the notice trail begins.

Treat the contract's daily-report requirement as the floor, not the ceiling. The spec tells you the minimum the owner will accept. The record that protects you in a dispute is usually more detailed than the minimum, because the minimum was written to satisfy a submittal, not to win a claim. Meet the contract requirement so you get paid, and keep the fuller record so you can defend the work. The two purposes overlap but they are not the same.

The format and the fields: structured vs freeform

A structured daily report with fixed fields beats a freeform note, because structure makes the record complete and searchable. The freeform note is fast and it is also where fields get forgotten. The day you are slammed is the day the freeform note skips the manpower count and the delay, and those are the days the delays happen. A form with a slot for weather, manpower by area, work by location, deliveries, inspections, delays, safety, and photos forces the question even on the bad days, and the answer "none today" on a slow field is itself a record.

Structure also makes the record searchable, which is what turns a year of dailies from an archive into evidence. When a claim asks what happened in the north electrical room across three weeks, a structured set lets you pull every entry tagged to that area in seconds. A shoebox of freeform notes makes you read all of them. The standard daily-report fields are not bureaucracy. They are the index that makes the record usable when you need it under pressure.

The fields should match how the job is actually broken down: by area, by trade, by cost code where it helps. A daily structured the way the project is structured rolls up cleanly into the progress report and the claim. A daily structured around nothing in particular has to be reorganized before anybody can use it, and reorganizing a year of records after the fact is the kind of work that does not get done until it is too late to do well.

The photo, the log, and the signoff in one place

The daily report falls apart when its pieces live in different places. The photos are on a foreman's phone. The written log is in a notebook in the truck or a spreadsheet on a laptop. The signed T and M ticket is in an email thread. The delivery slip is in a pile at the trailer. Each piece is real, and together they are useless, because nobody can assemble them into one record on the day a claim needs it. The photo, the log, and the signoff belong in one place, attached to the job.

This is the practical case for keeping the daily report in a single field system instead of scattered across a phone, a notebook, and email. FieldOS is the offline-first field tool a lot of crews use for exactly this. The job photos, the daily log, the proof packets, and the owner-ready report live together, attached to the job and the location, so the record assembles itself instead of having to be reconstructed from four sources after the fact. When the photo is tied to the log entry and the log entry is tied to the day and the area, the owner report builds itself from the dailies that were already kept, rather than living in your truck until somebody asks for it.

The test is simple. Can you produce, for a single day six months ago, the manpower, the work performed, the delays, and the photos, in under five minutes, without calling three people? If the answer is no, the pieces are too scattered, and the daily report is not really a record yet. It is raw material for a record nobody has time to build.

Digital vs paper and the offline reality

Paper still shows up on jobs because it always works, and that is its only real advantage. The paper binder does not need signal, does not need a charge, and does not sync wrong. What it cannot do is carry metadata, get searched, or be in two places at once. A photo stapled to a paper daily has no embedded timestamp or location a reviewer can verify. A paper binder in a trailer is one fire or one flood from gone, and it is unsearchable by definition. The digital record beats it on every axis except needing power.

The objection that kills digital on real jobs is signal. A data center under construction is a steel box with no cell service in the middle, a concrete deck three levels down, a mechanical yard behind the building. An app that needs a live connection to record the daily is an app that does not work where the work is. The answer is an offline-first tool that captures the log and the photos locally and syncs when the device gets back to signal, so the foreman at the gang box with no bars still gets the record made, and it uploads itself later. FieldOS is built that way for that reason.

The thing the digital record gives you that paper never can is the photo with metadata and the searchable log. A photo that carries its own date and location, in a log you can filter by area and date, is a record that defends itself. That is the gap between digital and paper that matters in a claim, and it is worth the small discipline of getting the crews onto a tool that works without signal.

How long do you keep daily reports?

Keep daily reports at least through the claim window and the applicable statute of limitations and repose, which run for years after substantial completion and vary by jurisdiction and contract. The contract governs the minimum retention, and the statute governs how long you can be sued or sue, so the honest answer is keep them longer than you think you need to. A reasonable default on large work is the life of the project plus the longest of the contract retention, the statute of limitations, and the warranty period, but confirm the actual numbers with your contract and your counsel, because they are project and state specific.

The reason to keep them long is that the disputes that need them surface late. A delay claim can run for a year or more after the job. A latent-defect claim can land years after closeout, when something installed and covered finally fails, and the daily report from the week it was built is the record of how it was built and who inspected it. A daily report you discarded at closeout is a defense you no longer have, on a claim that arrived after you stopped looking.

Retention is also a handoff. The owner or the GC usually has a contractual right to the daily reports, and the closeout package frequently includes them. Hand over what the contract requires, and keep your own complete copy regardless, because the copy in the owner's archive is organized for the owner's purposes, not your defense. A searchable digital set is far easier to retain for years than a wall of binders, which is one more reason the record should be digital before the job ends, not after.

From the daily to the owner report and the closeout

The dailies are the raw material that the weekly and monthly progress reports are built from, and they feed the closeout record at the end. The owner does not read 300 dailies. The owner reads the progress report, and the progress report is only as good as the dailies under it. When the dailies are specific, with manpower by area and quantities by location, the progress report writes itself and it holds up. When the dailies are thin, the progress report is a guess dressed as a status, and it falls apart the first time the owner challenges it.

On a data center the dailies also feed the commissioning and turnover record. The witnessed tests, the inspections, the hold points released, all logged on the dailies, become part of the evidence that the systems were built and verified the way the owner's project requirements demanded. The commissioning operations overview guide covers how that turnover record is assembled. The dailies are the field-level entries that the higher-level record draws on.

The cleaner the dailies, the cheaper the closeout. Closeout is where a year of loose records gets reckoned with, and the projects that close fast are the ones where the daily record was kept well from day one. The projects that drag through closeout for months are usually the ones reconstructing a record that should have been kept as they went. The daily report is the front-end discipline that pays off at the back end, and on the claim that may come after that.

What to document each day

Use a fixed field list so nothing gets skipped on the busy days, which are the days that matter. The table below is the working set for a large data center or commercial daily. Match it to the Division 01 requirement and add the cost-code and area breakdowns your project runs on.

The rule behind the list is that every field is a question someone will ask in a dispute. Fill it the way you would want it to read when a stranger pulls it a year from now, with names, locations, quantities, and times, not generalities.

Common mistakes

• Writing "worked on site" instead of the actual work by specific location and quantity.
• Back-dating or batch-writing dailies, which the metadata exposes and which taints the whole record.
• Recording a total headcount with no breakdown by company, trade, and area.
• Failing to record a delay the day it happened, which makes it nearly impossible to claim later.
• Letting the T and M ticket and the daily manpower disagree on who did the extra work.
• Taking photos with no location and no date, or leaving them stranded on a phone.
• Skipping the weather and temperature on the day the work was temperature-sensitive.
• Closing the daily with no signoff, so nothing ties the record to a person and a date.

Field checklist

Standards and references

The daily report is governed first by the contract, not by a code. The general conditions and the Division 01 administrative specifications spell out the daily-report requirement, the submission frequency, and any condition tying the daily to payment or to a claim. That language is project specific and it controls. Read it at the start of the job and write the daily to satisfy it. When the contract and any general guidance conflict, the contract wins.

The standard industry agreements set the framework for the notice and claim process the daily report supports. The AIA A201 general conditions, the ConsensusDocs and EJCDC families, and the AGC's project-management guidance all run change and delay claims on notice within a stated time, and the contemporaneous daily report is commonly where that notice and its supporting record begin. The specific notice periods and waiver provisions live in the contract you signed, so confirm the deadlines against that document rather than a general rule.

Two more sources shape what the daily must capture. OSHA recordkeeping and the company's own safety program govern the incident, near-miss, and toolbox-talk entries, and after a recordable the daily becomes part of that record. The company's own field procedures usually set a daily-report standard above the contract minimum, because the office has learned what it needs in a claim. This is process and project management, not code, so name the document that controls the point and verify the specifics against your contract, your safety program, and your counsel.

Terms and definitions

The daily report carries a handful of terms that mean specific things in a dispute, and using them precisely is part of keeping a record that holds up.

A daily report and a daily log are the same document under different names. Manpower is the labor headcount, counted by company, trade, and area. Percent complete is progress, best anchored to a countable quantity rather than a feeling. A delay is lost time, claimable mostly when recorded the day it happens with its cause and impact. T and M, or force account, is cost-plus work tracked by men, hours, equipment, and material on a signed ticket. A contemporaneous record is one made at the time of the event, which is the quality that gives the daily its weight.

Daily report / daily log

The contemporaneous record of who was on site, what they did, the conditions, and the problems on a given day

Manpower

Labor headcount on the job, recorded by company, trade, and area, ideally tied to a cost code

Percent complete

Progress on a scope, most defensible when anchored to a countable quantity rather than an eyeball estimate

Delay

Lost or impacted time, claimable largely when recorded the day it occurs with cause, duration, and impact

T and M / force account

Cost-plus work tracked by men, hours, equipment, and material on a signed ticket the daily must back

Contemporaneous record

A record made at the time of the event, the quality that makes the daily report credible in a claim

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is commissioning in construction?
• What is a field change order?
• What is an RFI in construction?
• What is an inspection and test plan?
• Cast-in vs post-installed anchors: which should I use?