Tank Inspection Software: What API 653 Teams Should Evaluate

FieldSight

Tank Inspection Software: What API 653 Teams Should Evaluate

Good tank inspection software keeps one inspection record from the first field reading to the finished client report, so nobody on your team has to rebuild the job in a spreadsheet, a CAD file and a Word template after leaving the site. When you evaluate options, focus less on feature lists and more on whether the tool carries field data, calculations, diagrams, photos and findings into a deliverable your inspector can review and sign. The most reliable test is a real upcoming API 653 inspection, not a canned demo.

This guide is for owners of inspection companies, inspection department leads and working API 653 inspectors who are comparing tools. It covers where reporting time actually goes, a checklist you can use in any demo, and how to run a fair trial.

What tank inspection software should actually do

API describes the inspector’s work as the supervision or performance of inspection activities as described in API Standard 653, Tank Inspection, Repair, Alteration, and Reconstruction (see the API 653 certification page). Software does not do that work. Its job is narrower and still valuable: to hold the evidence the inspector collects, to keep the calculations tied to that evidence, and to produce a clear deliverable without re-keying.

That means the software should support the inspector’s judgment, not replace it. Be cautious with any product that promises automatic compliance, guaranteed engineering correctness or a report that needs no review. The responsible inspector, the owner’s requirements and, where needed, an engineer’s evaluation still decide what the data means.

Where reporting time really goes

Before you look at any product, map how one recent job moved from the tank to the client. On most API 653 jobs the time disappears in the handoffs:

  • Field notes to digital records. Readings and observations on clipboards, notepads and phones get typed again at the desk.
  • Thickness data to calculations. Shell and bottom readings are copied into a workbook that may have been modified for the last job and never reset.
  • Sketches to drawings. A field sketch becomes a CAD drawing, often by someone who was not at the tank, and revisions come back when the layout does not match.
  • Photos to the appendix. Dozens of images get sorted, captioned and placed by hand.
  • Observations to findings. Shorthand becomes written findings, recommendations and priorities, sometimes in a different document from the data that supports them.
  • Draft to final. Review comments, version confusion and formatting cleanup stretch out delivery.

Write down roughly how many hours each step took on that job and who did it. That gives you a baseline from your own work instead of a vendor’s estimate, and it tells you which part of the workflow matters most in an evaluation.

Evaluation checklist for tank inspection software

Use this list during any demo or trial. Ask the vendor to show each item in the live application with realistic data, not slides.

  1. Single inspection record. Is field data entered once and reused in calculations, diagrams, findings and the report? Ask the vendor to change one reading and show everywhere it updates.
  2. Field capture. Can technicians and the inspector each enter their own data in the same inspection? How are roles and permissions handled?
  3. Shell and bottom thickness data. How are readings organized by course, plate or location? Can you see which reading drove a result?
  4. Calculations with visible inputs. Are the inputs behind each calculation shown and editable? What happens when a required input is missing? A tool that silently fills in a default is a risk to your reputation.
  5. Settlement documentation. If you perform settlement evaluations, how does the software record survey points and present the evaluation? Confirm the method matches the edition and requirements your client specifies.
  6. Tank diagrams. Can the inspector or technician build the layout during the job? Can the drawing be exported for clients who need CAD files?
  7. Indications and repairs. Can bottom indications be located on the plate layout and carried into a repair or defect table?
  8. Photos. Are photos stored with the inspection, linked to the items they document and carried into a report appendix with captions?
  9. Findings and recommendations. Can the inspector edit the issue, recommendation and priority separately? If AI drafting is offered, does every suggestion require inspector review before it is saved?
  10. Report output. Does the report carry your company branding? Which formats are available, such as PDF and Word, and can clients open a shared report without extra software?
  11. Review and QA. How does a reviewer see what is incomplete or unverified before the report is finalized?
  12. Data handling. Where is client data stored, who can access it, and how is lost work recovered? Ask for specifics, not general assurances.

Questions to ask in a demo

A short, focused demonstration tells you more than a long tour. Bring one recent job and ask:

  • Show me the path from one shell reading to the number that appears in the report.
  • Show me what the report looks like when an input is missing.
  • How long would it take my team to set up our report branding?
  • What would my technicians need to learn before their first job in the tool?
  • Which parts of my current report would still need to be produced outside the software?

That last question matters. No tool covers every client format or every special request. Knowing the gaps up front is better than finding them on a deadline.

How to run a fair trial on a real inspection

Sample data always looks clean. A real job shows you the edge cases: the missing nameplate, the plate that does not fit the template, the late photo set. Use these steps:

  1. Pick one upcoming inspection with a known scope and schedule.
  2. Designate one person to run it in the new tool from start to finish, so the result is not split across people and systems.
  3. Record your baseline using the hours from your mapping exercise above.
  4. Get permission before uploading client data to any system, including any AI features, and follow your client agreements.
  5. Track actual hours for field entry, calculations, drawings, photos, findings and review on the trial job.
  6. Review the finished report the way your client would. Check every value against the field evidence.
  7. Compare honestly. Count setup and learning time. A first job is usually slower than the tenth.

If you want to estimate value, use your own labor cost rates, not billable rates, and count each hour only once. Time released from salaried staff is capacity for more work, which only becomes revenue if you have the jobs and people to fill it.

How FieldSight supports this workflow

FieldSight is API 653 inspection and reporting software built around a single inspection record. In the application, technicians and inspectors can work in the same inspection, and that record carries field data into calculations, Annex B settlement evaluation, interactive tank diagrams, CAD/DXF output, findings, photographs and branded PDF and Word reports. Finalized reports can also be shared with clients as a link.

A few specifics relevant to the checklist above:

  • Inputs stay visible. In the shell calculations, the safe-fill versus specific-gravity chart marks the operating point, and it shows an indeterminate message when required inputs are missing instead of drawing a result.
  • Bottom indications. Indications can be located on the plate layout and carried into defect and repair tables in the report.
  • Findings stay with the inspector. The issue, recommendation and priority are edited separately. Optional AI assistance suggests wording for findings and photo captions, and the inspector reviews and approves each suggestion before it is saved.
  • Roles. Team plans support role-based access for collaborating inspectors and technicians.

FieldSight does not certify engineering correctness or guarantee compliance. The inspector reviews the calculations, the findings and the final report. The best way to judge fit is to see the workflow on a job like yours.

Next step

If your team is comparing tank inspection software, see the FieldSight API 653 workflow and request a walkthrough at fieldsightsolutions.com.