Compliance Tracking That Answers One Question Before Dispatch

The dispatch gate: one question asked before the crew leaves

Every compliance requirement an inspection company carries collapses into a single operational moment: a scheduler puts a name against a job. At that instant the firm either can or cannot defend the assignment, and nothing that happens later changes the answer. Compliance tracking software earns its place by making that moment fail loudly instead of quietly. The gate checks four things simultaneously — the technician holds a current certification in the method the job calls for, at the level it requires; the vision examination underneath that certification is current; the written practice the certification rests on covers this scope of work; and the instrument leaving the cage is inside its calibration interval.

Firms that run this check by hand run it once, at hire, and then trust the calendar. The gap opens quietly. A UT Level II certified in 2023 against a five-year recertification horizon looks safe for years, while the annual vision examination beneath that certification lapses in month thirteen. ASNT's SNT-TC-1A puts near-vision acuity on an annual cycle, and ISO 9712 makes the employer responsible for verifying visual acuity at least annually. A certification is only as valid as the shortest-cycle record beneath it, and that record is never the one framed on the wall.

The practical test for anything sold as compliance tracking is whether it can refuse. If the schedule still accepts a lapsed technician and merely turns a row amber, what you bought is a dashboard. The NDT ERP we build treats currency as a hard precondition on the assignment record, with a documented override that captures who authorised the exception and on what basis. An override that leaves no trace is functionally the same as no gate at all, and auditors know exactly where to look for it.

Certification currency is per method and per level, never per person

There is no such thing as a certified technician. There is a technician certified in UT Level II, MT Level II and PT Level I, each with its own training hours, its own documented experience hours, its own examination record and its own expiry date. A firm with forty technicians and six methods is tracking well over a hundred independent currency states, not forty. Spreadsheets model this badly because a spreadsheet row is a person, while the underlying reality is a matrix — and the matrix is what dispatch has to query.

The consequence shows up on multi-method jobs. A tank crew running MT on nozzle welds and PT on the shell needs both certifications live in the same body on the same day. A weld inspection scope that shifts from radiography to ultrasonics mid-turnaround, a substitution we set out in our comparison of RT and UT for weld inspection, silently changes which certification the assignment requires. If the system does not re-run the gate when the scope changes, it was only ever checking the job as originally sold.

Tracking that matrix is the job of a dedicated data model, which is why we keep NDT personnel certification tracking as its own record type rather than a set of date columns on an employee card. Each certification carries the method, the level, an effective date, an expiry, the examination results behind it, the written practice revision it was issued under, and the Level III who signed it. That structure is what lets the system answer a question about a job from fourteen months ago instead of only about today.

Vision dates are the most-missed record in the whole file

Near-vision acuity is the requirement firms forget because it belongs to nobody. It is not an HR record, not a training record and not a certification in its own right. It is a condition attached to certifications that already exist. SNT-TC-1A describes near-distance acuity sufficient to read a minimum of Jaeger Number 2 at not less than 12 inches on a standard Jaeger chart, administered annually. ISO 9712 sets a comparable bar of Jaeger Number 1 or Times Roman N4.5 at not less than 30 cm, and places responsibility on the employer to verify visual acuity at least annually.

Colour contrast differentiation runs on a different clock. Under SNT-TC-1A the examination demonstrates the capability of distinguishing and differentiating contrast among the colours or shades of grey used in the method, at initial certification and at five-year intervals thereafter. That distinction matters most in penetrant and magnetic particle work, where the acceptance decision rests entirely on the examiner seeing an indication against a developer background. Two records, two intervals, one certification — and a tracking system that treats them as a single field reports currency it cannot support.

Practically, the vision record needs its own expiry, its own reminder chain and its own blocking behaviour. When the near-vision date lapses, every certification depending on it should go non-current at that instant, not at its own printed expiry. Firms implementing this for the first time are consistently surprised by how many technicians go amber overnight. That surprise is the point. The amber was always there, sitting in a folder, waiting for an auditor to find it before you did.

The written practice is the thing everything else is tracked against

SNT-TC-1A is a recommended practice, not a standard. The binding document is the employer's own written practice, which SNT-TC-1A requires the employer to establish for the control and administration of NDT personnel training, examination and certification, to have reviewed and approved by the employer's NDT Level III, and to maintain on file. Employers may modify the recommended provisions but shall not eliminate the basic ones: training, experience, testing and recertification. Your compliance is measured against your document, not against ASNT's.

That is why software shipping with a generic certification calendar misses the target. Your written practice may set shorter recertification intervals than the five-year maximum SNT-TC-1A now recommends, may add method-specific examination requirements, and may restrict named technicians to defined techniques or product forms. ASME BPVC Section V, Article 1 requires NDE personnel to be qualified and certified in accordance with the employer's written practice, which makes that practice the operative rulebook on every code job you run for a fabrication, refinery or power client.

