The Day Went Sideways. What Should Actually Go in the Daily Report?
But the day didn’t go according to plan.
The crew ran short on concrete. A balance load had to be ordered. People and equipment waited. Production slipped, and the next operation started later than expected.
You already know what happened.
The crew knows what happened.
The superintendent probably knows what happened.
But six weeks from now?
That’s a different story.
Someone may ask:
Why did production fall off that day?
How long was the crew actually waiting?
How many people were affected?
Was anyone notified?
What caused the delay?
What did the crew do about it?
If the daily report says:
“Poured concrete. Had some delays.”
You don’t have much of an answer.
A good daily report should preserve enough of the day’s story that someone who wasn’t standing there can understand what happened later.
A Daily Report Is More Than a List of Work Performed
Daily reports often become a routine.
Crew.
Hours.
Equipment.
Weather.
Work performed.
Submit.
Those things matter, but they’re only the beginning.
When something affects the operation, the report needs to capture the event and its impact.
That doesn’t mean writing a novel.
It means recording the right facts.
A useful habit is:
Time → Location → Event → Impact → Notification → Next Step
If you can capture those six things, you’ve preserved most of what someone will need later.
Go Back to the Concrete Pour
Let’s use the same situation from the first two Field Lessons.
The crew was scheduled to pour concrete.
The quantity calculation was short.
The crew eventually ran out of concrete and needed a balance load.
Now compare two daily-report entries.
This Doesn’t Tell Us Much
“Poured sidewalk today. Ran short on concrete and waited on balance load.”
Technically, it’s true.
But it’s missing most of the information that matters.
When did it happen?
Where?
How long did the crew wait?
How many people were affected?
Was equipment affected?
When was the balance ordered?
When did it arrive?
Who was notified?
What happened to production?
Those are the facts that turn a note into a useful record.
Document What Happened, Not What You Think About It
A daily report isn’t the place to write:
“The concrete plant screwed us again.”
Maybe they did.
Maybe they didn’t.
The daily report doesn’t need the argument.
It needs the facts.
A better entry might read:
Concrete placement began at approximately 7:15 a.m. at the east sidewalk between Sta. 24+50 and Sta. 27+50. Initial concrete quantity was exhausted at approximately 10:40 a.m. before the planned placement was complete. A balance load was requested. Eight crew members and the concrete operation were affected while awaiting additional material. Balance load arrived at approximately 12:10 p.m. Placement resumed after arrival. Superintendent was notified. Remaining placement was completed that afternoon.
Now someone reading the report later can understand what happened.
Notice what isn’t in there.
No blame.
No exaggerated language.
No guess about responsibility.
Just the field condition and the effect it had on the operation.
Time Matters
When a meaningful delay occurs, record the time.
You don’t necessarily need a minute-by-minute diary of the entire project.
But if something stops or materially affects production, the timeline matters.
In our example:
10:40 a.m. — Initial concrete exhausted
Balance load requested
12:10 p.m. — Balance load arrived
Operation resumed
Now we know the interruption lasted approximately 90 minutes.
That matters because a 90-minute delay doesn’t necessarily mean only 90 minutes of impact.
If eight employees were affected:
8 people × 1.5 hours = 12 labor-hours
And there may have been equipment or downstream work affected as well.
The daily report should preserve the information needed to understand that impact.
Location Matters Too
“Concrete pour” isn’t a very useful location on a large project.
Neither is:
“Worked on sidewalk.”
Be specific enough that someone can connect the report to the actual work.
For example:
East sidewalk — Sta. 24+50 to Sta. 27+50
or
Structure S-12 at north entrance
or
8-inch water main — west side of Main Street between MH-4 and MH-5
The exact format will depend on the project.
The point is simple:
Someone reading the report later should be able to figure out where the event occurred.
Record the People and Equipment That Were Actually Affected
This is where the production information becomes important.
If eight people were on the project but only three were affected by the delay, don’t automatically say eight people were delayed.
If all eight were tied to the concrete operation and couldn’t move to productive work, document that.
The same applies to equipment.
Was the excavator actually waiting?
Was the concrete pump sitting?
Could another piece of equipment continue working elsewhere?
Document the actual condition.
Accuracy makes the report stronger than exaggeration ever will.
Record Directions That Change the Work
Not every important event is a delay.
Sometimes someone gives a direction that changes:
Scope
Sequence
Location
Material
Access
Production
Schedule
Means or methods
That belongs in the field record too.
Document what was directed, who provided the direction, when it occurred, and what happened next.
Again, stick to the facts.
The field report doesn’t have to decide whether something is a change order.
It needs to preserve the information so the right people can make that determination.
Photos Should Support the Story
A pile of random jobsite pictures isn’t documentation.
Photos become more valuable when they’re connected to the event.
If the grade was wrong, photograph the condition.
If an unknown utility stopped excavation, photograph its location.
If access was blocked, photograph the obstruction.
If material arrived damaged, photograph the material.
If you’re documenting completed work before it’s covered, capture enough context to show what and where it is.
The report tells the story.
The photos help prove what the field looked like when that story happened.
Don’t Wait Until the End of the Week
This is where information gets lost.
Friday afternoon comes around and somebody tries to remember what happened Tuesday morning.
Was the truck there at 10:30 or 11:30?
Were six people affected or eight?
Did the superintendent get called before or after lunch?
Nobody remembers exactly.
And now the daily report becomes a reconstruction instead of a record.
Capture important information while it’s happening.
Even a few quick notes during the day can make the final report dramatically better.
The Three Lessons Work Together
This concrete pour started with a simple question:
How much concrete do we need?
In How Much Concrete Do You Really Need? Measure the Pour Before You Order, we looked at checking grade, checking forms, measuring the actual pour, breaking complicated pours into separate calculations, and calculating the concrete before committing the crew and trucks.
Then something went wrong.
That created the next question:
Where did the day go?
In Where Did the Day Go? How Small Delays Turn Into Lost Production, we looked at how a concrete shortage can turn into waiting, lost labor-hours, a production gap, and potentially a problem for the next operation.
Now we have the third question:
What actually needs to be documented?
That’s where this lesson comes in.
These aren’t three separate management problems.
They’re one operating cycle:
Calculate the Work → Track What Happened → Document the Facts → Make the Next Decision
That’s how information becomes useful.
Build the Daily Report While the Information Is Fresh
The One Level Higher Construction Daily Report Builder is free to use and is designed to help organize the information that matters from the field.
It walks you through the project and day information, crew and hours, equipment, production, work performed, delays, directions, supporting documentation, and tomorrow’s handoff.
Use the Free Construction Daily Report Builder →
And if you’re using the OLH calculators in the field, OLH Pro puts 13 free construction calculators together in one place for grade, quantities, hauling, concrete, underground work, and production planning.
OLH Pro is free to use and can be bookmarked to your phone for quick access. There’s nothing to download from an app store.
Open OLH Pro →
The goal isn’t more paperwork.
It’s better information.
Calculate the work. Capture what happened. Recognize what needs attention. Make a better decision.
Comments