Six months after a bridge inspection, IMG_4821.jpg tells a colleague almost nothing. A folder named 2025-04-18_RiverBridge_Pier3 gives the photograph context before it is opened. For field photos, a workable system need not be elaborate: keep the originals, group images by visit or task, record where they were taken, and keep annotated versions separate.
The aim is not to describe every image in its filename. It is to maintain a path back to the asset, date, inspection location and field record. That matters when comparing a crack with a later photograph or using a construction-stage image to identify work subsequently concealed. A photograph can support an observation; on its own, it is neither a complete inspection record nor proof of a defect’s cause.
Start with one home for the photo archive
Choose a primary archive location the team can maintain under its usual information-management procedures. Photos scattered across personal phones, email attachments, desktops and messaging threads are hard to find and easy to lose. On a shared project, establish who uploads files, who may change them and which archive is authoritative. A synchronised folder may be convenient, but it is not a backup: deletions and unwanted edits can spread to connected devices.
Keep the top-level structure short: project or asset → visit or task → originals and working files. Use the asset identifier found on inspection forms and other records. Where a project covers several structures, name the structure or location rather than putting every image in one large folder.
- Asset or project: a stable identifier, such as RB-014_RiverBridge.
- Visit or task: a date and short purpose, such as 2025-04-18_RoutineInspection.
- Originals: files copied from the camera or phone without edits.
- Working: selected photographs, crops, annotations and report images.
Dates in YYYY-MM-DD format sort chronologically. Resist creating folders for every pier, elevation and defect unless the volume warrants it. A visit folder and a photo register are often easier to maintain, particularly when one image shows several elements.
Make intake a repeatable step
A good folder structure cannot recover context lost while photos sit on a device. Transfer them after each field visit. Before sorting, compare the camera clock and visit date with the field notes; an incorrect device time can distort the sequence, especially when several cameras were used.
- Copy files into an intake folder. Keep their original filenames for now, and do not immediately delete them from the device.
- Check the transfer. Compare file counts and, where feasible, total size. Open a selection from each device to check that the files are readable. If the records require a documented chain of custody, follow the project’s prescribed transfer and verification procedure instead of this informal check.
- File them by visit. Separate originals from exports and annotated versions. If several people photographed the visit, keep each person’s files together until naming conflicts are resolved.
- Record context while it is fresh. Enter the location, direction of view, element and observation reference in a register or the approved asset-management system.
- Verify backup before clearing devices. An upload does not establish that a second, recoverable copy exists.
Two devices may produce the same filename. Never let one image overwrite another: either add a camera or photographer identifier during a controlled rename, or retain the originals in clearly named device subfolders. Use the chosen approach consistently.
Use filenames for identification, not full descriptions
Renaming every photo by hand takes time and creates opportunities for transcription errors. A filename only needs enough information to identify an image outside its folder. For example, RB-014_2025-04-18_P3_0042.jpg gives the asset, visit date, location code and sequence number. Document what P3 means rather than relying on an inspector’s memory. If the camera filename matters to the evidence trail, retain it in the register after renaming.
Keep conclusions out of filenames. “Severe-foundation-failure.jpg” says more than the photograph may establish; a neutral location-based name remains valid if the assessment changes. Condition measurements also belong in an inspection record, where their method, units and date can be recorded.
For large sets, batch renaming helps, but test the pattern on copies first. Check that sequence numbers are unique, extensions remain intact and the order agrees with the register. Padding a sequence number—0042 rather than 42—keeps it in order beside 0043 and 0100.
Keep a small photo register
Folders and filenames help people find an image; a register connects it to the field record. For a small project, a spreadsheet stored with the visit records may suffice if access is properly controlled. For a larger programme, use the organisation’s approved inspection or asset-management system. Point the register to the original, not just a resized image in a report.
| Field | Example | Purpose |
|---|---|---|
| File ID | RB-014_2025-04-18_P3_0042.jpg | Finds the exact image |
| Location | Pier 3, upstream face | Identifies the element and side |
| View | Looking downstream | Helps interpret orientation |
| Record reference | Observation O-17 | Connects the image to field notes |
| Photographer | Inspector initials or staff ID | Clarifies provenance |
Not every image needs a long description. Adjacent views may share a location and observation reference, provided another competent person can distinguish the overview from the close-up and connect both to the field notes. If the drawings and forms use chainage, grid references or component numbers, follow the same convention.
Preserve originals and label derivatives
Keep the file received from the capture device as the original, without cropping, markup or recompression. Even if a report uses a clearer crop, the full frame may contain orientation, scale cues or nearby features that the crop leaves out.
Store edited versions in the working folder, with names that lead back to the source—for example, RB-014_2025-04-18_P3_0042_annotated.jpg. Record brightening, stitching, sharpening or other processing that could affect interpretation. Never overwrite the original. Identify report figures well enough for a reviewer to locate the source photograph and observation record. The same traceability matters when writing transport infrastructure case studies that hold up to scrutiny.
Embedded metadata needs checking, too. Timestamps and coordinates may be absent, wrong or stripped during export; a phone’s coordinates may describe the photographer’s position rather than the element photographed. Use metadata as supporting context, not a replacement for a location note. Before sharing images outside the project team, check organisational requirements for metadata, faces, vehicle registration numbers and restricted infrastructure details.
Build retrieval around the questions people actually ask
The test of an archive is whether someone can find an image without opening hundreds of files. They may need the upstream face of Pier 3 in April, a joint before repair, or the photograph behind observation O-17. Asset identifier, visit date, element, orientation and record reference should cover most such requests. Add other tags only when the team will apply them consistently.
Across repeat inspections, keep element names stable even as visit folder names change. For a reference view, note where the photographer stood and the direction of view. Two images with the same element label are not necessarily comparable: distance, lighting, water level and camera angle can differ. Put a scale in the frame when appropriate and permitted by the inspection procedure, and record measurements separately rather than estimating them from an uncalibrated image.
Try a retrieval exercise with a colleague who did not attend the visit. Can they find the original behind a report figure and an earlier view of the same element? If not, fix the identifier or register field that held them up before adding more folders.
Back up the archive and retire temporary copies carefully
Keep recoverable copies in locations that do not share one point of failure. Storage and retention depend on contractual duties, organisational policy, security requirements and the images’ role in the project record. Check those requirements before deleting files, particularly ones linked to incidents, claims or ongoing investigations.
Test restoration periodically rather than relying on a backup dashboard. Restore a sample visit folder, open several photographs and check that the register still points to the correct files. Before clearing an intake folder, compare it with the authoritative archive. For a recent visit, start with one image cited in the inspection notes: follow its archive path and confirm that the original is readable and unedited.
