Daily reports: fifteen minutes that decide six-figure claims

Writing the delay entry properly

Most daily reports either omit disruption entirely or describe it in a way that is useless later. There is a specific way to write it that holds up.

Four components:

The condition, factually and without characterization. "Mechanical contractor working in ceiling space at grids 6 to 11, preventing access for ceiling grid installation." Not "MEP is in our way again."

The activity affected, named specifically. Which crew, which scope, which location.

The quantified impact. Hours lost, workers idled, crew relocated to a different activity. "Four-person crew relocated to level 3 for the balance of the day; approximately six hours of planned production not achieved."

The notification made. Who was told, when and how. This closes the loop that most claims fail on — not whether the disruption happened, but whether it was raised at the time.

Two rules govern the tone. Record facts, never blame or legal conclusions. A report saying "the GC's mismanagement caused this delay" is an argument that will be attacked; one recording exactly what happened is evidence. And never edit a past report. If something was wrong or omitted, add a correction in a later dated entry. An altered contemporaneous record loses most of its value and raises questions about everything around it.

Photographs that mean something

Everyone photographs jobsites now, and most of those photographs are useless as records because they lack the three things that make an image evidence: location, date and context.

Five practices:

Establish fixed vantage points. Four to eight positions photographed weekly from the same spot throughout the project. This produces a comparable sequence rather than a pile of images.

Shoot wide, then medium, then close. A close-up of a defect with no wide shot cannot be located afterward by anyone.

Photograph what will be covered, before it is covered. Everything above a ceiling, inside a wall, or under a slab. This is the single most valuable category of construction photograph and the one most often skipped because the crew is in a hurry to close up.

Include something that establishes scale and location. A tape measure, a column line marker, a grid reference written on the wall.

Name and file them the day they are taken. Ten thousand photographs with no organization are approximately as useful as none, which is the state of most project photo archives.

One additional habit with disproportionate value: photograph the site at the end of every week from the fixed vantage points, whether or not anything notable happened. The weeks where nothing happened are frequently the ones a delay analysis turns on.

Two claims, two outcomes

A mid-size commercial contractor faced two delay disputes within eighteen months, on projects of similar size and with similar underlying facts: another trade's late work compressed their schedule and forced overtime.

Claim A, on a project with weak documentation. Daily reports existed but recorded only headcount and a one-line work description. No disruption entries. Photographs were plentiful but unlabeled and undated in any organized way. The contractor claimed $214,000 in acceleration and lost productivity. Unable to demonstrate when the interference began, which activities were affected or that notice had been given contemporaneously, they settled for $38,000 after roughly $22,000 in professional fees.

Claim B, after the reporting standard changed. Daily reports included manpower by subcontractor, work by location, and a disruption field completed on 31 separate days naming the interfering trade, the affected activity and the estimated hours lost. Photographs from fixed vantage points, weekly. Notification emails referenced in the reports. The contractor claimed $186,000 and settled for $161,000, with approximately $9,000 in professional fees, and reached agreement in about six weeks rather than eight months.

The difference in recovery: roughly $136,000, plus $13,000 in reduced fees and seven months of avoided distraction.

The reporting change that produced it cost the superintendent about twelve additional minutes a day.

Making it actually happen

Daily reporting fails on consistency, not on knowledge. Everyone knows what to write; the reports stop appearing in week six.

Five things that make it stick:

Keep it to fifteen minutes. A form requiring forty minutes will not be completed daily by anyone, regardless of policy. If your template takes longer, it is too long.

Write it on site, at the end of the day. Reports written the next morning lose detail; reports written weekly are reconstructions, and reconstructions are exactly what they need not to be.

Use a structured form, not free text. Fields prompt completeness. A blank page produces a paragraph about the weather.

Have someone read them. The fastest way to end daily reporting is for the field to conclude nobody looks. A project manager who reads them and responds to something specific once a week keeps the practice alive indefinitely.

Make it a foreman task, not only a superintendent task. The person closest to the work knows what slowed it down, and their entry is more useful than a summary written two levels up.

One organizational note: whatever the format, the reports must be stored where they will still be findable in three years. Claims and warranty issues arrive long after the project team has moved on, and a record nobody can retrieve is functionally a record that does not exist.

The other records that matter

The daily report is the backbone, but four other records carry weight in the same situations, and each is cheap to maintain during the work and impossible to recreate afterward.

Meeting minutes with distribution. Whoever writes the minutes controls the record. If the general contractor or the owner writes them and you do not review them, their version becomes the accepted history of the project. Read them within a few days, and respond in writing to anything inaccurate or missing — a short correction email creates a contemporaneous record even when the official minutes do not.

Correspondence, kept in one place. Notice of a condition sent by text message from a superintendent's phone is real notice and is also the notice nobody can find in two years. Route anything that constitutes a notification, a request or an agreement through a channel that is archived and searchable.

Time and material tickets, signed daily. For work performed outside the contract on a time and material basis, an unsigned ticket is a conversation about whether the hours were real. Signed the same day by someone with authority, it is a document. This single habit resolves more billing disputes than any contract clause.

