The exact column specification for tracking NDT inspector certifications

The eleven columns, specified

Start with identity. Inspector name plus a unique employee ID, because names repeat, change and get typed three different ways across a year of edits. Every downstream join — to the schedule, to payroll, to the training record — runs on the ID. Then method and level as two separate controlled-list columns, never a free-text "UT2" blob. Separating them lets you filter every Level II in a method when a job requires it, and lets the flag logic answer the only question dispatch cares about: who is currently qualified to perform and interpret this method today.

Next, provenance. Issuing body and scheme as a controlled list — employer written practice, an ASNT scheme, an ISO 9712 certification body, API ICP, AWS — because renewal rules belong to the scheme, not to the person. Certificate number exactly as printed is the only field a client can independently verify. Issue date and expiration date as real ISO dates. A single expiry stored as text silently removes that row from every calculation on the sheet, and nothing on screen tells you it happened.

Close with the operating columns. CEU or continuing-education status as earned-versus-required plus an as-of date. Next action date, which is not the expiry — it is the date work must begin, set by the scheme's own lead time. An owner name, because a deadline without a person attached is a wish. And the computed flag, which is derived, never typed. Anything typed by hand drifts within a quarter.

The 90/60/30 flag logic, written out

The flag is one subtraction: days remaining equals expiration date minus today. Everything else is banding. Above 90 days, clear — no action, no noise. At 90 days the row turns amber and a renewal task opens against a named owner. At 60 days it turns orange, which means the application, the CEU evidence and the experience log must already be submitted to the issuing body. At 30 days it turns red and the scheduler is told. At zero and below, expired: assignment to that method stops.

Two refinements make the logic survive contact with reality. First, make the amber threshold a per-scheme value rather than a global 90. A scheme requiring a practical re-examination needs a longer runway than one renewed on an activity attestation, and hard-coding 90 across all of them guarantees that the slowest scheme is started too late every time. Second, add a separate flag for vision examinations, which run on their own annual cycle under SNT-TC-1A-based written practices and expire independently of the certification itself.

The failure mode worth designing against is not the red cell — it is the row nobody looks at. Conditional formatting only works when a person opens the file. Push the flag out instead: a scheduled query that emails every amber, orange and red row to its owner each Monday, with the count of days remaining in the subject line. That is the minimum viable version of what certification tracking software does continuously.

The evidence columns an auditor opens first

The eleven columns run your process. Four more columns decide whether you pass a personnel-records audit. A link or file path to the scanned certificate, so verification takes ten seconds rather than a search of three shared drives. The examination records supporting the certification — general, specific and practical results where the scheme requires them, with dates and the examiner who administered them. Written practices are audited against their own text, and the text names these records.

Vision examination results are the field most often missing. SNT-TC-1A-based written practices call for near-vision acuity examined annually and color differentiation on a five-year cycle, and both are recorded per person with a date and an examiner. An inspector whose certification is current but whose annual vision examination lapsed four months ago is, against the written practice, not qualified. A tracker that shows only certification expiry reports that person as green.

The fourth is the written-practice revision under which the certification was issued. When the practice is revised — new training hours, a changed experience requirement, a new method added — you need to know which inspectors were certified under which revision to judge whether anything needs re-issuing. Reconstructing that later from memory takes days. Recording it at issue costs one column. This is the same discipline that compliance tracking applies to every other controlled record.

One row per certification, not one row per inspector

The single most common structural error in these spreadsheets is a wide layout: one row per inspector, with UT expiry, PT expiry, MT expiry and radiation-safety expiry spread across columns to the right. It reads well and it fails in three ways. The flag has no single input, so someone writes a formula that takes the minimum of four dates and the other three expiries disappear from view. Filtering for "everyone qualified in PT" becomes a column-specific hunt. And adding a method means restructuring the sheet.

The tall layout — one row per certification, with the inspector ID repeated — fixes all three at once. The flag is arithmetic on a single column. A pivot by method and level gives you the qualification matrix for a bid in one step. Adding a method adds a row. Adding an inspector adds however many rows they hold certifications. Nothing about the structure changes as the company grows from twelve inspectors to eighty.

It also makes the history correct. Renewals become new rows with new issue and expiry dates rather than overwrites of the old ones, so continuity across cycles stays visible, and a gap between one certification's expiry and the next one's issue shows up as an actual gap instead of vanishing under an edit. Gaps matter: an examination performed inside one is a finding on every report signed in that window. Expiry tracking methods all depend on this shape.

What breaks when the spreadsheet reaches forty inspectors

No audit trail. When an expiry date changes from March to September, the spreadsheet records the new value and nothing else — not who changed it, not when, not what it was before. An auditor asking why a certification appears to have been extended has no answer available, and neither do you. Every controlled record in an inspection company carries revision history except, in most firms, this one.

No single source of truth. The file gets emailed to a client during prequalification, copied to a laptop before a site visit, and saved to a second folder by the training coordinator. Within a quarter there are four versions with different content and no way to tell which is current. The version that reaches the client during an audit is the one that was last emailed, which is the one that is furthest out of date.

No enforcement. This is the failure that costs money. The spreadsheet turns a cell red on Monday. On Tuesday the dispatcher — working in the scheduling file, not the certification file — assigns that inspector to a job requiring the expired method. The examination is performed, the report is issued, and the problem surfaces weeks later when a client verifies certifications against the report signatures. Blocking assignment requires the certification data and the crew dispatch schedule to live in one system.

The renewal workflow the columns should drive

Columns without a workflow are a filing cabinet. Attach four actions to the flag. At amber, the owner confirms the inspector intends to renew and identifies the scheme's requirements — hours, examinations, employer attestation. At orange, the application is submitted and the submission date is recorded in the tracker itself, so the row stops escalating while it sits with the issuing body. At red, dispatch is notified and forward schedules are checked for that inspector against that method. At expiry, assignment stops.

Record the outcome, not just the deadline. When the new certificate arrives, add a row with the new issue and expiry dates, attach the scan, and mark the old row superseded rather than deleting it. Deleting is how continuity evidence disappears. Superseding is how you demonstrate, three years later, that a person held an unbroken certification across the period covered by a stack of reports.

Continuing education deserves its own cadence. CEU requirements are earned across a cycle, not at the end of one, so a tracker that only checks CEU status at the 90-day flag discovers the shortfall too late to fix it. Review earned-versus-required quarterly against the as-of date. The inspector who is eight hours short in month thirty has options. The one who is eight hours short in month thirty-five does not.

When to graduate from the spreadsheet to a system

Four conditions each independently justify the move. Above roughly 25 active inspectors, the row count crosses what one person can meaningfully review each week. More than one office maintaining the file introduces concurrent edits, and spreadsheets resolve concurrent edits by losing one of them. A client contract requiring proof of certification currency at dispatch demands enforcement the spreadsheet cannot provide. And an audit finding on personnel records means the evidence chain has already failed once.

What the system must add is narrow and specific. Field-level audit history on every date. Role-based edit rights so certification data is changed by the certification owner and read by everyone else. Document storage with the certificate attached to the row rather than referenced by a path that will break. Automated notification at each threshold to a named owner. And a hard link into scheduling so an expired certification removes the inspector from the eligible list for that method — the enforcement step nothing else provides.

Atlantis builds this on an Odoo-based platform, cloud or on-premise, with certification and calibration tracking, offline field capture and configurable records. The template above is genuinely usable as-is, and running it well for a year is the best possible specification for what you will need the software to do. Bring the filled-in sheet to a demo — it is a faster requirements document than any questionnaire. More templates sit in /tools.

Request a consultation