FieldRoutes for Multi-Location Pest Control: What Each Office Should Own
Branches share a company and a FieldRoutes account, not a map, a wage or a time zone. A practical split of what the company decides and what each office keeps.
In short
Multi-location pest control on FieldRoutes works best when the company sets the rules every branch keeps, such as required skills, preferred technicians and bans, and each office owns what differs locally: costs, working hours, routing goal and the service types it plans. Plan one office at a time, give every shared technician one owning office per day, and compare branches only on definitions they share.
- In FieldRoutes, technicians, customers and each day's route belong to one office.
- Customer rules belong to the company; costs, hours and routing goals belong to each office.
- Rules about the next few days count in each office's own time zone.
- A technician shared between branches needs one owning office for every day.
- Compare offices only on definitions they share.
Running several branches on one FieldRoutes (formerly PestRoutes) account raises a question the software cannot answer for you. In multi-location pest control, what has to be the same everywhere for the company to stay manageable, and what should each office decide for itself?
FieldRoutes is built for more than one office. Its enterprise page promises to measure and compare performance across offices. PestRouting reads each office from FieldRoutes, which stays the system of record, and plans one office at a time, with company-wide defaults that each office can override value by value. How those settings stack falls under my responsibility, and the split below is the one I would set up for any multi-branch operator.
How FieldRoutes divides work between offices
In FieldRoutes, each office has its own technicians, customers and time zone, and every route on every day belongs to one office. That last detail matters the moment technicians cover for another branch. On a day a technician runs another office's route, the day belongs to that other office, and an appointment booked by one office can sit on a route of the other.
When PestRouting writes an adopted plan back, it never touches another office's appointments, and it does not write a technician's day when that day's route belongs to another office. The rule underneath is worth copying into your own process. One office owns each technician day.
What the company decides and what each office owns
| Setting | Company decides | Each office decides |
|---|---|---|
| Customer rules: preferred technician, preferred days and times, required skills, bans | Yes. A customer rule should mean the same in every branch | Only with a written reason |
| Routing goal | A default | Yes. A dense metro branch and a rural one may want different goals |
| Cost per hour, mile and route | A default | Yes. Wages and drive distances differ by market |
| Working hours and closures | Company holidays | Office hours and local closures |
| Days the planner leaves alone | A baseline, such as nothing moves up to 2 days out | Its own exceptions on top |
| Service types it plans | No | Yes. One branch may leave rodent exclusion to its own crew |
PestRouting uses the same structure in its configuration. Organization Settings hold the defaults, and Office Settings change one value at a time. Each value is marked OWN, INHERITED or DEFAULT, so nobody has to guess where a number came from. An office's exceptions come on top of the company's. Where both cover the same day, the office's exception wins, but an office cannot delete one the company set.


Time zones change what tomorrow means
Rules that protect the next few days count from the day the plan runs, in each office's own time zone. A company rule such as "up to 1 day out: add nothing and move nothing" covers different hours in an Eastern and a Pacific branch. That is the behavior you want, because a company-wide lock should mean each branch's own tomorrow. Our guide on when to lock tomorrow's routes covers how many days to protect.
The nightly sync follows the same logic. Each office reads its technicians and subscriptions from FieldRoutes at 3 a.m. in its own time zone, so a plan started in the morning works from that night's data.
Shared technicians need an owner for every day
Floaters are where multi-branch routing usually breaks. A technician who works for two branches shows up in both, often with customers in both, and each dispatcher assumes the other planned the overlap. Settle it with a short procedure:
- Give each floating technician a home office in FieldRoutes.
- Decide which office owns them on which weekdays, and close the other office's routes for those days.
- Check customers in one office whose preferred technician belongs to another. In PestRouting they show under Needs attention as "Preferred tech off the crew", with the technician named, until someone decides.
- Record any cross-branch cover as a dated exception with an end date, never as a standing arrangement.
Licenses and state lines
Branches near a state line often serve customers in two states. According to the Bureau of Labor Statistics, state laws require pest control workers to be licensed, so a technician who is legal on one side may not be on the other. PestRouting can hold a skill for one state only, and a job that requires it goes only to a technician who holds it for the customer's state. Our guide to FieldRoutes skills and licenses covers the setup, and the territory guide covers keeping a one-state technician inside that state.
Compare branches on shared definitions
FieldRoutes lets each branch see its own reports and use its own KPIs, as one large operator describes in a FieldRoutes customer story. In the same piece, another operator describes splitting its 10 offices into four regions. That flexibility helps a branch manager and makes branch rankings meaningless, unless a few definitions are fixed company-wide first:
- What counts as a callback, and which service types count as recurring.
- How production value is priced on a visit.
- Which part of the day is paid: depot to depot, or first stop to last stop.
- The bounds behind a route grade, for example miles and production per route, set per office where markets differ.
With those fixed, a rural branch is no longer judged on a metro branch's mileage. Our post on FieldRoutes reporting lists the metrics worth comparing.
Key insight: A branch comparison is only as fair as the definitions under it. Agree on them before the first ranking, or the ranking turns into a debate about data.
Roll it out one office at a time
Start with the branch whose FieldRoutes data is cleanest, and set the company defaults from it. Add the next branch, override only what genuinely differs, and write down why. Each override should have a reason someone else can read a year later. If a value ends up overridden in every office, it was never a company default, so move it.
Frequently asked questions
Can FieldRoutes handle multiple locations?
Yes. FieldRoutes keeps several offices in one account, each with its own technicians, customers, routes and time zone, and it reports across offices. The work for a multi-location operator is deciding which rules are shared and which are local.
Should every office use the same scheduling rules?
Customer rules should be the same everywhere: preferred technicians, preferred days and times, required skills and bans. Costs, working hours, the routing goal and the service types an office plans can differ, as long as each difference is written down.
How do I schedule a technician who works for two offices?
Give them a home office and decide which office owns them on each weekday. In FieldRoutes a technician's route on a given day belongs to one office, so close the other office's routes for those days and treat any other cover as a dated exception.
Does PestRouting plan all offices at once?
No. A PestRouting planning session plans one office over a date range, using the company's settings plus that office's own overrides. With All Offices picked in the office switcher, lists such as recent sessions show every office together.
Do branches in different time zones need different rules?
Usually not. A rule such as keeping the next two days as booked counts days in each office's own time zone, so one company rule fits every branch. Set an office rule only when a branch needs more or fewer protected days.
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.



