API 653 Report Review: A QA Checklist Before You Issue
An API 653 report review is the last check before a tank owner relies on your findings. A good review traces every reported value back to field evidence, confirms the calculation inputs, and makes sure each finding has a clear recommendation and priority. The checklist below is a practical way to do that review consistently, whoever performed the fieldwork.
What the report must contain depends on the edition of the standard in force, the owner’s own procedures and the scope of the inspection. This article covers the workflow of a review, not the code requirements. The certified inspector and, where required, the responsible engineer still decide what is acceptable.
Why reports slip through review with problems
Most report errors aren’t engineering mistakes. They’re transfer mistakes. A reading gets typed into a spreadsheet, copied into a calculation, re-entered in a table and described again in a narrative. Each copy is another chance for a reading to land on the wrong course, a nozzle to be mislabeled, or a photo caption to describe the wrong plate.
Reviewers also run short on time. When the review happens days after the fieldwork, often by someone who wasn’t at the tank, it’s tempting to check formatting and spelling and trust the numbers. A structured review puts the effort where errors actually happen: the links between evidence, inputs, results and conclusions.
API 653 report review checklist
Work through these in order. Each step depends on the one before it.
1. Identity and scope
- Tank identifier, location, owner and inspection date match the work order and the field records.
- The inspection type and scope are stated, along with any areas that couldn’t be inspected and the reason.
- The inspector of record and any technicians are named the way the owner expects.
2. Construction and service basis
- Diameter, height, product, specific gravity, fill height and operating temperature all come from a stated source: nameplate, drawings, owner data or field measurement.
- Shell material and joint information are documented. Where records are missing, the report says how the basis was established and who decided it.
- Any assumed value is labeled as an assumption, not presented as a recorded fact.
3. Thickness data traceability
- Pick several readings at random and trace each from the field record to its location on the diagram, then to the calculation input and the reported result.
- Check that the governing readings are the ones used, and that readings below the recordable threshold appear where the report says they do.
- Confirm that previous-inspection data used for corrosion rates comes from the correct earlier report and locations.
4. Calculations
- Each calculation shows its inputs, or makes them easy to find.
- No result is shown for a calculation whose required inputs are missing. An incomplete input should produce a visible gap, not a quiet default.
- Results that drive decisions, such as fill height, remaining life or the next inspection timing, match the values carried into the summary.
5. Settlement and bottom data
- Survey points, reference locations and the evaluation method are documented together.
- Bottom indications are located on the plate layout, and the repair table matches the drawing.
- Proposed patch plates or repairs on the diagram match the written repair scope.
6. Findings and recommendations
- Every finding states the condition observed, the recommendation and a priority, and each is clear enough to read on its own.
- Recommendations are specific enough for the owner to act on or hand to a contractor.
- The executive summary or action-item list matches the detailed findings. Nothing is added, dropped or reworded so that its meaning changes.
- Any AI-assisted wording has been read and approved by the inspector, not accepted unread.
7. Photographs
- Each photo in the appendix supports a finding or documents a condition, and its caption names the correct component and location.
- The photos referenced in findings actually appear in the report.
- Client-confidential or unrelated images are removed.
8. Drawings and deliverables
- The tank diagram, plate layout and any CAD/DXF output are the current revision, not an earlier sketch.
- Branding, headers, revision status and signatures follow the company and owner format.
- The PDF, Word file and any shared link all show the same finalized content.
Who should review, and when
The review is most useful when it happens close to the fieldwork, while missing information can still be collected with a phone call instead of a return trip. Many teams split it: a technician or junior inspector confirms data entry and photo placement, and the inspector of record reviews the basis, calculations, findings and recommendations. The API 653 inspector certification covers the individual’s qualification. Your company procedure should state who signs off on what.
Keep a short review log: what was checked, what changed and who approved it. When an owner asks how a number was derived, that log and a traceable record are your answer.
How FieldSight supports report review
FieldSight keeps the API 653 inspection in one record: field data, shell and bottom thickness readings, calculations, Annex B settlement evaluation, interactive tank diagrams, findings, photographs and the final report. Because the report builds from that record, a reviewer traces values through one workspace instead of comparing separate spreadsheets, drawings and Word files.
- Visible inputs: calculation inputs stay attached to the inspection. Where required inputs are missing, the safe-fill versus specific-gravity chart shows a message saying it can’t produce a result instead of drawing one, so the gap is visible during review.
- Structured findings: the issue, recommendation, priority and report action item are edited as separate fields, so the summary and detailed findings come from the same entries.
- Photos with the record: photos stay linked to the inspection items they document, and the included photos and captions carry into the photographic appendix.
- Inspector-reviewed AI drafting: optional AI suggestions for write-ups and captions are reviewed, edited and approved by the inspector before they’re saved.
- Consistent deliverables: branded PDF and Word reports, CAD/DXF output and client report sharing come from the same finalized record.
FieldSight doesn’t certify engineering correctness or guarantee compliance. The inspector’s review and judgment still decide what goes out. If you’re comparing tools for this workflow, see what API 653 teams should evaluate in tank inspection software.
Put your review process to the test
Take your last issued report and run the checklist against it. Count how many values you could trace back to field evidence without opening another file. If that took longer than it should, see how FieldSight keeps the inspection record and the report together.