Field Observation Report: What to Include and How to Write One

A field observation report is a structured record of what you saw, heard and measured at a site or event, written so someone who wasn’t there can rely on it later. A good one names the place, the date, the observer and the scope. It separates fact from interpretation, attaches evidence, and ends with who must do what by when. The exact format depends on your discipline and contract, so this guide covers the parts that stay the same and shows where they change.

TL;DR

• Every report needs five blocks: administrative details, conditions, scope, observations, and recommendations with sign-off.
• Keep description and interpretation apart. Write what you saw first, then what you think it means.
• State what you did not observe. An architect’s report is not an exhaustive inspection unless the agreement says it is.
• A photo is evidence, not a conclusion. Give each one a location, a time and a plain caption.
• For design teams, record the reason behind each observation and decision, not only the list of findings.

Table of Contents

• What a field observation report is, and what it is not
• The five blocks every report needs
• How to write it, step by step
• Separate what you saw from what you think
• Scope: say what you did not observe
• Photos and evidence
• Safety observations are a different animal
• What design teams need beyond the standard template
• Our perspective: the report is the start of the record
• Turning conversations into records
• A checklist to copy
• FAQ
• Sources

What a field observation report is, and what it is not

People use “field report,” “site observation report” and “construction observation report” almost interchangeably. They overlap in what they record: date, place, observer, evidence and findings. They differ in purpose.

There is no universal format. The structure depends on the contract, the research question, the discipline and the audience. Do not assume one type can stand in for another. A municipal form, for example, defines a structural observation as visual observation for general conformance at significant construction stages. It does not replace required inspections.

The five blocks every report needs

Pages that rank for this topic converge on the same skeleton. Here it is, with the reason each block exists.

1. Administrative information

Project name, site address, observer and their role, date, arrival and departure times, and who else was present. This is what lets someone find and trust the report six months later. Add a report number if you will write more than one.

2. Conditions

Weather, temperature, access limits, and anything that affected what you could see. A report that says nothing about conditions invites the question of whether the slab was wet, the light was poor or a trade was absent.

3. Scope

What the visit was for, which areas you walked, and which you did not. This is the block most people skip, and the one that protects you most. More on this below.

4. Observations

Numbered, specific and located. “Framing at Level 2, gridline C to E: blocking not yet installed at the north wall” beats “framing incomplete.” Pair each item with a photo reference.

5. Recommendations and sign-off

For each finding that needs action: the proposed correction, a responsible owner, a due date and a status. Close with a signature or acknowledgment and a distribution list.

How to write it, step by step

The method below draws on the USC research guide to field reports, adapted for professional site work.

1. Define the question and the boundaries. Why are you there? A progress check, a deficiency walk, a critique, a client review? Write one sentence and keep it at the top.
2. Take notes during the visit or right after. Observations only become data when they are recorded. Memory edits quickly.
3. Describe, then interpret. Use who, what, where, when and why. Put what you saw in one place and what you think it means in another.
4. Look for patterns. Was the same issue present at three locations? Was something unusually good or bad compared with earlier visits?
5. State conclusions and limits. Say what you can support and what you cannot.
6. Assign actions. Every recommendation gets an owner and a date, or it is just an opinion.
7. Review, sign and distribute. Check facts against photos before it leaves your hands.
8. Revisit open items. The next report should open with the status of the last report’s findings.

USC suggests writing in the past tense for completed fieldwork. That convention also helps a site report: it signals that you are recording, not predicting.

Separate what you saw from what you think

One practical framework is the 3 Cs: context, content and concepts, designed for recording unstructured field observations.

• Context: who was present and why the observation happened.
• Content: what was actually seen or said.
• Concepts: the pattern, implication, decision or question that follows.

This matters because interpretation hardens into “fact” quickly. Six weeks on, nobody remembers that “the contractor seems behind” was a guess prompted by an empty laydown area. If the report keeps the layers apart, the reader can see the evidence and judge the inference.

A short worked example

Notice that the last column names an unresolved question. It does not pretend the answer is known.

Scope: say what you did not observe

For architects, scope is the professional boundary. The AIA’s G711-2018 Architect’s Field Report is a form for documenting site observations during visits, tracking progress, quality and compliance with contract standards. The form is meant for periodic visits, or for a daily log if there is a full-time project representative, per the AIA’s instructions. It does not turn every visit into an exhaustive or continuous inspection unless the agreement says so.

The Ontario Association of Architects describes the same idea in its practice manual: the duty during field review is to make sufficient periodic site visits to determine general conformity with the contract documents. Contract terms differ by country and by agreement, so check yours.

In practice:

• Write the observer’s role in the header.
• List the areas observed and the areas not observed.
• Avoid words like “approved,” “complies” or “certified” unless your contract calls for them.
• Put limits next to the findings they affect, not in a boilerplate footer nobody reads.

If a report involves a regulated structural observation program, follow the jurisdiction’s form. The Long Beach form, for instance, ties observation to significant construction stages, and unresolved deficiencies can require re-observation and a final report. Check with your engineer of record and local building department about what applies to your project.

Photos and evidence

A photo shows a condition. It does not say what the condition means. For each image, record:

• observation number it supports
• exact location (level, gridline, room)
• date and time
• direction or view context
• a plain-language caption

Then connect the image to an owner, a corrective action or a follow-up date. A folder of unlabeled phone pictures is not documentation. It is a search task for whoever inherits the project.

