Guides / Field reports
How to write a construction field report
Short answer: A construction field report records what you saw on a specific site visit, on a specific date, and what needs to happen next. Put the project, date, time, weather, who was there and why you came at the top. Then list numbered observations, each with a location, a plain description, a reference to the drawing or spec, a photo and a status. Close with open items carried from the last visit, required actions with an owner, and your name and signature. Send it the same day.
Owner's reps write them. So do architects doing construction administration, engineers of record, third-party inspectors and lenders' construction monitors. The names change (site visit report, field observation report, field report) but the job is the same: leave a dated record that someone who was not on site can read six months later and understand.
What a field report is for
Most field reports get read twice. The first time is the next morning, by the GC's project manager deciding what to fix. The second time is months later, when there is a dispute about a change order, a schedule delay or a defect, and someone pulls every report from that period. Write for the second reader. They don't know the site, they don't know who "Mike" is, and they will notice if a report says "looks fine" with no photo.
A good report does three things:
- States what was observed, where, and when.
- Compares it to what the contract documents require, when that's within your scope.
- Says what happens next and who owns it.
It does not certify work you didn't see. If you looked at the second floor and not the third, the report says so.
What to include in a construction field report
Header information
This is the part people skip when they're in a hurry, and it's the part that makes the report usable later. Include the project name and address, permit or job number, report number, date of visit with arrival and departure time, weather and temperature, the purpose of the visit, and the people you met (name, company, role). If the GC's superintendent walked with you, name them.
Work in progress
A short paragraph on what trades were on site and roughly what stage the job is at. "Framing crew of six on Level 3, MEP rough-in ongoing on Level 2, drywall delivery staged at the north entrance." This puts your observations in context and helps the schedule people.
Observations
The core of the report. Number every item so it can be tracked across visits. Each one needs:
- Location: grid line, floor, room number or elevation. "Level 2, grid C-4" beats "near the stairs."
- What you saw, in measurable terms when you can. "Rebar spacing measured 14 in. o.c.; drawings call for 12 in. o.c. (S-201, detail 4)."
- A photo reference.
- A status: open, closed, or for information.
- The action required, if any, and who is responsible.
Items from previous visits
Carry every open item forward until it's closed. Note when it was first raised. An item that shows up on five reports in a row tells a story that a single report can't.
Sign-off
Your name, title, company, license number if you're a licensed professional and it's appropriate, and signature. Add a distribution list so there's no argument later about who received it.
Template outline
Field report template
- Project name, address, permit or job number
- Report number and date of visit; time on site
- Weather and site conditions
- Purpose of visit (scheduled, requested by owner, pre-pour, follow-up)
- Present on site: name, company, role
- Work in progress at the time of the visit
- Observations: number, location, description, reference, photo, status, action, responsible party
- Open items from previous reports and their current status
- Required actions and deadlines
- Limitations: areas not observed, access issues
- Prepared by, signature, date issued
- Distribution list
Photo practice that holds up later
Photos carry more weight than text in most disputes, but only if someone can tell what they show. A close-up of a crack with no reference point is nearly useless.
- Take a wide shot first to show location, then the close-up.
- Put something in the frame for scale: a tape measure, a pen, a hand.
- Shoot the grid line marker, the room number or a column tag when you can.
- Keep the date and time stamp. Don't edit originals; mark up a copy.
- Caption each photo with the observation number it supports.
- Photograph the good conditions too. "Firestopping at Level 2 penetrations complete" with a photo protects everyone.
Arrows and circles on a marked-up copy help the reader find the issue fast. Keep the unmarked original in your files.
Writing the observations
Write what you saw, not what you think happened. "Water staining on ceiling tile at Room 214, approximately 2 ft by 3 ft" is a fact. "Roof is leaking" is a conclusion, and it might be a condensate line.
Some habits that help:
- One issue per item. Don't bundle three problems into one paragraph; they get closed at different times.
- Use the drawing and spec references the contractor uses.
- Avoid "approved" or "accepted" unless that's in your role and authority. "Observed" and "appeared to be" are there for a reason.
- Skip adjectives. "Poor workmanship" invites an argument; "mortar joints 3/4 in. to 1 in., spec calls for 3/8 in." does not.
If you struggle with wording in the truck, an assistant can help clean up dictated notes. Arazim Reports, for example, can suggest clearer phrasing for an observation, but the facts and the judgment stay yours.
Common mistakes
- Sending it a week later. Memory fades and the issue is already covered up by drywall.
- No limitations section. If you couldn't access the roof, say so, or the report implies you checked it.
- Vague locations. "East side" on a building with four east-facing wings doesn't help anyone.
- Dropping open items. If it was open last time and you didn't check it, list it as "not reviewed this visit."
- Directing means and methods. Telling a sub how to do the work can shift responsibility to you. Note the deficiency and the requirement, and let the GC sort out the fix.
- Photos without captions, dumped at the end of the PDF.
If the visit is a formal inspection against a checklist, see the site inspection report guide. For the contractor's own daily record, see construction daily logs. And if the visit ends with a walkthrough of finish items, that's a punch list.
Write the report before you leave the site
Arazim Reports puts your notes, marked-up photos and signature into a PDF on your own letterhead. It works offline, so a basement with no signal is not a problem.
Start free trial 14 days free, no credit card. Then $10/month for your first year.FAQ
What is the difference between a field report and a daily log?
A daily log is kept by the contractor every working day and covers manpower, equipment, deliveries, weather and work performed. A field report is written by a visitor, such as an owner's rep, architect, engineer or inspector, after a specific site visit. It focuses on observations and required actions.
How long should a construction field report be?
As long as it needs to be and no longer. A routine visit is often one or two pages plus photos. A pre-pour or problem visit may run longer. Numbered observations with photos are easier to read than long paragraphs.
Who should receive the field report?
Typically the owner or owner's rep, the architect, the GC's project manager and superintendent, and any consultant whose work is affected. Follow the distribution set out in your contract and list the recipients on the report itself.
Should a field report say the work is approved?
Only if approving that work is within your role and contract. Most field reports record observations and conformance concerns. They do not accept work or relieve the contractor of its obligations. When in doubt, check your agreement and write "observed."
How many photos should a field report include?
At least one per open observation, usually a wide shot and a close-up. Add photos of key work that was done correctly. Caption each one with the observation number so the reader can match them.