How to Write a Daily Field Report (Template)
A daily field report is the record of what happened on a site on one day, written by someone who was there. Its value shows up later: when a pay application is questioned, when a schedule slips and someone asks when the problem first appeared, when a contractor and an owner remember the same conversation two different ways. A report written on the day settles those questions. A report reconstructed a week later starts them.
This guide covers what belongs in a daily report, how to write each section so it is useful in six months, and the habits that make it hold up. The template at the end follows the same structure.
What a daily field report is for
Three things, in order of how often they matter:
- A record written on the day. Dated, factual, written before memory has a chance to drift. In a dispute, a daily written at the time carries weight that memory and email threads do not.
- A progress signal. The owner, the GC, or your own manager should be able to read it in two minutes and know whether the day went to plan.
- The source for everything downstream. Weekly summaries, punch lists, RFIs, and closeout documentation are easier to build from clean dailies than from a camera roll.
It is not a diary, a place for opinions about the crew, or a substitute for the safety log, the RFI log, or the change order process. It points to those; it does not replace them.
The header
Every daily report needs the same identifying block at the top, so a page pulled out of a binder or an email attachment still stands on its own:
- Project — name and number
- Customer — the entity paying for the work
- Site — location, including the building or area if the project spans several
- Date — the day the report covers, not the day it was written (they should be the same)
- Prepared by — your name and role
- Captures from — if the report covers more than one day, the range
Weather, crew count, and equipment on site are worth a line each on construction projects. On a plant or facility job they matter less than which systems were down and which were live.
The five sections
The order below is deliberate. A reader with two minutes reads the summary and stops. A reader with ten reads down to next steps. A reader with a problem goes straight to issues and safety.
1. Summary
Three to five sentences. What was the plan for the day, what got done, and the single most important thing a reader needs to know. If the day went to plan, say so in one line and move on.
Write it last, after the other sections are filled in. A summary written first tends to describe intentions rather than results.
Weak: "Good progress today, a few issues but overall on track."
Better: "Demolition of the north wall plate complete; contractor found corroded steel behind it (see Issues). Electrical rough-in in Room 104 started a day early. One recordable safety observation, closed on site."
2. Work Performed
The factual account of what was done, by whom, and where. One line per activity, in the order it happened or by area. Include quantities where they exist — linear feet installed, panels set, tests completed — because quantities are what the pay application will be checked against.
Name the contractor or trade, not individuals, unless the individual matters (an inspector, an engineer of record, a customer representative making a decision).
Example lines:
- 07:30–11:00 — ABC Mechanical removed existing plate and insulation, north wall, Grid C-4 to C-7 (approx. 22 LF).
- 10:15 — Owner's representative on site; confirmed light/medium/heavy repair options requested for the steel condition below.
- 13:00–16:30 — DEF Electrical began conduit rough-in, Room 104 (ahead of the Wednesday plan).
3. Issues
Anything that is not going to plan, or that someone is going to ask about later: unforeseen conditions, delays and their cause, coordination conflicts, missing materials, decisions that are waiting on someone.
For each issue, record four things: what was observed, where, who was told, and what is expected to happen next. If a photo exists, reference it. If a decision is needed, name whose decision it is. This is the section that generates RFIs and change requests, so write it as if you were about to draft one.
Example:
- Existing steel behind the north wall plate shows section loss at Grid C-5 (see photos 3–5). Contractor to field-verify extent before repair. Owner requested light, medium, and heavy repair options for review. RFI to follow. Decision needed by: owner's representative.
Do not soften it. "Some minor concerns with the steel" will read as negligence later if the steel turns out to matter.
4. Safety
Observations, near misses, incidents, toolbox talks held, permits issued or closed, and corrective actions taken. If nothing happened, write "None reported." A blank safety section reads as "not checked." A "None reported" reads as "checked, nothing found."
Record what was done about an observation, not only that it was made. "Extension cord across walkway in Room 104 — moved and re-routed on the spot, discussed with the electrical foreman" is complete. "Cord in walkway" is not.
5. Next Steps
What is planned for tomorrow, what is waiting on whom, and any dates. Keep it short and specific. This section is what the next day's summary will be measured against, and it is the fastest way for a manager to see whether the project is being driven or drifting.
Example:
- ABC Mechanical to expose full extent of steel corrosion, Grid C-4 to C-7, and mark up for the structural engineer.
- DEF Electrical to continue Room 104 rough-in; inspection requested for Thursday.
- Owner's representative to confirm repair-option review meeting (proposed Friday 10:00).
Site photos
Photos are the part of a daily report that cannot be argued with, provided they are labeled. A photo with no caption, no location, and no time is a picture of a wall. For each photo the report should carry:
- a caption saying what the photo shows and why it was taken
- the location (grid, room, elevation, or equipment tag)
- the time it was taken
- a tag or category — progress, issue, safety, existing condition, completed work
Eight to twelve photos is usually enough for a day. More than that and the report becomes a gallery nobody reads; the rest can stay in the project file.
The rules that make a daily report hold up
Same day, every day. A daily written the next morning is already a reconstruction. If the day ended in the truck, the notes from the truck are the report.
Facts, then interpretation, clearly separated. "Contractor did not have the submittal on site" is a fact. "Contractor is disorganized" is an opinion, and it will be read aloud in a room you are not in.
"None reported." beats blank. Every section gets filled. An empty section is ambiguous; a "None reported" is a statement.
Measurements carry their method. A tape reading and an estimate from a phone camera are not the same thing. Note which one it was, and field-verify anything a decision depends on.
Names on decisions. Every open item in Issues and Next Steps names the person or role who owns the decision. "Pending owner decision" without a name is how things stall.
Keep it to two pages. If it is longer, the detail belongs in an attachment or the project file, and the report should reference it.
Common mistakes
- Writing the summary first. It ends up describing the plan, not the day.
- Recording that a problem exists without recording who was told. The report should show the communication happened.
- Skipping the safety section on a quiet day. The quiet days are exactly when a blank section looks worst.
- Photos in the camera roll, captions in your head. Two weeks later neither is findable.
- Mixing yesterday's catch-up into today's report. Date each entry to the day it happened, even if it is being written down late — and say it is being written down late.
Download the template
The template follows the structure above exactly: the project header, the five sections with fill-in prompts, and a site photo log. It prints in black and white and works in Word or as a PDF you fill by hand.
How FieldBinder AI produces this report
The sections above are the same five sections FieldBinder AI generates from a project's captures. The app works from what was recorded in the field — photos with captions, voice notes cleaned into field notes, tagged issues, safety observations, measurements — and drafts the Summary, Work Performed, Issues, Safety, and Next Steps sections from those captures only. Photos appear in a site photo log with their captions, tags, and times. The result is an editable draft: you review it, correct it, and export it as a branded PDF or copy the text into an email.
The draft is a starting point, not a signed document. Every generated report is marked as AI-assisted, and you are responsible for reviewing it before it goes to a customer. What the app removes is the hour of reconstruction, not the judgment.
AI report generation is part of the Pro plan; capture and organization by project are included on every plan. See pricing · How it works for project managers
Frequently asked questions
How long should a daily field report be?
One to two pages. Long enough to record what happened, short enough that the people who need to read it will. Detail beyond that belongs in attachments or the project file.
Who should write the daily report?
The person who was on site and responsible for the work that day — a superintendent, project manager, owner's representative, or engineer conducting the site visit. It should not be delegated to someone who was not there.
Should I write a report on days when nothing happened?
Yes. "No work performed — weather" or "No site activity; awaiting material delivery" is a record that matters when the schedule is reviewed. A missing day looks like a missing report.
What is the difference between a daily report and a daily log?
In practice the terms are used interchangeably. Some firms use "log" for a short, form-based entry and "report" for a narrative document sent to the owner. The structure in this guide works for either.
Can a daily field report be used in a dispute?
Daily reports written on the day are routinely relied on in schedule and payment disputes, which is the reason to write them on the day, in fact-based language, with dated photos. This guide is not legal advice; ask your counsel how your project's records should be kept.
