FieldRoutes Skills and Licenses: Matching the Right Technician to Every Job
Skills decide who may take a termite or mosquito job. How FieldRoutes stores them, where they go missing, and how to keep specialist hours for specialist work.
In short
FieldRoutes skills work as a filter: a service type requires a skill, and only technicians who hold it, on their employee record or through a license, should get the job. When skills are missing from the data, every technician looks eligible and nothing warns you. Require skills only for what is mandatory, check who holds each one in each area and state, and protect specialist hours with a separate rule.
- A required skill works only if the service type requires it and the technician holds it in the data.
- Missing skills cause no errors. They make every technician eligible.
- Licenses are a state matter, so a multi-state office has to know who holds what where.
- Preferences and training status do not belong in required skills.
- Skills decide who may take a job, not how specialist hours get spent.
A termite inspection goes to a technician without the license, and nobody notices until the report comes back wrong. FieldRoutes skills exist to prevent exactly that, and they do, once they are actually in the data. The failure we look for first when an account connects is a missing skill setup, because a wrong one at least produces complaints.
PestRouting reads skills and licenses from FieldRoutes (formerly PestRoutes), which stays the system of record. While Enforce required skills is on, PestRouting gives a job that needs a skill only to a technician who holds it. That part of the product is my responsibility, so the details below come straight from the data model.
How FieldRoutes stores skills and licenses
Three records decide who may take a skilled job. The service type names the skills it requires. The technician holds skills directly on their employee record. A license can grant skills too, and a license can name the states it covers.
| Record | What it carries | What breaks when it is missing |
|---|---|---|
| Service type | The skills a job of this type requires | Every technician looks eligible |
| Employee record | The skills a technician holds | A qualified technician never gets the work |
| License | Skills it grants and the states it covers | Skills granted in the wrong state, or not at all |
FieldRoutes presents matching jobs to technician expertise, certifications and location as a core part of scheduling in its route efficiency guide. That matching is only as good as these three records. A service type with no required skill tells every tool, FieldRoutes' own included, that anyone may do the job.
Missing skills fail silently
When a skill is missing, nothing errors. The job simply opens up to everyone. In one of our published results stories, skills had never been entered in FieldRoutes, so the first planning run let anyone take any job. The office pointed it out while reading the plan, and the skills go in before the next run.
Our audits handle the same gap in the open. When a job needs a skill nobody is on record as holding, the audit gives it to whoever actually did the work and lists that assumption. A planning session does the opposite. A stop whose required skill no available technician holds is left unplaced, and the reason names the missing skill, for example "Preferred technician lacks a skill" with the skill and the technician.
Key insight: A wrong skill setup produces complaints. A missing one produces nothing, which is why it survives for years.
Licenses are held per state
Pest control licensing is a state matter. The Bureau of Labor Statistics notes that state laws require pest control workers to be licensed. The EPA's certification standards set 10 federal categories for commercial applicators, which states, territories and tribes may add to or remove from. An office whose customers sit on both sides of a state line needs to know which technician is licensed where.
FieldRoutes keeps the skills on a technician's employee record for every state. PestRouting can also hold a skill for one state only, say termite work in one state and mosquito work everywhere, and then sends a job that requires the skill only to a technician who holds it for the customer's state. That regional rule stays in PestRouting, because the employee record in FieldRoutes has nowhere to store it.


Require only what is mandatory
Every required skill removes technicians from the pool for that job. That is the point when the skill is a license. It is a problem when the "skill" is really a preference, because it shrinks the pool for nothing and leaves stops without a slot.
| Kind of requirement | Example | Make it a required skill? |
|---|---|---|
| Legal license | Fumigation, termite work in a given state | Yes, held per state |
| Service line | Termite, mosquito, wildlife exclusion | Yes, on the service types that need it |
| Equipment | A misting rig or a lift on the truck | Yes, if the job cannot happen without it |
| Training status | Still riding along with a senior technician | No, decide it by whom you plan |
| Customer wish | "Send Ana again" | No, that is a preferred technician |
My test is simple. If the job is illegal, unsafe or physically impossible without it, make it required. Everything else belongs in the preferred technician field or a note.
Skills decide eligibility, not capacity
A termite specialist who also holds the general pest skill will happily fill a quiet Tuesday with quarterly perimeter visits. Every rule is satisfied, and the specialist hours are gone when two inspections come in on Wednesday. Skills say who may do a job. They say nothing about how scarce hours should be spent.
Two habits help. First, count how many technicians hold each skill in each area. A skill only two people hold is the tightest limit in any plan and the first place stops go unplaced. If it is short every week, that is a hiring question. Second, decide what wins when the schedule is full. In PestRouting, setting When fully booked, prioritize to Longer visits gives a 4-hour commercial job its spot before four 1-hour visits, and High-production visits favors the work that earns more. With room for everything, the setting changes nothing.
A 30-day cleanup in FieldRoutes
- List every service type and the skills it requires. Mark the ones that should require a skill and do not.
- For each technician, compare the skills and licenses in FieldRoutes with what they actually hold, state by state.
- Count holders per skill in each area. Every area needs at least one technician for each skill its customers require, which ties skills to your territory setup.
- Plan one week, or re-plan a past month, and read every stop that could not be placed. Fix the data behind each reason.
- Repeat the check after each hire, each license renewal and each new service line.
Skills are also the first thing to check when an optimizer keeps sending the wrong person, as our guide to FieldRoutes route optimization explains.
Frequently asked questions
Where are skills set up in FieldRoutes?
FieldRoutes keeps skills on three records. The service type lists the skills it requires, the technician's employee record lists the skills they hold, and a license can grant skills and name the states it covers. All three have to agree for a skill to filter anything.
Why does FieldRoutes send a technician without the right license?
Usually because the requirement is not in the data. Either the service type requires no skill, or the license is not recorded on the technician, so every technician looks eligible. Fix the service type first, then the technicians.
Can a technician hold a skill in only one state?
In PestRouting, yes. A skill can count everywhere or in one state, and a job requiring it goes only to a technician who holds it for the customer's state. FieldRoutes keeps employee skills for every state, so that rule lives in the planner.
What happens when no technician has the required skill?
In PestRouting the stop is not planned, and its reason names the missing skill. On the Configuration map, the same customers appear under "A skill this job needs", grouped by what would fix them, so you can give the skill to a technician or move one onto the area.
Are skills the same as a preferred technician?
No. A required skill says who may do a job; a preferred technician says who should. If the preferred technician lacks a required skill, the two rules conflict, and the stop needs a decision instead of a quiet override.
Ran into a word you would define differently? The glossary says how we use every term on this page.

Written by
Ahmed Abd El DayemCo-Founder & CTO, PestRouting
Responsible for product, engineering and data security at PestRouting, including the route planner and the FieldRoutes integration.
Ahmed on LinkedInLiked this? Get the same analysis on your routes.
30 minutes. We listen first. Then you decide if a real audit makes sense. No pitch, no pressure.