Safety observations are a different animal

If your report is about safety, the content changes. A safety observation is a proactive record of safe behavior, at-risk behavior, a hazard or a near miss before an injury occurs. A useful one states what was seen, where and when, the risk or severity, evidence, immediate control, corrective action owner, due date and verification status.

A 2022 peer-reviewed study of US dairy-product manufacturing facilities found safety observations among the six leading indicators participants ranked highest for perceived effectiveness. Treat that carefully. Leading indicators are meant to reveal worsening conditions early, but a high count of reports does not by itself prove a site is safe. Use these reports to prompt action. For a specific hazard on your site, bring in your safety officer or a qualified safety professional.

What design teams need beyond the standard template

Standard templates answer “what did we see?” Design teams also need “why did we decide this?” A critique, a client walk-through or a coordination meeting generates observations, but the value sits in the reasoning attached to them.

For design critiques, client reviews and project conversations, a reliable record keeps:

• source, date and participants
• direct evidence (what was said or seen)
• interpretation, kept separate
• decision or design intent
• risk
• action, owner and due date
• commitment made, and by whom
• unresolved questions and what would reopen the decision
• next review date

Capture dissent too. USC’s guidance treats analysis as an argument grounded in evidence, which maps well onto critique: a record that preserves the competing rationale is a defensible design rationale, while a list of opinions is not. Forcing premature agreement on paper only creates a fight later.

If you want templates for the surrounding documents, our guides on site meeting minutes, design review notes and a design documentation template cover the adjacent formats.

Our perspective: the report is the start of the record

We build project memory software, so we see the same failure in studio after studio. The field report gets written, filed and forgotten. Three months later someone asks why the corridor ceiling was lowered, and the answer lives in a conversation nobody wrote down, or in a PDF that lists the change without the reason.

A report tells you what was observed on a given day. It rarely tells you why the team responded the way it did. That reasoning is what junior designers need when they inherit a task and wonder where it came from. It is also what a principal needs when a client disputes a decision.

Our view is simple. Treat each observation as a traceable record: what was seen or said, who was there, what was decided, what risk it carries, who owns the next step, and which question is still open. Keep a link from each decision back to the conversation it came from. Keep interpretation labeled as interpretation. Say plainly what the report does not cover.

None of this requires software. A disciplined template and a habit of writing the “why” next to the “what” get you most of the way. Software helps when the volume of conversations outgrows what one person can keep tidy.

, Rajas

Turning conversations into records

Most of the reasoning behind a field observation happens in conversation: the site walk, the critique, the client call. The Intent Ledger turns meeting notes, transcripts, critique feedback and client comments into ILM Records, structured and source-backed records of decisions, design intent, risks, actions, commitments and unresolved questions, each traceable to the conversation it came from.

If you want to try it on a single project, the Project Record pack is a $29 one-off purchase. Working Memory is $29 per month for ongoing use, and the Studio Ledger pack is a $119 one-off purchase. See all options on the pricing page, or read more at The Intent Ledger.

A checklist to copy

Before you send the next report, check:

1. Header complete: project, address, observer and role, date, times, attendees.
2. Purpose stated in one sentence.
3. Conditions noted.
4. Areas observed and not observed listed.
5. Observations numbered, located and written in the past tense.
6. Description and interpretation kept apart.
7. Every photo captioned and tied to an observation.
8. Every recommendation has an owner, a due date and a status.
9. Open questions listed, not smoothed over.
10. Signature or acknowledgment and distribution list.

If you also track what clients say on site, our guides to client comment tracking and client meeting documentation show how to give those comments owners and dates.

FAQ

What is the difference between a field report and a site observation report?

A field report is the broader term. It covers daily logs, site visits and research fieldwork. A site observation report is a field report focused on site conditions and deficiencies at a particular time. In practice, many firms use the terms interchangeably, so follow what your contract or instructor specifies.

How do you write a good observation report?

Define the question and boundaries first, take notes during or right after the visit, and describe what happened using who, what, where, when and why. Keep description separate from interpretation. End with conclusions, recommendations and limitations, and attach evidence such as photos.

Does an architect’s field report certify the work?

Not by default. AIA guidance describes the G711-2018 as a record of periodic or daily observations, and it does not automatically mean exhaustive or continuous inspection. State what you observed and what you did not, and avoid language that implies certification unless your agreement calls for it. For your own contract, ask your attorney or professional liability insurer.

What is a safety observation?

It is a proactive record of a safe behavior, at-risk behavior, hazard or near miss, made before an injury or loss occurs. A good one notes the location, risk, evidence, immediate control, corrective action owner, due date and verification status.

Sources

• FAQs: G711-2018, Architect’s Field Report (AIA Contract Documents)
• Instructions: G711-2018, Architect’s Field Report (AIA Contract Documents)
• FORM-021 Structural Observation Report (City of Long Beach)
• 2.3.11 Contract Administration, Field Functions (Ontario Association of Architects)
• Writing a Field Report (USC Libraries)
• The 3 Cs of Content, Context, and Concepts (PMC)
• Safety leading indicators study, dairy-product manufacturing (PMC)

Recommended

• 46% Less Documentation, Traceable Design Meeting Notes for Design Teams
• Record of Decision: 8 Fields Design Teams Must Capture
• Design Documentation Template: Capture Decisions, Not Just Tasks
• Site Meeting Minutes: What to Record and a Template