Skip to main content
Operations

When an Expired Certification Takes the Job

Nobody decides to send a technician with a lapsed certification. It happens in the gap between the renewal list and schedule. Here's how it happens, what it costs, and the four controls that close the gap on a large team.

Published September 26, 2026 6 min read

A technician with an expired certification usually ends up on a job because nothing between the expiry date and dispatch board was connected. The renewal date sat in one place, the schedule got built in another, and nobody's job was to compare them every morning. The fix isn't a better reminder. It's making the expiry date part of the rule that decides who's qualified to go.

Here's how it happens, what it costs, and the controls that stop it on a team large enough that nobody can keep it in their head.

How it happens

It happens in the gaps:

  • The renewal was "in progress". The technician did the hours, sent the form, and everyone assumed it was done. The new card hasn't come through, and the old one ran out on Friday.
  • The date was in the wrong place. Region A keeps a spreadsheet. Region B keeps a calendar. The technician who moved from B to A last spring isn't on either list.
  • The reminder went to someone who left. The person who set up the calendar alerts moved on. The alerts go to an inbox nobody reads.
  • The grace period got mistaken for a renewal. Some bodies allow time to renew late. NATE, for example, allows a 120-day grace period before the technician has to retake the exams, and says a technician whose certifications are all in their grace period isn't considered NATE certified. A grace period to renew isn't the same thing as being renewed.
  • The schedule was built weeks ago. Recurring inspections were assigned in advance, when the certification was still current.

Every one of these is ordinary. On a team with dozens of technicians holding a few credentials each, you should expect to see some of them.

What it costs

We won't put a dollar figure on it, because it depends on your trade, your state and your contracts. But the costs fall into a few buckets, and you'll recognise them.

Redoing the work. If a contract or an inspector needs the work done by someone with a current certification at a stated level, the visit may have to be repeated by someone who has one. That's a second technician, a second truck roll, and a customer who has to let you in twice.

Contract trouble. Commercial contracts in fire protection often name the certification level required for inspection work. Our fire protection inspection guide covers why the right-cert technician matters. If a customer asks who did the work and what they held on that day, you want a good answer.

Licensing trouble. Rules about working with a lapsed license are set by each state and licensing body. Check yours. The safe assumption is that an expired license isn't a license.

Trust. The customer who finds out once will ask to see credentials every time after.

Control 1: One record for each technician and credential

Every certification and license belongs on the technician's record, with its expiry date, in one system. Not a regional spreadsheet, not a manager's calendar. If you run multiple regions, this is the control that makes the others possible. We cover what to record in how to track technician license expirations.

Include credentials that don't expire, and mark them that way. EPA Section 608 is the common example: the EPA says 608 credentials do not expire. Our list of which trade certifications expire covers the rest.

Control 2: Reminders that reach three people

The technician, their manager and the owner or operations lead. At 30 days, at 7 days, on the day, and once after. Three recipients means one person's vacation doesn't become everyone's problem.

Control 3: Assignment that respects the date

This is the control that actually stops it. When the rule that picks a qualified technician checks the expiry date, an expired certification stops counting the day after it runs out, whether or not anyone read the reminder.

Decide your policy for the edge cases before they happen:

  • The expiry day itself. Does the certification count on its last day? Pick one answer and apply it everywhere.
  • "Renewal submitted, card not received." Treat it as expired until the new date is on the record.
  • Manual overrides. Dispatchers will sometimes need to assign by hand. Make sure they know what they're overriding.

Control 4: A weekly look ahead

Reminders cover the next 30 days. Once a week, someone looks at everything expiring in the next quarter, by region. That's where you spot the technician with 90 NICET points to earn and two months to do it.

Build it into onboarding and transfers

Two moments cause most of the gaps on large teams: a new hire, and a technician moving between regions or branches.

  • New hires. Record every credential and its expiry date before the technician's first assignment, not in their first month. Get the dates from the cards or board lookup, not from the résumé.
  • Transfers. When a technician moves region, check which of their credentials are valid in the new state. A license that's current in one state may not count in another.
  • Leavers. Remove their credentials from any regional list you still keep, so the weekly review isn't cluttered with people who've gone.

If you find one after the fact

It will still happen occasionally. Dispatchers are the last line, so give them a simple rule first: if auto-assignment won't pick a technician for work that needs a certification, check the record before assigning them by hand. When one does get through:

  1. Stop further assignments that need the credential until the renewal date is on the record.
  2. List the visits the technician did after the expiry date that needed the credential.
  3. Check your contracts and your state's rules for what those visits need, and whether any have to be repeated.
  4. Talk to the customer where the contract calls for it. It goes better when they hear it from you.
  5. Fix the gap that let it through. Which of the five failure modes above was it?

How FSM Navigator handles it

FSM Navigator runs the whole customer lifecycle in one app, from first booking and signed quote through dispatch, invoicing and service agreement renewal. Certifications are part of the dispatch step: the expiry date sits on the technician's skill, the same record auto-assignment already uses to decide who's qualified.

  • Owners and Managers record the date from the technician's profile in the web dashboard. Nobody can change the date on their own skill.
  • A daily check emails reminders at 30 days, 7 days, on the expiry date, and once after it expires. Owners and Managers get one summary for the team; each technician gets their own.
  • The certification still counts on its expiry day. From the next day, in your company's time zone, auto-assignment stops treating that skill as qualifying the technician.
  • The Certification Expiry Tracker on the KPI dashboard lists everything that has expired or runs out in the next 90 days, which is your weekly look-ahead.

Dispatchers can still assign by hand, the same as today. For teams with hundreds of technicians and custom skill categories, see how it scales on the large teams page, or read the full certification tracking walkthrough.

What it doesn't do: store the certificate itself, or check with any licensing board. It helps you keep track, and keeps auto-assignment in line with the dates you enter. What your contracts and your state require is still yours to check.

Sources

Try Pro free for 14 days

Certification tracking comes with auto-assignment on the Pro and Enterprise plans. A card is required at signup, and nothing is charged until the trial ends.