The as-built schedule. Recording actual start and finish dates against the baseline as the job progresses takes minutes per week and produces the comparison that any delay analysis requires. Reconstructing it at the end, from daily reports, is possible but expensive — and it is the exercise professional analysts bill for.

The connecting principle is worth stating plainly: documentation is only valuable if it was created at the time and can be found later. Records assembled after a dispute begins are argument, not evidence, and everyone in the process knows the difference.

Five mistakes in construction documentation

• Leaving the disruption field blank. Discards the only field that decides most claims.
• Recording total headcount instead of headcount by subcontractor. Loses the ability to prove who was and was not manning the job.
• Editing past reports. Destroys the contemporaneous quality that gives them weight.
• Unlabeled, unorganized photographs. Ten thousand images that cannot be located are worth about as much as none.
• Writing opinions instead of facts. Turns evidence into an argument that the other side gets to attack.

The numbers to watch

• Report completion rate, as a percentage of working days — anything below 95% means the record has holes exactly where you will need it.
• Days with a disruption entry, which on most projects should not be zero.
• Average time to complete a report, because a rising number predicts abandonment.
• Photographs from fixed vantage points per week.
• Notifications referenced in reports against notifications actually sent.
• Time to retrieve a specific day's record from a project that closed two years ago.

Documentation is the only part of construction where the work is done at one time and the value is delivered at another, sometimes years later. That makes it permanently easy to deprioritize and permanently expensive to have skipped. Fifteen minutes at the end of the day, a structured form, a disruption field that gets filled in, and photographs from the same eight positions every week — it is not sophisticated, and it is routinely the difference between recovering most of a claim and recovering almost none of it.

Frequently asked questions

What should a construction daily report include?

Nine elements, and the most commonly omitted are the ones that matter most later. Date, weather and site conditions, with temperature, precipitation, wind and ground conditions — a report that says rain is far weaker than one recording rainfall and the hours work stopped. Manpower by company and trade rather than a total, which is the field that proves whether a subcontractor was manning the job as promised. Work performed by location, specific enough to be verifiable. Equipment on site, including idle equipment, since idle time is a cost in delay claims. Deliveries received, with damage or shortage noted. Visitors and inspections, including inspector name, purpose and outcome. Delays, disruptions and interference — the single most important field and the one most often blank. Safety observations, including near misses. And photographs tied to the report and to the location.

How do you write a disruption entry that holds up?

In four components, written the day it happens. The condition, stated factually and without characterization — mechanical contractor working in ceiling space at grids 6 to 11, preventing access for ceiling grid installation, rather than MEP is in our way again. The activity affected, named specifically by crew, scope and location. The quantified impact, such as a four-person crew relocated to level 3 for the balance of the day with approximately six hours of planned production not achieved. And the notification made, recording who was told, when and how — which closes the loop most claims fail on, since the dispute is rarely about whether disruption occurred but about whether it was raised at the time. Two rules govern tone: record facts rather than blame or legal conclusions, and never edit a past report — add a correction in a later dated entry instead.

What makes a construction photograph useful as a record?

Location, date and context, which most jobsite photographs lack. Five practices supply them. Establish four to eight fixed vantage points photographed weekly from the same spot throughout the project, producing a comparable sequence rather than a pile of images. Shoot wide, then medium, then close, because a close-up of a defect with no wide shot cannot be located afterward. Photograph everything that will be covered before it is covered — above ceilings, inside walls, under slabs — which is the most valuable category and the one most often skipped. Include something establishing scale and location, such as a tape measure or a grid reference. And name and file them the day they are taken, since ten thousand unorganized photographs are about as useful as none. One habit adds disproportionate value: shoot the fixed vantage points every week even when nothing notable happened.

Are daily reports worth the time they take?

The ratio is unusual even for construction. Fifteen minutes a day across a nine-month project is roughly forty-five hours of writing, while a single disputed delay claim on a mid-size commercial job commonly involves six figures. In one contractor's experience, two similar delay disputes went very differently: on the project with reports recording only headcount and a one-line work description, a $214,000 claim settled for $38,000 after $22,000 in professional fees; on the project where reports recorded manpower by subcontractor, work by location and a completed disruption field on 31 separate days, a $186,000 claim settled for $161,000 with $9,000 in fees, in six weeks rather than eight months. The difference in recovery was roughly $136,000, produced by about twelve additional minutes a day.

How do you get daily reports done consistently?

Five things, because daily reporting fails on consistency rather than knowledge — everyone knows what to write, and the reports stop appearing in week six. Keep it to fifteen minutes, since a form requiring forty will not be completed daily regardless of policy. Write it on site at the end of the day, because reports written the next morning lose detail and weekly reports are reconstructions, which is exactly what they need not to be. Use a structured form rather than free text, since fields prompt completeness while a blank page produces a paragraph about the weather. Have someone read them, because the fastest way to end the practice is for the field to conclude nobody looks. And make it a foreman task as well as a superintendent one, since the person closest to the work knows what slowed it down.