Tank Inspection Photo Documentation: From Field Photo to Finding
Good tank inspection photo documentation means every photo in the report clearly shows a specific condition, where it is on the tank and which finding it supports. When a photo cannot be tied to a location and a finding, it adds pages without helping the client make a decision. The practical answer is to plan photos around findings in the field, record location and context at capture, and review the photo set against the findings list before the report is issued.
This article covers a field-to-report workflow for API 653 inspection teams. It deals with organizing work, not engineering requirements. What must be photographed, how many photos are required and how they are presented can depend on the applicable standard, the owner’s inspection program and the client’s report requirements. Confirm those for each job.
Why inspection photos become a reporting problem
Most crews take plenty of photos. The trouble starts at the desk. Images sit on several phones, a camera card or a shared folder, with file names that mean nothing a week later. Whoever writes the report has to remember which photo shows which plate, nozzle or shell course, and why it was taken.
That causes predictable report problems:
- Photos that do not match any finding, or findings with no photo supporting them.
- Captions that only name the component, such as “shell nozzle”, without saying what condition is shown.
- Location references in captions that disagree with the tank diagram or the data tables.
- Duplicate or near-duplicate images that make the photo section longer and harder to read.
- Hours spent captioning, ordering and placing images after the field work is done.
None of these problems is technical, but each one hurts how the report reads to the owner. A reviewer who cannot match a photo to a finding has to stop and ask. The inspector then reconstructs the context from memory.
Plan the photo set around findings, not around the walkdown
A useful habit is to treat each photo as evidence for something specific. Before the inspection, agree with the crew on the kinds of photos the report will need. Typical groups are general views that identify the tank and its surroundings, component overviews, close-ups of each recorded condition and photos showing the areas tied to recommendations.
In the field, a close-up usually only makes sense next to an overview that shows where it was taken. A pair of photos, one wide and one close, often tells the reader more than several close-ups taken from the same spot.
What to record when the photo is taken
- Component: shell, bottom, roof, appurtenance or foundation, using the same names as the report sections.
- Location: the reference your diagrams and tables already use, such as course, plate number, orientation or X/Y position.
- Condition: a short field note on what the photo shows, in your own words.
- Link: the inspection item or finding the photo supports, if one exists yet.
If these four items are recorded when the photo is taken, the caption and the finding can be written later without guessing.
Write captions that a reviewer can check
A caption should let someone who was not on site understand what the image shows and where. A practical pattern is component, location, condition and, where relevant, a reference to the related finding. Keep the wording consistent with the findings section and the tank diagram, so the same plate or nozzle is never described two different ways in one report.
Avoid putting conclusions in a caption that the findings section does not support. If a photo shows an area that still needs evaluation, the caption should describe what is visible. The evaluation belongs with the inspector’s finding and recommendation.
Connect photos to findings and recommendations
The client mainly wants to know what needs attention, how urgent it is and what is recommended. Photos are most useful when they sit right next to that information. For each finding, check that:
- The issue is described in plain terms with its location.
- The recommendation is stated separately from the description of the condition.
- The priority, where your reports use one, is assigned and consistent with the recommendation.
- At least one photo supports the finding, if a photo is appropriate for that condition.
- The photo caption uses the same location reference as the finding and the diagram.
Working through findings this way also shows gaps while the crew can still fix them. A finding with no supporting photo is far easier to resolve before demobilization than after.
Pre-issue checklist for the photo section
Before the report goes out, run the photo section through a quick review. It fits into the broader steps in our API 653 report review checklist.
- Every included photo has a caption that names the component, location and condition shown.
- Every finding that calls for visual support has at least one linked photo.
- Location references in captions match the tank diagram, data tables and findings text.
- Duplicate, blurry or irrelevant images are excluded rather than buried in an appendix.
- No photos include people, vehicles, documents or site details the client has not agreed to show.
- Photo order follows the report structure, so readers do not jump between components.
- Any caption or finding wording drafted with assistance has been read and accepted by the responsible inspector.
If your company uses a standard report structure, define where photos and the photo appendix sit in that structure once. Then each job follows the same pattern. Our article on building a repeatable API 653 report template covers that side of the deliverable.
How FieldSight supports photo and findings documentation
FieldSight keeps photos and findings in the inspection record they document. They aren’t stored in a separate folder and pieced together at the end of the job. In FieldSight Pro:
- Photos stay with the inspection and can be linked to inspection items, so the context recorded in the field travels with the image.
- Inspectors can request AI-assisted caption suggestions. A suggestion is a draft for the inspector to edit and accept, not final wording.
- Findings carry the issue, recommendation, priority and a concise report action item. The inspector can review and edit each one separately.
- AI-assisted findings and narrative drafts support the inspector, and final content stays subject to the inspector’s review and approval.
- Included photos and their captions carry into the report’s photo appendix, alongside the calculations, diagrams and findings from the same record.
- Reports are produced as company-branded PDF and editable Word files, and a finalized report can be shared with clients through a controlled browser link.
The software organizes the record and drafts wording. It does not decide what a condition means. Technical judgment, the final wording and the decision to issue the report stay with the inspector.
Start with your next inspection
Take one upcoming tank inspection and compare how the photos, captions and findings come together in your current process with a workflow where they are kept in one record from the start. To see how FieldSight handles photo documentation, findings and report output, visit FieldSight.