FieldRoutes Preferred Time vs Exact Time: When to Use Each
Preferred time and exact time should be governed like scarce scheduling inventory, or they will quietly destroy route flexibility and margin in FieldRoutes.
Last updated on April 2, 2026.
The difference between preferred time and exact time in FieldRoutes is not cosmetic. It is a margin decision. Every exact-time promise spends route flexibility before dispatch even starts. That can be worth it when a real constraint exists. It becomes expensive when teams hand out exact times simply to avoid a difficult booking conversation.
Google's vehicle routing guidance for time windows explains the basic rule: tighter time constraints shrink the set of feasible routes. In a pest control business, that means more windshield time, more awkward sequencing, and more pressure on the rest of the day when too many accounts are promised narrow arrival windows.
| Promise type | Best use case | Operational tradeoff |
|---|---|---|
| Preferred time | Recurring residential work with some customer flexibility | Keeps more routing options open |
| Tight preferred window | Customers with moderate availability limits | Useful compromise when exact time is unnecessary |
| Exact time | Commercial coordination, locked access, or true hard constraints | Consumes flexibility and raises routing cost |
Preferred time should be the default promise
Most recurring pest control work does not need an exact timestamp. It needs a credible service window that fits the customer's day while still allowing dispatch to build a dense route. FieldRoutes' scheduling guidance highlights the value of organized service windows and realistic arrival expectations for both customer experience and route efficiency.
Preferred time works well because it protects two things at once: the customer feels heard, and operations keeps enough room to sequence intelligently. That balance matters more in recurring businesses than in one-off field service because the cost of a bad promise repeats over and over again.
Key insight: Exact time is not better service by default. In many cases, it is just prepaid schedule inflexibility.
Exact time should require a reason code
Exact times belong where the customer or site truly demands them: commercial access coordination, gated properties with narrow availability, multi-party inspections, or a first visit where the team must meet a stakeholder on site. If the booking team cannot explain why the appointment must be exact, it usually should not be.
This is where governance matters more than feature knowledge. The software can support any promise you feed it. Your job is to decide which promises deserve that rigidity. Without that discipline, exact-time creep spreads one booking at a time until dispatch is sequencing around a calendar full of artificial constraints.
What exact-time creep really costs
FieldRoutes' route optimization guidance links better routing to lower drive time, better on-time performance, and stronger customer satisfaction. Exact-time overuse pushes against all three. Routes become less dense, technicians wait between hard commitments, and late-first-stop pressure increases because one early appointment can throw off the whole board.
That is why exact-time usage should be reviewed as an operating metric, not only a customer service setting. High exact-time share often signals weak booking discipline upstream, not just a busy calendar.
Weak booking rule
Give exact time whenever the customer asks so the call ends quickly.
Strong booking rule
Offer preferred windows first, use exact time only when a documented constraint justifies it.
Build a promise ladder for the booking team
A good booking script moves from most flexible to most rigid. Start with the technician's service day or broad preferred window. Narrow only if the customer truly cannot accept it. Move to exact time only when the constraint is real and the account value justifies the operational cost.
This is the same issue underneath our article on dispatch debt: the route often becomes unstable because promises were made without pricing the cost of that promise into the schedule.
What to review in FieldRoutes every week
- Exact-time rate: how many appointments are locked too tightly.
- Exception count: how many notes and overrides were needed to honor those promises.
- Late-first-stop frequency: whether early rigidity is throwing off the whole day.
- Preferred-to-exact conversion rate: whether the booking team escalates too fast.
If those numbers drift up together, the business is buying customer convenience with route instability.
30-day action plan
- Week 1: define which job types are allowed to use exact time and which are not.
- Week 2: train booking staff on a promise ladder that starts with preferred windows.
- Week 3: require a reason code or note for every exact-time appointment.
- Week 4: review exact-time share by CSR, route, and territory with dispatch.
The result is not less customer care. It is better promise discipline. And better promise discipline is one of the simplest ways to protect the route book before optimization even begins.
Frequently asked questions
Should exact time ever be the default in FieldRoutes?
No. Exact time should usually be reserved for accounts with a true operational constraint. Defaulting to it spends routing flexibility too early.
What is the advantage of preferred time?
Preferred time gives customers a reasonable expectation without forcing dispatch into a narrow route shape. That usually improves density and on-time performance.
Can commercial customers still need exact times?
Yes. Commercial access rules, site coordination, and inspections often justify tighter promises. The key is to use exact time where it is truly necessary, not where it is merely convenient to promise.
How do you know if your team overuses exact time?
If dispatch is constantly overriding routes, same-day flexibility is low, and exact-time share keeps climbing, you likely have a promise discipline problem rather than a routing problem.
Written by
PestRouting Team
Practical guidance on pest control route optimization, scheduling, and operational efficiency.
Liked this? Get the same analysis on your routes.
20 minutes. We listen first. Then you decide if a real audit makes sense. No pitch, no pressure.
