You walk a 200,000-square-foot building, photograph a cracked expansion joint on the roof, a dripping valve in the mechanical room, and a blocked fire exit on the third floor, then move on. Three months later, an insurer asks you to prove you flagged that exit and that a contractor cleared it. You have 80 photos in a phone roll and no way to show which one, which floor, or who fixed it. You did the inspection. You have no record you can stand behind.
Facility teams document buildings for the moments that come later: a compliance audit, an insurance claim, a warranty dispute, a capital planning request, a contractor who insists the repair was never in scope. The walk-through is the easy part. A few habits, each costing seconds on-site, separate a record you can defend from a camera roll you cannot.
Structure the Walk-Through by Zone or System
Decide before you start whether you are inspecting by location or by system, and hold the report to that same order. Use a spatial route for condition and life safety walks, where the floor plan is your reference: exterior, lobby, stairwells, each floor in turn, roof, then plant rooms. Use a system grouping for technical inspections: HVAC, electrical, plumbing, fire protection, and building envelope. Mixing the two in one report is the fastest way to lose a finding between the cracks.
A fixed order pays off for the person who was not on the walk. Your recipient scans to the area they own, and you compare this month’s roof section against last month’s without hunting through a stack of photos. Number the zones or systems and reuse that numbering on every visit. A contractor who reads “Zone 4, item 2” knows where to stand without calling you.
What to Capture (and Annotate) On-Site
A photo on its own answers “is there a problem.” It does not answer “where,” “how bad,” or “what now.” Add four things while you are still standing in front of the issue, because rebuilding them at your desk is guesswork.
- Location. Mark where you took the photo on a floor plan, or write the room and orientation. “Northeast corner, third-floor electrical room” beats a photo of an anonymous gray panel.
- The Defect. Draw on the image: Circle the corroded fitting, arrow the hairline crack, outline the water stain. The mark carries to whoever opens the file weeks later, when “top left, you’ll see it” would mean nothing.
- Severity and Owner. Tag each finding monitor, repair, or act-now against a scale your whole team grades the same way, and name who owns the fix. When two inspectors give the same valve different grades, your trend data falls apart. An unassigned finding is one nobody closes.
- A Short Note. Two sentences on what you saw and what you suspect caused it outweigh the cleanest photo with no caption. A voice memo recorded on-site works as well as typed text.
Shoot at full resolution and keep the originals. A compressed thumbnail that looked sharp on the phone often hides the exact crack a warranty claim or a manufacturer’s dispute later turns on.
What a Complete Deliverable Should Include
The report serves the people who were not on-site, so build it for them. A complete building-inspection deliverable carries:
- A header: Building, date, inspector, areas covered, and conditions if weather bears on a finding.
- A distribution list, so no one argues later about who was told what.
- The findings, each with its located, annotated photo, severity, and owner.
- A status line on every open item from the previous visit. Leaving last month’s blocked exit unmentioned turns the file into a liability.
- Sign-off and a distribution date.
Send it within 24 to 48 hours, while the context is fresh and the corrective window is still open. Hold the format steady from visit to visit so the file grows into a usable history of the asset, the kind that supports a capital request or shows an auditor a pattern, rather than a drawer of one-off PDFs.
Decide where the finished record lives before you need it. A report parked in one inspector’s phone or personal inbox disappears the day that person changes jobs, and facility teams turn over. Store it where the maintenance lead, the property manager, and their backup can pull it without asking you, and where last year’s visits sit next to this one. A record earns its keep only when someone other than its author can act on it, today and after you have moved on.
None of this adds time on-site. It changes what you settle before you raise the camera: that every finding carries a location, an annotation, a severity, and an owner. Capture those four on each photo, and you can answer the insurer, brief the contractor, and show the exit was cleared, all from one record you built in the moment.
Patrick Ferreira is the co-founder of PhotoReport, a mobile and web app that facility, inspection, and building teams use to capture annotated site photos and generate field reports. He writes about inspection and field-documentation practice.