FieldRoutes Preferred Time vs Exact Time: When to Use Each
FieldRoutes keeps a customer's wish on the subscription and the promise on each appointment. Mixing the two up is how routes fill with Timed visits nobody needed.
In short
In FieldRoutes, preferred time is a standing wish on the subscription, stored as a preferred start and end, while an exact time is a Timed arrival window on one appointment. Preferred time vs exact time is a choice between a wish the planner can honor across many days and a fixed point that shapes the whole route. Default to preferred time or anytime, and book a Timed window only for a constraint you can name.
- Preferred time lives on the subscription; the arrival window lives on each appointment.
- FieldRoutes has no exact time field. Offices mean a Timed window.
- Anytime appointments carry 8 a.m. to 8 p.m. as a placeholder, not a promise.
- A constraint that repeats every visit belongs on the subscription, not in a new Timed booking each time.
- Count Timed appointments weekly, because the share grows by habit.
Preferred time vs exact time sounds like a settings choice. In FieldRoutes (formerly PestRoutes) it is a data question first. The two promises live in different records, they last for different lengths of time, and they cost a route very different amounts.
PestRouting, the planner I help build, reads both from FieldRoutes, which stays the system of record, and plans routes that keep them. Planning whole months under those promises has shown us how differently they behave, and that difference is the best guide to when each one belongs on a booking.
Where FieldRoutes stores each promise
| Preferred time | Arrival window | |
|---|---|---|
| Lives on | The subscription | Each appointment |
| Stored as | A preferred start and a preferred end, next to preferred days and the preferred technician | Anytime, AM, PM or Timed, with a start and an end |
| Means | When the customer would like every visit | What the office told this customer for this visit |
| Lasts | Until someone edits the subscription | One visit |
| Cost to the route | Low, because the planner can pick among many days and slots | High when Timed, because the visit becomes a fixed point |
FieldRoutes has no field called exact time. When an office says exact time, it means a Timed appointment, often with a window of an hour or less. In the FieldRoutes API the appointment's time window reads AT for anytime, AM, PM or Timed.
Two placeholders trip up reports. An anytime appointment still carries 8 a.m. to 8 p.m. as its start and end, and a subscription without a preferred time stores midnight to midnight. Neither is a promise. A report that counts them as windows makes the office look far more tightly booked than it is.
When to use preferred time
Preferred time fits a recurring customer with a standing constraint. Someone who starts work at noon wants the quarterly visit in the morning, every quarter. Put that on the subscription once, and every future visit carries it without another phone call. Our glossary entry on preferred time covers the booking conversation behind it.
It also fits the customer who says "mornings" and means "not during the school run". Ask one more question at booking. The real boundary is usually wider than the first answer, and a wider preferred time gives the planner more days and slots to work with. A narrow preference saved without that question is one way a recurring schedule drifts into a shape nobody chose.


When an exact time is worth it
A Timed window earns its place when someone else's schedule is fixed. A commercial site whose manager opens the back door at 7, a gated property with one access slot, an inspection with a buyer and an agent on site, a first visit where the customer has to walk the technician through the house. In those cases the promise wins the account or makes the job possible.
Outside them, a Timed window is route capacity spent on comfort. One Timed visit on a 12-stop route is cheap. Two at opposite ends of the territory decide where the technician drives all morning, whatever else is on the route. Google's routing documentation treats each time window as the only span in which a visit may happen, and every window you add removes orders the day could have been driven in. The glossary entries on exact time and time windows explain how to count them.
Key insight: A preferred time costs the route a little on every visit. A Timed window costs it a lot on one visit. Repeat the Timed booking every quarter and you pay the high price every quarter.
A booking ladder for the office
FieldRoutes' own scheduling guide notes that customers have limited time to meet technicians and prefer specific days and times. The ladder below takes that seriously and spends the tight promises where they matter:
- Ask whether the customer needs to be home. Exterior perimeter service often does not, and anytime is the honest answer.
- Offer the service day first.
- If a day is not enough, offer AM or PM.
- Book a Timed window only for a constraint you can name, and note the reason on the appointment.
- If the constraint repeats every visit, move it to the subscription as a preferred time, so it gets planned instead of negotiated each time.
What a planner does with each
FieldRoutes' optimization can pick days and times from customer preferences and due dates, as its HomeShield case study describes. In PestRouting, while Respect preferred times is on, a visit lands inside the time of day its subscription asks for. A booked visit keeps the window the customer was given. When the office keeps bookings on their day, a booked visit's time may shift only inside that window.
Where the office lets the planner reschedule recurring work, a recurring visit promised 9 to 11 may move to another day of its period and keeps 9 to 11 on the new day. The customer was promised a time, and the date was never part of that promise. New visits go back to FieldRoutes with an arrival window inside the customer's preferred time, or as anytime when there is none. Which days the planner may touch at all is a separate decision, covered in our guide on when to lock tomorrow's routes.
Preferred days follow the same logic, with one wrinkle. FieldRoutes holds one preferred day per subscription, while a customer may accept two. Our page on preferred days in FieldRoutes explains how PestRouting keeps the whole set.
What to count every week
- The share of appointments booked as Timed, per route.
- How wide those Timed windows are, and whether they are narrowing.
- The share of recurring subscriptions with a preferred time, and how narrow the preferred times are.
- Timed visits that repeat on the same customer every cycle, which belong on the subscription instead.
Leave the anytime placeholders out of every count. If the Timed share climbs while the number of customers with a real constraint stays flat, the office has a habit and no policy, and the fix is training the people who book. The FieldRoutes route optimization guide shows what a heavily timed route does to any optimizer.
Frequently asked questions
What is the difference between preferred time and exact time in FieldRoutes?
Preferred time is a standing wish stored on the subscription as a preferred start and end, and it applies to every visit. An exact time is a Timed arrival window on one appointment. The first guides planning, the second fixes one visit in place.
What does anytime mean on a FieldRoutes appointment?
Anytime means the office made no time promise for that visit. FieldRoutes stores it as AT, with 8 a.m. to 8 p.m. as a placeholder start and end. Treat those appointments as fully flexible when you count windows.
Should recurring customers get an exact time?
Rarely. If a recurring customer has a real constraint, record it once as a preferred time on the subscription. Booking a fresh Timed window each cycle spends the most expensive promise over and over for the same need.
Does PestRouting keep the time window a customer was promised?
Yes. PestRouting keeps every arrival window already booked in FieldRoutes, so a visit may move only inside its window, and a recurring visit that changes day keeps its time. New visits are written back with a window inside the customer's preferred time, or as anytime.
Do commercial accounts need exact times more often?
Often, yes. Site access, a contact who must be present and audit schedules are real constraints, so Timed windows are more common there. Our guide to commercial and residential routes covers how to plan both on the same team.
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.