Revision control on the practice itself is the piece firms skip. When the practice is revised, existing certifications were issued under the prior revision, and an auditor tracing a two-year-old job needs the revision that was in force then. Store the practice as a versioned, effective-dated document and bind each certification to the version it was issued under. Doing that once removes an entire category of audit finding, and it is the single change we recommend most often during an NDT programme audit and gap assessment.

Calibration status is a personnel problem wearing a different hat

The dispatch gate has a fourth input most certification tools ignore: the instrument. A current Level II carrying a flaw detector three weeks past its calibration date produces a report with exactly the same defect as one signed by a lapsed technician. ISO 9001:2015 requires the organisation to determine whether the validity of previous measurement results has been adversely affected when measuring equipment is found unfit for its intended purpose, and to take appropriate action. That clause is the reason instrument status belongs inside the assignment check rather than beside it.

The same clause creates a reverse-traceability obligation nobody enjoys discovering late. When an instrument returns from the calibration house out of tolerance, the question is not whether to recalibrate it. The question is which examinations performed since the last good calibration are now in doubt. Answering that requires knowing which serial number was used on which job, by which technician, on which date. Firms without that link end up quarantining months of work because they cannot narrow the exposure to the jobs actually affected.

Linking instruments to jobs is straightforward once the equipment register is a first-class record rather than a tab in a workbook. Our NDT equipment calibration tracking holds calibration certificates against serial numbers with effective and expiry dates, and the job record stores which serial numbers were issued to which crew. The out-of-tolerance query then returns affected jobs in seconds instead of a month of forensic reading, and the same link feeds the dispatch gate. One data structure, two problems solved.

Why spreadsheets fail at exactly the wrong moment

A spreadsheet stores current state and overwrites history. When a certification is renewed, the old expiry is typed over. When a vision date is updated, the previous one is gone. Every audit question is a historical question, so the tool holding your compliance data destroys precisely the information an auditor asks for. This is not a discipline problem that better habits fix. It is a property of the format, and it is present in every workbook regardless of how carefully it is maintained.

The second failure is ownership. The certification workbook lives with the Level III, the calibration log with the equipment coordinator, the schedule with operations. None of the three is notified when another changes, and reconciliation happens in a meeting nobody wants to hold. Copies proliferate — one on a laptop, one in an email thread, one on the shared drive, one printed for a client — and by the time an auditor asks which is authoritative, the honest answer is that nobody in the room knows.

Replacing spreadsheets is not really about features. It is about moving from a snapshot to an append-only history where every change writes a new row, preserves the old one, and records who made it and when. Once records are effective-dated, the historical question becomes trivial: show the state of this technician's file on 14 March last year. That single capability converts audit preparation from reconstruction into retrieval, which is the whole argument for putting compliance inside the operating system rather than alongside it.

What the gate looks like inside a real schedule

A working compliance gate has three tiers, not one. At sixty days out, the Level III sees a renewal queue and can book examinations without disrupting live work. At thirty days, the scheduler sees a warning against any assignment that would run past the expiry, because a two-week turnaround starting before a certification lapses ends after it. At zero, the assignment is refused outright. Firms implementing only the third tier discover that a hard block with no runway simply becomes an override habit within a month.

Subcontracted and agency technicians break most implementations. They are not on payroll, so they are not in the HR system, so they are not in the gate. Yet they sign reports carrying your company's name and your client's acceptance. The gate must treat a subcontractor's certification exactly like an employee's, including the vision record and the written practice their certification was issued under, which is frequently a different practice belonging to a different employer. That last point catches firms out repeatedly at third-party audit.

Client-specific approvals form the final layer: site orientation, safety training, badge validity, fitness-for-duty currency. These have nothing to do with NDT competence and everything to do with whether the crew gets through the gate at seven in the morning. Modelling them as another currency record on the same technician is cheap to build and eliminates the most expensive failure mode in field work, which is a mobilised crew turned away and a full day billed to you as standby.

What compliance tracking software will not do for you

Software does not make the judgement calls. Whether a technician's documented experience hours support certification in a new method, whether a limited certification is appropriate, whether the written practice needs revision after a code edition change — these are Level III decisions, and no workflow engine substitutes for them. What software does is remove the clerical failure modes surrounding those decisions, so the Level III spends their time on the decisions themselves rather than on reconciling three spreadsheets that disagree with each other.

It also cannot repair a programme that is structurally non-compliant. If the written practice does not match the codes your clients invoke, a tracking system will faithfully enforce the wrong rules and produce a clean dashboard sitting on top of a finding. That is why the first engagement is usually an NDT programme audit and gap assessment rather than an implementation. You establish what the rules actually are before you automate them, and the assessment output becomes the configuration specification.

Finally, no system fixes data that was wrong at the source. Certifications entered from memory, vision dates estimated, calibration certificates filed without being read — all of these survive a migration intact. Budget the data load as a verification exercise, not a transfer. Atlantis builds this on Odoo 18 for NDT companies: affordable, accessible and fully customisable to your written practice rather than to a generic template. Ask for a demo or a quote and we will run your written practice against the model first.

Request a consultation