A first construction site visit can feel like proof that you finally work on real buildings. You arrive, take dozens of photographs and return with a folder of images. The next day somebody asks what changed, which drawing the issue concerns and who must act. If the photos cannot answer, the visit produced memories rather than a useful project record.
Site observation is a supervised professional activity. The NCARB Construction and Evaluation experience description includes site visits, meetings, documentation and evaluating work against design intent. The precise duty of an architect depends on the contract and jurisdiction. This guide teaches a junior employee how to support that process, not how to assume authority they do not have.
Read before you travel
Ask your project lead why the team is visiting now. Is the purpose to observe progress, review a mock-up, answer a contractor question, meet the client or examine a particular condition? Obtain the current drawings, relevant specifications, last field report, open RFI or issue list and site access requirements. If you do not know the reason for the visit, you will photograph whatever looks interesting rather than the decision that matters.
Mark three priority questions in advance. For each, note the document reference and the person who can answer it. For example: “At grid B-4, has the wall opening been formed to the current approved dimension?” is more useful than “check walls.” Carry a safe, accessible copy of the relevant documents and follow site rules for personal protective equipment, induction and photography. Do not assume you may enter every area or share every image.
Agree with the senior architect what you may say on site. Can you clarify the location of a drawing? Can you note a question? Can you instruct a contractor to change work? These are different levels of authority. If you are unsure, record the question and route it. A confident guess given aloud can become an unofficial instruction with real cost.
Record observations, not conclusions you cannot support
The useful unit of a field note is a specific observation with a location, date, source and next action. “Door not right” is too vague. “Level 2, room 214, opening observed about 150 mm east of location shown on A-202 revision C; verify dimension and review with project architect” is traceable. If you did not measure it, do not pretend that “about” is an exact survey result. Note how the dimension was obtained and any obstruction.
Separate what you saw from what someone told you. Write “contractor stated the partition was relocated on Tuesday” as a reported statement, not as a verified fact. Separate a concern from a defect. You may see a condition that appears inconsistent with a drawing, but another approved change may explain it. The field report should make the question visible so the authorised person can decide.
Use a repeatable note format: item number; location; photograph reference; drawing or specification reference; observation; question; owner; due date or next review. Add status later: open, answered, action in progress or closed with evidence. If your office already uses a field-report template, follow it. The purpose of the fields is to keep the decision from disappearing between a camera roll and a meeting.
Make photographs answer a question
An AIA practice note on site photography explains both the value and risk of photos in documenting observations. A photo can show the context of work; it can also be misread without a location or the reason it was taken. Take an overview that locates the issue, then a closer view with a clear reference, subject to safety and site rules. Record the direction of view and the relevant drawing number. Avoid photographing people, confidential client areas or restricted equipment without permission.
Do not rely on the camera’s automatic filename as your index. Link each image to a numbered note before the details blur. If you use a phone, follow the firm’s policy for storage and transfer; client project images should not sit indefinitely in a personal gallery or consumer cloud account. Capture enough to support the observation, then place the images in the approved project record.
Review the image before leaving the area. Is the issue visible? Could someone who was not there identify the room and element? A close-up of a joint may be meaningless without a wider shot. Conversely, a wide image may conceal the condition that prompted the note. If a photo cannot show it, add a quick sketch with dimensions or ask the senior colleague how to document it.
Keep the site conversation disciplined
Contractors often need timely answers. Be helpful without inventing authority. Listen, repeat the question in your own words and confirm the drawing or document they are using. Then state how it will be routed: “I will record this for the project architect and confirm the response through our agreed process.” That is more useful than an uncertain “should be fine.”
If a question appears urgent for safety or imminent covering-up of work, alert the appropriate senior person through the project’s escalation route immediately. A field note is not a substitute for timely communication. The contractor remains responsible for its own means, methods and site safety under the applicable contract; do not casually take over that responsibility because you happen to be present.
At the end of the visit, compare your priority questions with what you actually learned. Which were answered by observation? Which require a consultant, client or contractor response? Which cannot be verified until another stage? Tell the lead architect before leaving if a decision affects work happening that day.
Close the loop back in the office
Upload notes and images to the approved location promptly. Send a concise summary: purpose of visit, significant observations, decisions needed, owners and timing. Check the office’s formal report and review process before anything is issued externally. A junior employee can draft a report; the person with professional authority reviews it.
Do not call an item “resolved” merely because somebody discussed it. Record the approved response, whether a revised document or formal instruction is needed and how the team will confirm the action. An issue may be resolved by a drawing revision, an RFI response, a contractor correction, a client decision or a later inspection by an appropriate specialist. Your log should show which path was chosen.
This is where a site visit becomes valuable to your learning. Return to the drawing that described the observed condition. Did the design intent survive construction? If not, was the problem in the documents, an approved change, a coordination gap or a method the project team could not control? Ask your supervisor. That discussion is more educational than the photograph alone.
Keep a private learning note separate from the official project record. The official report should contain facts, agreed actions and reviewed language. Your personal note can say what surprised you, which drawing you failed to find quickly and what you will prepare differently next time. Do not mix speculation into a report that a client or contractor may rely on. The separation makes both records more useful.
Build a safe work sample for your career
You may not be allowed to show a live field report in a job application. You can still describe the method, with permission and without confidential details: “I logged observations against the current drawing issue, routed three consultant questions and updated the action register after review.” If you create a hypothetical example, label it as such. Show the difference between observation, question and authorised response.
A good junior site visitor does not need to know every answer. They need to return with a record that lets the right person answer. Location, evidence, document reference, owner and closure are the five pieces that turn a photo walk into a professional contribution.
Browse current architecture jobs on Jobs.archi and compare your next step with our guide for recent architecture graduates.
The post A Site Visit Is Not a Photo Walk: A Junior Architect’s Field Note Method first appeared on jobs.archi.