API 653 Report Template: Building a Repeatable Inspection Deliverable

FieldSight

API 653 Report Template: Building a Repeatable Inspection Deliverable

A good API 653 report template is more than a formatted Word file. It is a fixed structure that tells your inspectors where every piece of field evidence belongs, so each report reads the same way no matter who wrote it. The template only works if the data behind it is organized the same way. Otherwise every job still ends in a copy-and-paste session at the desk.

This article covers how to plan the sections, connect each one to its field source, and keep the template under control as your team grows. It stays at the workflow level. The content a report must include depends on the edition of API 653 you work to, the owner’s inspection program and contract, and your company’s written procedures. Check those documents, not a generic template, for required content.

Start with the reader, not the file

Before you change fonts or logos, write down who reads the report and what each reader does with it. On a typical tank job those readers include:

  • The owner’s integrity or facility contact, who needs to see quickly what needs attention, how urgent it is and what is recommended.
  • The engineer or reviewer, who needs the measurements, calculation inputs and results in a form they can check.
  • The next inspector, who will open this report years from now looking for previous readings, locations and repairs.
  • A repair contractor, who may only get the repair scope, drawings and locations.

A template that serves all four keeps the summary short and clear and keeps the supporting data complete and easy to trace. Most report problems come from mixing those two layers: findings buried in data tables, or conclusions with no visible basis.

Plan the sections and their sources

Treat the template as a map from report sections to field records. For each section, decide where the information comes from and who enters it. The table below is an example structure, not a required list. Change it to match your procedures and the owner’s specification.

Report sectionTypical sourceCommon failure point
Tank and job identificationOwner records, nameplate, job setupTank IDs or dates that differ between cover page and body
Summary of findings and recommendationsInspector’s reviewed findingsSummary not updated after a finding changes
Shell, bottom and roof thickness dataUT and scanning records with locationsReadings re-keyed from field sheets into tables
CalculationsMeasured data plus construction and operating inputsInputs that can’t be traced to a record or a documented assumption
Settlement evaluation, where performedSurvey data and evaluation resultsSurvey points that don’t match the drawing orientation
Drawings and diagramsTank layout, plate and nozzle locations, indicationsDrawing revised separately from the data it shows
PhotographsField photos tied to findingsCaptions that don’t match the finding or location
Sign-offResponsible inspector and reviewerSign-off applied before the final review

The third column is the important one. Almost every failure point comes from the same piece of information existing in two places that can drift apart.

Step-by-step: building a template your team will actually use

  1. Collect your last several issued reports. Mark which sections were consistent across inspectors and which looked different every time. The inconsistent sections are where the template needs the most structure.
  2. Fix the section order and headings. Pick one order and keep it. Clients learn where to look, and reviewers can compare one job to the next.
  3. Separate findings from data. Give every finding the same fields: location, condition observed, recommendation and priority. Keep the measurement tables in their own sections and refer to them from the finding.
  4. Define how locations are described. Agree on reference points, orientation and numbering for plates, courses and nozzles so locations in tables, drawings and photos match.
  5. Write down the calculation basis. Wherever a calculation depends on construction records, operating conditions or an assumption, the template should have a place to state that basis, not just the result.
  6. Set photo rules. Decide how photos are numbered, what a caption must identify and how each photo links to a finding or section.
  7. Control the template itself. Keep one current version, record who changes it and why, and stop old copies from circulating on laptops.
  8. Review before you issue. A template does not replace review. Run each report through a consistent QA pass. Our API 653 report review checklist covers that step.

Why a Word template alone stops working

A shared Word file standardizes how the report looks. It does not standardize where the data comes from. On many teams the real workflow is still field sheets, a spreadsheet for readings, a separate calculation file, CAD for drawings and a folder of photos. Then someone rebuilds all of it inside the template. Each handoff is a chance for the cover page, tables, drawings and findings to disagree.

The data side needs the same discipline as the document side. If your thickness readings are scattered across files, start there. Our guide to organizing tank UT thickness data walks through one approach. If you are comparing software that keeps data and report in one place, see what API 653 teams should evaluate in tank inspection software.

How FieldSight supports a repeatable API 653 report

FieldSight approaches the template problem from the data side. You don’t maintain a separate template and then fill it by hand. The inspection record holds the field data, calculations, diagrams, findings and photos, and the report is generated from that record.

  • Branded output: Inspection Pro produces company-branded PDF and editable Word reports. Branding covers company logos, colors, contact information, report styling and sign-off details.
  • Findings and photos in context: Findings are recorded with their photos and measurements. AI-assisted findings, narratives and photo captions are available, and the final content is subject to the inspector’s review and approval.
  • Diagrams from the same record: Bottom, shell, fixed-roof and floating-roof diagrams, X/Y indication and weld-defect records, and CAD/DXF export come from the inspection data. They are not redrawn separately.
  • Calculations carried forward: Calculation results, including Annex B settlement evaluation and corrosion rates, remaining life and inspection intervals, carry into the report with the rest of the inspection data. The inspector and any responsible engineer still review the inputs and results.
  • Controlled finalization: Inspection records are versioned and finalized under control. Finalized reports can be shared with clients as browser-based reports through a controlled link, with a PDF download still available.

FieldSight does not decide what your report must contain or certify that it meets a standard. Those remain the responsibility of the inspector, the owner’s requirements and your procedures. What it changes is where the report comes from: one inspection record instead of several files rebuilt at the end of the job.

See the workflow on your own report format

If your team keeps rebuilding the same report from separate files, compare that process with a report generated from one inspection record. See how FieldSight builds API 653 inspection reports.