Why an Expired Certification Should Block Dispatch Automatically

It's 2:00 in the afternoon and a licensed job needs covering. The nearest technician is close, free, and no longer certified for that work. Nobody has to remember the expiry date, because the dispatch board won't let them be assigned. The dispatcher picks the next person and moves on.

Here is the version most companies live with. Same job, same afternoon, and the board doesn't know. The technician's certification lapsed last month in a spreadsheet, or in the learning system, or in an HR record, and the dispatch tool has never heard of any of them. The technician goes. Nobody notices until an audit, or a customer, or a stop-work order.

In a licensed trade, the HR record is an operational record. That's the whole argument of this article, and it has a practical corollary: a certification should be something the dispatch board can read.

The compliance gap has a shape

Credentials are tracked in one place: a spreadsheet, a learning management system or an HR system. Assignments are made in another, the field service tool. Neither reads the other. This is the sixth of the six information gaps, and it's the one with the highest stakes and the lowest visibility.

Its cost is binary. It costs nothing, for months or years, until there's an audit finding or a stop-work order. Then it costs a great deal at once. That's why it tends to stay off spreadsheets, and why it's the one gap where a company's honest confidence matters more than an average. We show how to think about that number in what disconnected field service systems actually cost.

What the credential is depends on the trade. In HVAC, technicians who handle refrigerants need EPA Section 608 certification. In electrical work, state licensing and code training apply. In fire and life safety, licensing and manufacturer certification are tracked alongside the records an authority having jurisdiction may ask for. In utilities, safety training and licensing for regulated trades carry the same weight. We'll take up the trade-specific versions in the articles on fire and life safety, electrical contractors and utilities and telecom.

To be clear about what this article isn't: it's not legal advice, and it doesn't tell you what any regulation requires. It describes an operational risk, and how software can help you avoid it.

Why reminders do not solve it

Most companies already have renewal alerts. They're necessary. They aren't enough.

An alert informs a person. It doesn't stop a dispatch. The failure happens in the space between the alert and the board, and that space is filled by people who are busy. The dispatcher is also the supervisor, the customer service representative and the first call for tech support. The renewal email went to someone else, or to a shared inbox, or to a manager who was on leave.

Nobody in that chain did anything wrong. The system just relied on a memory holding up under load, which memory doesn't do.

What requirement-aware assignment means

The alternative is straightforward to describe. Work types carry the certifications they require. A technician whose credential has lapsed can't be assigned to that kind of work, and the board says so at the moment of assignment, when the dispatcher can still do something about it.

Two things follow from that.

The rule applies to recommendations, too. When the board suggests a technician for a job, it shouldn't suggest one the credential doesn't support. Governance isn't only about what an AI can read. It's also about what it's allowed to propose. We cover that in where AI actually changes a field service operation and whose permissions does the AI inherit.

And it works in the other direction. A technician records an EPA recertification on Monday and is dispatch-eligible on Tuesday. There's no phone call to the office and no manual update to a second system. Nobody has to remember to tell the board that someone is qualified again.

The record has to be one record

A dispatch board can only read a credential if the credential lives where the board can see it. That's an architecture question, not a feature one.

When HR, learning and recruiting all write to the record the dispatch board reads, compliance stops being a spreadsheet. A few pieces make this concrete:

• Certification tracking with expiry alerts, so the people who need to know in advance do.
• Training that closes the gap it found: courses assigned automatically by role or location and delivered on the phone, so a technician can renew without a trip to an office.
• A role change in the HR system updating access and training assignments together, so a promotion or a transfer doesn't leave stale permissions behind.

This is the difference between an FSM tool and a workforce platform, and it's why they're different purchases. A field service tool manages the job. A platform that also holds the employee record can connect the job to the person's qualifications. It's the argument in why field service software has been split down the middle for 20 years.

MangoApps puts field service on the same platform as People Operations, learning and recruiting, so a certification recorded in one is visible to the other.

Setting it up: one work type, three credentials

The idea is easier to trust once you've seen it applied to one job. Take a single work type, say a refrigerant recovery call. List what a technician needs to be assigned to it: the certification for handling refrigerants, the company's own safety course, and whatever licensing your jurisdiction expects for the work. That list is the requirement.

