Daily Job Reports: What Field Crews Should Record (with a Sample)
What a field crew’s daily report should capture, how to write entries that hold up in a dispute, and a filled-in sample you can copy.
Key Takeaways
- Write it the same day, every day. A record made at or near the time, as a regular practice, is far more credible than one rebuilt later. That’s also the test courts use for business records.
- Facts, numbers and names beat adjectives. “Set 22 of 40 posts, east line” is useful. “Good progress on fence” isn’t.
- Delays and customer instructions are the most valuable lines. Record who said what, when, and what it changed. These are the entries that pay for change orders and defend schedule claims.
- Photos belong in the report, not in someone’s camera roll. Attach them to the day and the job so anyone can find them later.
- Keep the form short enough to finish in the truck. A report nobody fills in is worse than a short one everyone does.
Quick-Start Prioritization Framework
| Section of the report | Must have | Skip if |
|---|---|---|
| Date, job, crew and hours | Always | Never |
| Weather and site conditions | Outdoor work, or anything weather affects | Fully indoor service visits |
| Work completed, with quantities | Always | Never |
| Materials and equipment | Deliveries, shortages, rentals | Nothing changed |
| Delays, problems, extra work | Anything that cost time or money | Truly nothing happened |
| Customer and inspector contact | Any instruction, approval or inspection | No contact |
| Safety | Toolbox talk, near misses, injuries | Never skip on construction sites |
| Photos | Start, end, anything covered up | Never |
| Plan for tomorrow | Multi-day jobs | One-visit jobs |
A daily job report is the crew’s memory of the day, written down before it fades. It takes a foreman ten minutes. Months later it is the thing that settles whether the homeowner asked for the extra outlet, why the job ran three days long, who was on site when the fence got damaged, and whether the trench was inspected before anyone went in. Most small crews either skip it or write “worked on job” and move on. This guide covers what to record, how to write it so it’s useful, a filled-in sample, and the habits that keep reports coming in every day.
What a daily report is for
A daily report isn’t paperwork for the office. It has four jobs, and knowing them tells you what to write.
Proof of what happened
When a customer disputes a bill or a general contractor backcharges you, the question is always what happened on a specific day. Under Federal Rule of Evidence 803(6), a business record can be admitted when it was made at or near the time by someone with knowledge, kept in the course of a regularly conducted activity, and making it was a regular practice. Courts use their own rules and states have their own versions, but the logic is universal: a report written every day, the same way, is believable. One written after the dispute starts isn’t.
Getting paid for extra work
Most unpaid extra work starts as a conversation on site. “While you’re here, can you also…” If the report records the request, who made it and what it involved, the office can turn it into a change order. If it doesn’t, it usually becomes free work.
Running the next day
The report tells the office what’s done, what’s short and what the crew needs tomorrow. That is how materials get ordered before the crew runs out, not after.
Safety and compliance
OSHA’s construction rules require accident prevention programs that provide for frequent and regular inspections of job sites by competent persons (29 CFR 1926.20(b)). For excavations, a competent person must inspect daily before work starts (29 CFR 1926.651(k)). A line in the daily report showing the inspection happened, and who did it, is the simplest record of that.
What to record, field by field
Here is a complete daily report for a crew. Trim it to fit your work, but think twice before removing the delays and contact sections.
| Field | What to write | Why it matters |
|---|---|---|
| Date, job name and address | Filled automatically if possible | Every other line hangs on this |
| Crew on site | Names, start and stop times, subs on site | Payroll, and who to ask later |
| Weather | Conditions at start and midday, temperature, rain | Explains delays; affects concrete, paint, sealing |
| Site conditions | Mud, standing water, access blocked, utilities off | Explains slow days and change orders |
| Work completed | What, where and how much, in units | Progress billing and schedule |
| Materials received or used | Deliveries with ticket numbers, shortages, damaged items | Ordering, supplier claims |
| Equipment | Rentals on and off site, breakdowns, hours | Rental bills and job cost |
| Delays and problems | What, start and end time, cause, who was told | Schedule claims, change orders |
| Extra work requested | Who asked, exactly what, whether it was approved | Getting paid |
| Customer, GC or inspector contact | Name, time, what was said or decided | Settles “nobody told us” |
| Inspections | Type, inspector, pass or fail, corrections | Permits, warranty |
| Safety | Toolbox talk topic, near misses, injuries, first aid | Records and early warning |
| Photos | Start, end, progress, anything covered up, any damage found | Proof |
| Tomorrow | Plan, crew needed, materials needed | Next day starts on time |
A filled-in sample
This is what a good report looks like for an ordinary day on a residential job. The job and names are made up; the level of detail is the point.
Header
Tuesday, March 10. Job: Patel backyard, 412 Alder Lane. Foreman: J. Ruiz. Crew: J. Ruiz 7:00–3:30, D. Kim 7:00–3:30, A. Osei 7:00–1:00 (left for dentist, approved). Weather: overcast, 48°F at 7:00, light rain 11:15–12:30, 55°F at 2:00. Site: lawn soft after rain, kept equipment on plywood.
Work and materials
Work completed: set and plumbed 22 of 40 fence posts, east and north lines, concrete in all 22. Dug 9 post holes on west line, not set. Materials: received 40 bags concrete mix from supplier, ticket 88213, 2 bags torn, set aside. Equipment: rental auger on site, 5.5 hours used.
Delays, extra work and contact
Delay: stopped post setting 11:15–12:30 for rain. Crew cleaned up and staged west line. Problem: found old concrete footing at west line post 6 location, about 18 inches down. Photo attached. Called office 12:45, told S. Lee. Extra work: at 2:10 Mrs. Patel asked for a second gate on the north line, 4 ft wide, near the shed. Told her the office will send a price. Not started.
Safety and tomorrow
Safety: toolbox talk at 7:05 on auger kickback, all three present. No injuries, no near misses. Called 811 ticket confirmed valid before digging. Photos: 14 attached (start, posts set, old footing, torn bags, end of day). Tomorrow: finish west line posts if footing can be broken out, need jackhammer rental. Two crew. Waiting on gate price approval.
How to write entries that hold up
The difference between a useful report and a useless one is rarely length. It’s specificity.
| Vague | Specific |
|---|---|
| Worked on fence | Set 22 of 40 posts, east and north lines |
| Rain delay | Stopped 11:15–12:30, light rain; staged west line |
| Customer wants changes | 2:10, Mrs. Patel asked for a second 4 ft gate on north line; price to follow; not started |
| Some materials bad | 2 of 40 concrete bags torn on delivery, ticket 88213, set aside |
| Inspector came | 9:40, county inspector R. Hall, footing inspection, passed |
| Problem with old stuff in ground | Old concrete footing at west post 6, about 18 in. down, photo attached, office told 12:45 |
Write what you saw, not what you think
“Plumber’s truck blocked driveway 8:00–9:15, crew could not unload” is a fact. “Plumber was in the way all morning again” is an opinion that will be read out loud someday. Stick to times, quantities, names and what was said.
Quote instructions
When a customer, GC or inspector tells the crew to do something different, write it close to word for word, with the time and their name. “Per Mrs. Patel at 2:10” is a short phrase that saves long arguments.
Never edit yesterday quietly
If something needs correcting, add a dated note saying what changed and why. A report that was silently rewritten after a dispute started loses most of its value.
Weather, delays and the schedule
Weather is the most common reason a crew loses a day, and the most commonly disputed.
Record what you observed on site
Write the conditions at the site, with times: “light rain 11:15–12:30.” A forecast or an app’s city-wide reading doesn’t tell anyone what the ground was like at 412 Alder Lane.
Back it up later if needed
NOAA’s National Centers for Environmental Information runs Climate Data Online, which gives free access to historical daily weather records by station, searchable by ZIP code, city or county. Certified copies are available for a fee for legal use. Your daily report plus the nearest station’s record is a strong combination.
Separate delay from slow
A delay is a period when the crew couldn’t do the planned work, with a cause and a start and end time. Slow progress without a cause isn’t a delay, and calling it one weakens the real ones.
Safety lines that matter
A daily report isn’t an OSHA log, but it is where the day-to-day evidence of a safe site lives.
Toolbox talks and inspections
Record the topic, who led it and who attended. Record required inspections: excavations before work each day by a competent person, scaffolds, ladders, equipment. A short entry is enough: “Trench inspected 6:50 by J. Ruiz, no issues.”
Injuries and near misses
Record every injury, even first aid, and every near miss. Serious events also have deadlines: OSHA requires employers to report a work-related fatality within 8 hours and an in-patient hospitalization, amputation or loss of an eye within 24 hours (29 CFR 1904.39). The daily report doesn’t replace that call, but it should show it was made.
Making reports happen every day
The form is the easy part. Getting it filled in on the 40th day of the job is the hard part.
One owner, one deadline
The foreman writes it before leaving the site. Not the next morning, not on Friday. Give them the paid time to do it; it’s work, and it counts as hours worked.
Make most of it tap, not type
Date, job, crew and times should fill themselves. Weather and common delays can be picked from a list. Typing should be reserved for the things only the foreman knows: what got done, what went wrong, who said what.
Read them
If the office never responds to a report, foremen stop writing them. Reply to problems the same day. Turn “customer asked for a second gate” into a price by morning. That’s the feedback that makes the habit stick.
Common mistakes
Most weak reports fail in the same few ways.
- Writing reports at the end of the week from memory.
- Recording effort (“worked hard”) instead of output (“set 22 posts”).
- Leaving out the customer conversations, which are the entries most likely to matter later.
- Photos sitting in personal phones instead of attached to the job and date.
- No times on delays.
- Opinions and blame in the report.
- Editing old reports without a dated note.
- A form so long the foreman skips it on busy days, which are the days you most need it.
A note on tools
Paper forms, a shared spreadsheet and job management apps all work if the report gets written every day. If you’d rather not adapt someone else’s form, Floot can build a daily report app from a plain-English description of your own fields, with photos stored on the job and the office notified when a delay or extra work is reported. It’s free to start.
Frequently Asked Questions
What should be included in a daily job report?
Date, job and crew with hours, weather and site conditions, work completed with quantities, materials and equipment, delays and problems with times, extra work requested, customer or inspector contact, safety notes, photos and the plan for tomorrow.
Who should write the daily report?
The foreman or lead on site, before leaving for the day. It should be one named person per job, with the time to do it counted as paid work.
Are daily reports legally required?
No general federal law requires a daily report for private work, though contracts, public projects and some inspections do require written records. Their value is mostly as proof: a record made at the time, as a regular practice, is the kind courts generally treat as reliable.
How detailed should a daily report be?
Detailed enough that someone who wasn’t there can tell what got done, what went wrong and who said what. That usually means quantities, times and names, not long paragraphs.
Should I include photos in daily reports?
Yes. Attach photos of the start and end of the day, progress, anything that will be covered up, and any damage or surprise conditions you find. Store them with the job and date, not in personal phones.
How do I prove a weather delay?
Record the observed conditions on site with start and end times in the daily report, then back it up if needed with NOAA’s Climate Data Online, which offers free historical daily weather by station.
Sources
- Federal Rules of Evidence, Rule 803(6), Records of a regularly conducted activity (Cornell LII) https://www.law.cornell.edu/rules/fre/rule_803
- OSHA, 29 CFR 1926.20, General safety and health provisions https://www.osha.gov/laws-regs/regulations/standardnumber/1926/1926.20
- OSHA, 29 CFR 1926.651, Specific excavation requirements https://www.osha.gov/laws-regs/regulations/standardnumber/1926/1926.651
- OSHA, 29 CFR 1904.39, Reporting fatalities, hospitalizations, amputations and losses of an eye https://www.osha.gov/laws-regs/regulations/standardnumber/1904/1904.39
- NOAA National Centers for Environmental Information, Climate Data Online https://www.ncei.noaa.gov/cdo-web/
- U.S. Department of Labor, Fact Sheet #22: Hours Worked under the FLSA, 2008 https://www.dol.gov/agencies/whd/fact-sheets/22-flsa-hours-worked