Getting an Inspection Business Off Spreadsheets

The spreadsheet is not the problem. The problem is that four spreadsheets have to agree with each other and nobody is responsible for making them.

Most inspection companies do not run on one spreadsheet. They run on a certification tracker, a calibration log, a job schedule and a costing workbook, each owned by a different person, each partially correct, and none of them consulted at the moment a technician is dispatched. Replacing them is less a software project than a sequencing problem — and doing it in the wrong order is why these projects stall.

Migrate in this order, and only this order

Certification register first. It is the highest audit risk, the smallest dataset, and the fastest thing to prove value on.
Calibration register second. Same argument, and it shares the same dispatch control as certification.
Client and asset registers third — the structure everything else attaches to.
Work orders and scheduling fourth, once the two dispatch constraints above are enforceable.
Job costing fifth, because it depends on work orders existing.
Historical inspection reports last, and possibly never in full — see below.

What to do about incomplete history

Every migration surfaces records that cannot be reconstructed: certifications without examination evidence, calibration certificates that were never filed, inspection reports whose CML identity is ambiguous. The instinct is to delay the project until they are fixed. That is the wrong call — the gaps exist whether or not you migrate, and migration is what makes them visible.

The right move is to load what is verifiable, record explicitly what is not, and make a documented decision about each category. A documented baseline decision is defensible in an audit; a silent gap is not.

A pilot that actually proves something

Pick one crew and one client contract, and run six weeks live. The pilot should answer three questions with numbers rather than impressions: did report turnaround time fall, did audit-evidence assembly time fall, and did any compliance gap reach a client gate. Measure the baseline for all three before starting, because nobody remembers accurately afterwards.

Resist the urge to pilot with your easiest client. Pilot with the one whose reporting requirements are most demanding, because that is the case the system has to survive.

The change-management part everyone underestimates

Field technicians will not adopt a tool that is slower than paper. Test the field path with the least enthusiastic technician you have, not the most.
The person who owns the spreadsheet today owns the risk of the migration. Involve them early or the project inherits an internal opponent.
Run the old and new systems in parallel for exactly one cycle — long enough to build trust, short enough that people do not settle into doing both forever.
Turn off the old spreadsheet on a fixed date. Projects that leave it as an optional fallback never finish.

Frequently Asked Questions

How long does the whole migration take?

Six to ten weeks for a typical 20–60 technician inspection business to be live on the core modules, with historical report migration continuing afterwards if it is being done at all. The pacing constraint is almost always historical data reconciliation, not configuration.

Should we migrate historical inspection reports?

Often not in full. Reports from closed contracts that are unlikely to be audited can stay archived in place with an index entry, while reports for assets under an active inspection programme should migrate because their thickness data feeds corrosion-rate calculations. Decide by whether the data is still doing work, not by completeness for its own sake.

What if we are mid-contract on a major client?

That is usually the best time, not the worst — you have a live case to pilot against and a concrete definition of success. What to avoid is migrating during a turnaround or shutdown peak, when nobody has attention to spare and any friction gets blamed on the system.

Can we do this without a full-time internal project owner?

Realistically, no. Someone internal has to make decisions about incomplete records, written-practice interpretation and client reporting formats, and those decisions cannot be outsourced to the vendor. It does not need to be a full-time role, but it needs a named owner with the authority to decide.

See it running on your own workflow

Thirty minutes, your job types and your reporting formats, co-presented by an ASNT NDT Level III. Affordable, accessible, fully customizable — request a demo and a tailored quote.