Preconstruction photo documentation creates a visual baseline of a site before work changes it. Record the areas the project may affect, connect each condition to a recognizable location, and identify anything you could not see. Review the set before mobilization, demolition or protection work makes the original conditions harder to establish.
For a superintendent preparing a renovation or a contractor organizing site access, the useful question is simple: could someone who missed the walkthrough understand what was visible, where it was, and what remains unknown?
Define the baseline before taking photos
Start with the work limits and the activities that could change surrounding conditions. A room renovation may affect a loading entrance, elevator lobby and delivery corridor as well as the room itself. A utility project may affect pavement and landscaping beyond the excavation.
Agree who will capture the record, which areas can be accessed, who reviews it, and when the set must be ready. Check the project’s own documentation requirements for notice, attendance, required views and submission format. A general checklist cannot establish those requirements for every job.
Public agencies illustrate the purpose. The Los Angeles Bureau of Engineering describes preconstruction photographs as a record of existing conditions and calls for the first contractor photographs before site construction begins in the contracts it describes. Treat that as an example of a project owner’s process, not a rule for every project.
Use a marked reference plan or a simple area list to define the route. Include access routes, staging areas and nearby surfaces that could be affected. Obtain the necessary access permission before including neighboring property. Assign clear location names that the field team and reviewer will both recognize.
What to photograph before construction starts
Adapt the following coverage list to the agreed scope. Record ordinary visible conditions as well as noticeable damage; a folder containing only close-ups of defects cannot explain the full area reviewed.
- Work area: overall views of the site, room or elevation before alteration, with recognizable boundaries and features.
- Access and staging: entrances, corridors, loading areas and surfaces along planned material or equipment routes.
- Existing surfaces: relevant walls, floors, ceilings, doors, glazing, paving and other finishes that will remain.
- Visible conditions needing attention: cracks, chips, staining, displaced components or worn areas, paired with a location view.
- Adjacent infrastructure: relevant curbs, sidewalks, drainage features, landscaping and other assets within the agreed coverage.
- Coverage limits: locked rooms, stored materials, poor visibility and other conditions preventing a useful observation.
For a concrete municipal example, the City of Delta’s preconstruction photo checklist asks about damage to infrastructure along a property’s frontage, including curbs, roads, sidewalks and drainage assets. Its location and inspection-date fields help tie those observations to a particular visit.
For a broader reference across the job lifecycle, use Filio’s construction photo documentation checklist. This pre-start walkthrough has a narrower purpose: establish the visible starting condition before work alters it.
Walk a repeatable route and record the gaps
Choose a starting point and move through the agreed areas in a consistent order. In a building, that might mean the delivery entrance, the access corridor, then each work room. Outdoors, it might mean a sequence of named frontage sections. The route should make missing areas noticeable during review.
At each location, take enough context to identify the area, then closer views of relevant conditions. Check focus, glare and lighting while you are still there. A sharp close-up of a chipped tile has limited value if the reviewer cannot tell which room or threshold it belongs to.
Mark areas you could not inspect as “not observed” and record the reason. A floor hidden beneath stored materials is different from a visible floor with no damage noted in the captured views. Neither a blank folder nor a distant photograph establishes that an inaccessible area was in good condition.
Follow-up is an action, not evidence that an area was inspected. Give each gap a follow-up owner in the project’s existing process. If access becomes available later, capture a dated supplement and state what changed between visits. Do not quietly fold later photographs into the original baseline as if they were taken at the same time.
Write condition notes that stay with the evidence
A useful condition note identifies the location, describes what is visible and references the relevant images. Add the visit date and photographer or recorder so a reviewer can follow up. When direction matters, use a clear reference such as “looking toward the loading entrance.”
Keep the observation separate from a diagnosis. “Discoloration visible below the window sill” describes the image. “The window leaks” attributes a cause that may require further investigation. If someone supplies an explanation, identify it as their statement rather than turning it into an observed fact.
The Federal Highway Administration’s inspection guidance recommends recording observations on site or immediately afterward and distinguishing supported observations from opinion. That reporting discipline is useful when preparing a baseline, even though the guidance addresses FHWA inspection work.
Example: a corridor before a renovation
Consider an illustrative walkthrough before a contractor starts moving materials through a school corridor. The team sees a chipped tile at the west doorway, while stored furniture obscures part of the east wall.
- Location: Level 1, corridor C-01, west doorway. Observation: chipped edge visible on the floor tile beside the door frame. References: context image EC-014 and detail image EC-015.
- Location: corridor C-01, east wall. Limitation: lower wall behind stored furniture not visible during this visit. Follow-up: the site lead coordinates access for a supplementary record before deliveries.
These example IDs describe a reporting method, not a Filio field requirement. The first note records a visible condition. The second preserves an information gap. Neither assigns responsibility for damage or certifies the condition of the building.
Review time and location information alongside the images and visit notes. Metadata can provide context, but it does not by itself prove a condition’s cause, exact position or history. See the construction photo metadata review for the limits of timestamps and GPS.
Review the record before the site changes
Ask a reviewer to work through the agreed coverage list while the team can still return to the site. Organize the set by area so the reviewer can answer five questions:
- Can I identify every area that was included in the walkthrough?
- Can I place each important detail using its location view and note?
- Are the relevant conditions clear enough to review at a useful image size?
- Are inaccessible or obscured areas stated explicitly, with follow-up identified?
- Can I distinguish the original visit from later additions and find the referenced source images?
Correct gaps in the record where access and timing permit. Keep the original images and make the relationship between source records and any annotated copies clear. A concise reviewed report can summarize the set, but it should not imply complete coverage when exclusions remain.
If the project requires an owner’s acknowledgment or a formal submission, use that established process. A report being generated, emailed or opened is not the same as an authorized person accepting it.
Use Filio to organize and report the field records
Filio supports capturing project photos, organizing records with tags and context, and assembling selected field records into reports. Those capabilities can support the baseline workflow when the team supplies useful location references and condition notes.
Use the project’s agreed naming and tagging conventions to distinguish existing-condition records from later construction photos. Review the selected records and report content before sharing. Filio’s guide to creating construction photo reports explains the reporting workflow in more detail.
The coverage review and decisions about observations remain with the project team. Organizing photos or exporting a report does not establish that every area was inspected, determine the cause of damage, or replace any required specialist assessment.
Questions to resolve before the first walkthrough
How many preconstruction photos are enough?
Start with the project’s requirements, then check coverage rather than aiming for an arbitrary total. The set should let a reviewer identify the agreed areas, understand relevant visible conditions and recognize the limits of the visit. Additional images are useful when they resolve a specific missing view or unclear detail.
What if work has already started?
Document the conditions that are still observable and state when the record was made. Identify any earlier photographs by their actual source and date, and keep uncertainty visible. A later record should not be presented as a complete pre-start baseline. Route unresolved questions through the project’s responsible reviewer.
Make the starting condition understandable
A useful baseline connects photographs, locations, observations and limitations. The practical test is whether another person can understand the starting condition without relying on the photographer’s memory.
As construction progresses, maintain separate records for later stages, including concealed work before it is covered. Keep those records connected to the project history without changing what the original baseline says.
Talk with Filio about organizing your field photos and preparing reviewed reports for your next project.
