A surveyor can leave a property with 120 photos and still not have usable evidence. The problem was never how many photos got taken. It’s that nothing in the file says which photo answers which question.
Why does a full memory card feel like a finished job?
On site, photography feels complete because it’s connected to something. You see the crack, you photograph the crack, you already know what it means. The camera is just recording a thought you’re having in real time. By the time you leave, you’ve got 80, 120, sometimes 300 images, and it feels like the property has been thoroughly documented.
That feeling doesn’t survive the trip back to the office. The property isn’t in front of you anymore. The photos are just files now, and the thinking that gave each one meaning stayed on site.
The photo remembers what. It doesn’t remember why.
A photo captures a defect. It doesn’t capture the reason you took it, what you were ruling in or out, or how it connects to the note you made two rooms earlier. That gap is the same one covered in why a photo isn’t evidence in a survey report: the image is data, not judgement.
Building surveyor Andrew Leonard put the shift in perspective well: before digital cameras, a surveyor loaded a roll of 24 or 36 exposures and had to decide, in the moment, whether a shot was worth taking. You either remembered what you’d photographed or you made a note, because the film wouldn’t come back for days.
Digital removed that constraint. It didn’t replace it with anything. Surveyors now shoot without limit, which is usually the right call for coverage, but nothing forces the context to travel with the image the way it used to when memory was the only backup.
It’s a pattern that comes up constantly talking to surveyors while building Sitarva: nobody is short on photos. Everyone is short on a reliable way to know what each one was for once they’re back at a laptop three hours later.
More photos isn’t the fix
The instinct when something feels ambiguous is to capture more: more angles, more close-ups, more notes. It doesn’t help, because volume was never the constraint. A folder of 300 unlabelled images is a bigger version of the same problem, not a solved one. Every additional photo without context is more material to reconstruct later, not less.
This is where report writing turns into detective work rather than review. The surveyor isn’t checking their findings, they’re rebuilding them from partial memory, and that rebuilding happens hours or days after the observation was actually made.
Why this shows up later, not on the day
The real cost surfaces when the report gets questioned, not when it’s written. A client disputes a conclusion. A contractor argues a defect wasn’t there. A claim goes to a second surveyor who has to work out what the first one meant from a photo with no context attached. At that point the question changes from “what did you find” to “what evidence supports it, and can you show your reasoning,” which is the standard laid out in our guide to a building survey audit trail.
If the answer relies on memory, it’s already weaker than it should be. That’s not a writing problem. It’s a defensibility problem, and it starts at the point of capture, not the point of drafting.
Keeping the context attached from the start
The fix isn’t fewer photos or more discipline on site. It’s not losing the connection between the photo and the reasoning behind it in the first place, so nothing has to be reconstructed once the surveyor is back at a desk. That’s also where most of the desk-based rework comes from in the first place, something I’ve broken down in where survey report time actually goes.
Sitarva is built around keeping that link intact: photos, observations, and the surveyor’s own reasoning stay connected from the moment they’re captured through to the finished report. The surveyor still makes every judgement call. Sitarva just makes sure the evidence behind that call doesn’t go missing between the site visit and the write-up.