Now the board has something to check. When the dispatcher opens the job, every technician either meets all three or doesn't, and the ones who don't are visibly out of the running with the reason attached. A technician who is two weeks from a renewal is a different case from one whose credential lapsed in March, and the record can tell those two apart.

You don't need to model every work type on day one. Start with the two or three that carry the most risk and the most licensing, and add others as you go. In a typical implementation, certification requirements per work type are set in weeks three and four, which is early enough that the pilot crew works against them from their first real job.

Objections worth answering

"We already track certifications in our learning system." Good. That's the record. The question is whether the board reads it. A learning system that knows about a lapse and a dispatch tool that doesn't are two systems, and the gap between them is the one this article is about.

"Our dispatchers know their technicians." They do, and it's a real asset. It also doesn't scale past the next vacation, the next new hire or the next busy day. Knowing someone's history and remembering the exact date a credential lapses are different jobs, and only one of them belongs to software.

"We'd rather trust the technician to tell us." Most will. The problem isn't honesty. A technician can be unaware their credential lapsed, or believe a renewal was filed that hasn't been processed. A system that checks doesn't accuse anyone. It removes a question nobody should have to answer under pressure.

What to ask a vendor

You don't have to take anyone's word for it. There's a demo that settles it in two minutes, and it's request four of the five we suggest sending before any vendor meeting:

"Expire a certification, then try to assign that technician."

Watch what happens. Either the board declines the assignment, or it doesn't. If the answer involves an alert, a report or a manual step, the credential isn't on the record the board reads.

Ask two more things while you're there. Whose record does the dispatch board read? And who else writes to it? If HR, learning and the field service tool each keep their own copy, the gap is still open, however good the sync is.

This is question seven in the twelve-question evaluation guide.

The stop-work order you never get

When dispatch works this way, audit-ready records with full version history aren't a separate project. They're a byproduct of the way work gets assigned. The order that never arrives is the return on all of it, and it's a hard one to put on a spreadsheet because it's an event that didn't happen.

The practical starting point is small. Pick one licensed work type, list the credentials it requires and see whether your current board can tell who holds them today. If it can't, you've found your first gap. For people staffing a seasonal or growing workforce, the staffing article picks up where this one stops, and the implementation guide shows how to set the requirements per work type in weeks three and four.

The certification question is one of twelve in the evaluation section of the Field Service Management guide, which also covers the other five gaps. You can also see the Field Service Suite itself.

Frequently asked questions

How do you track technician certifications and licenses?

Keep certifications and licenses on the employee record with expiry dates and renewal alerts, and make the record readable by the system that assigns work. A spreadsheet works until someone forgets to open it. The stronger approach is a record that HR, training and dispatch all read, so a lapse or a renewal changes what the dispatcher sees without any manual update.

What is requirement-aware or certification-based dispatch?

It means work types carry the certifications they require, and the dispatch board checks the technician's credentials at assignment. A technician whose credential has lapsed can't be assigned to that type of work, and the board says why. When they recertify, they become eligible again without anyone updating a second system.

Can scheduling software automatically block an uncertified technician?

It can if the credential and the schedule live on the same record. If certifications sit in a separate spreadsheet or learning system, the scheduling tool has nothing to check. Ask a vendor to expire a certification in a demo and then try to assign that technician. The result shows whether blocking is automatic or depends on a person remembering. In MangoApps, work types carry the certifications they require, and a technician whose credential has lapsed cannot be assigned. The board says so at assignment.

How quickly should a recertification update dispatch eligibility?

Immediately, once it's recorded. A technician who records a recertification on Monday should be dispatch-eligible on Tuesday at the latest, with no phone call to the office and no second entry. Delays here usually come from a manual step between the training record and the dispatch tool. In MangoApps, a recertification recorded on Monday makes the technician dispatch-eligible on Tuesday.

Which industries need certification-based dispatch most?

Licensed and regulated trades: HVAC, electrical, plumbing, fire and life safety, and utilities and telecom. Any trade where the wrong technician on a job is a compliance problem has the same need. The specifics differ by trade and jurisdiction, so check with your compliance lead about what applies to you.