Organising Marine Survey Photos: A System That Survives a Full Season
A practical photo workflow for marine surveyors — naming, linking to findings, backup, and retrieval — that holds up after a hundred surveys, not just one.
Ask any working surveyor where their reports leak time, and photos come up first. Not the taking of them — the wrangling. A typical pre-purchase survey produces 150–300 images. Multiply that by a season of work and you have a folder structure that nobody, including you, can navigate three months later.
Here's a photo workflow that survives the volume.
The problem with folders
The default approach is a folder per survey, photos dumped in, filenames left as `IMG_4821.jpg`. It works for the report you're writing this week. It collapses the moment a client emails six months later asking for "the photo of the corroded keel bolt on the Bavaria 36."
You don't have a search problem. You have a structure problem.
Capture photos against observations, not into folders
The shift that changes everything: photos belong to findings, not surveys. When you spot the corroded chainplate, the photo is captured as part of that observation — not into a generic camera roll that you'll sort later. The photo carries the finding's context with it from the moment of capture.
This is the single biggest workflow change you can make. It eliminates the entire "match photos to findings at the desk" step, which is where most of the leakage happens.
Caption at capture, not at the desk
A three-word caption written on the boat — "port chainplate, deck level" — is worth ten minutes of squinting at thumbnails later. You already know what you're looking at. Your future self, two weeks later, will not.
If your tools don't support captioning at capture, voice memos on the same phone work as a fallback. Anything to attach context to the image before the moment passes.
Standardise what every survey gets
Every survey should produce the same baseline photo set, regardless of findings:
- Vessel overview (bow, stern, both beams, transom)
- HIN/CIN plate
- Engine plate and hour meter
- Helm station with instruments powered on
- Each through-hull and seacock
- Bilge (dry condition)
- Battery bank and main switch panel
- Safety equipment locker
Build this into your template as a required capture list. It catches the gaps before you leave the boat — not at 9pm when you're writing up.
Backup that actually runs
A surveyor's photo archive is professional indemnity evidence. It needs to exist in two places, automatically, without you remembering to copy files. Phone-to-cloud sync covers the field side. Your survey tool should handle the long-term archive. If both rely on you manually moving files, one of them will fail at exactly the wrong moment.
Test the restore, not just the backup. Pick a survey from four months ago and try to retrieve its photos. If it takes more than thirty seconds, the system is broken even if the files are technically there.
Retrieval is the real test
A good photo system is judged by retrieval speed, not capture speed. The questions to design for:
- A client wants the photo of finding 4.2 from a survey last March.
- An insurer wants every photo of the engine bay from a specific survey.
- You want to find every example of osmosis you've photographed in the last year, across
all surveys, for a training session.
If your current setup can't answer those in under a minute, the structure is doing you no favours. Tools built around the surveyor workflow — evalo is one — store photos against observations and vessels by default, so retrieval is a filter, not an archaeology project.
The compounding effect
Photo workflow improvements compound. The hour saved per report turns into a day per month turns into a fortnight per year. More importantly, the photos you take become an asset you can search, reuse for marketing, and produce instantly when a claim or dispute arrives — instead of a 40GB folder you avoid opening.