A pool service company in Phoenix keeps 340 accounts on a clipboard route sheet that was built in 2019 and has been amended by hand ever since. New customers get appended to the end of whatever day has room. Cancellations leave holes. The Tuesday route now crosses the same intersection 4 times, and nobody has looked at the whole thing at once in years, because nobody has ever put it on a page where it could be seen.
Address driven businesses
Some companies sell to a location instead of to an office. Pest control, landscaping, medical equipment servicing, vending, HVAC, commercial cleaning, and equipment rental all share the same operating unit, which is a customer address that has to be visited on a schedule.
For these businesses, the customer list is a list of places. That changes what the list is for. A CRM is designed to answer questions about accounts and deals. A route sheet answers questions about a single day. Neither answers the question that governs the week, which is which addresses are near which other addresses.
Losses in a route sheet
A route sheet sorts alphabetically or by city, which puts every Phoenix account together and stops there. Two customers 400 feet apart on opposite sides of a city line sort into different sections, and a technician drives between them twice in one week.
The pattern gets worse as the business grows. At 40 customers, the owner holds the geography in memory. At 340, nobody does, and the route sheet becomes a record of decisions made when the company was smaller.
Putting the list on a map
The fix starts with an export. Address, customer name, service frequency, and last visit date are enough. The 340 rows become 340 pins in software that can map multiple locations, and the clusters the route sheet has been ignoring show up immediately.
Most owners find 2 or 3 surprises in the first view: a dense pocket of customers in one suburb split across 3 different service days, a single account 40 miles out that consumes an entire afternoon, and a part of town with 1 customer where the company once had 12.
Coloring the pins by service frequency adds a second layer. Weekly accounts and quarterly accounts have different geographic requirements, because a weekly customer 30 minutes away costs 26 hours of driving a year and a quarterly one costs 2. When both are the same color on the map, the expensive ones hide among the cheap ones.
Service days grouped by area
With the pins visible, the service days can be redrawn as areas rather than as lists. Everything in the northwest quadrant becomes Tuesday. Everything south of the freeway becomes Wednesday. The rule is simple enough for a dispatcher to apply to a new customer without asking anyone, which is the property the old route sheet lacked.
Restaurant operators size their delivery zones by time rather than by distance. In a QSR Magazine feature on getting delivery done right, an operator recommended a radius that keeps a round trip inside 20 to 30 minutes, and noted that the same drive time is worth about 2 miles in downtown Dallas and 5 miles somewhere less congested. A service area drawn in miles will be too big in the city and too small in the suburbs.
The cost of getting the address wrong
Bad location data is expensive in a way that does not show up as a line item. A 2022 survey of more than 1,000 customers by the routing company Circuit found that nine out of 10 had a food or grocery delivery go wrong at some point, with refunds the most common response.
Customers assign the blame locally. Research from eduMe found that 63% of consumers had received at least one inaccurate delivery order in the previous year, and that a majority held the restaurant responsible rather than the delivery platform. A service business carries that exposure too. The customer whose Thursday appointment was missed because the address geocoded to the wrong side of the highway does not distinguish between a dispatching error and indifference.
Scheduling rules with legal deadlines
Where technicians are hourly, the schedule is also a compliance question. A running list of states and localities with predictive scheduling mandates shows how many jurisdictions now require employers to post schedules about 2 weeks ahead and limit late changes.
A route built from a map is easier to publish 2 weeks out than one assembled each Friday from the clipboard, because the areas stay fixed even when individual stops move. The rule is the boundary. The stops inside it change week to week without changing who works where.
Keeping the map honest
Re-export after every quarter so new customers appear where they actually are, and flag any address the software could not place. A failed match usually means a typo, a missing unit number, or a rural route that needs coordinates instead of a street address, and each one is a stop somebody will eventually be sent to find.
Also mark the accounts that will never fit a route. Every service business has a few, kept for history or margin. Naming them on the map stops them from quietly reshaping a day around themselves.
The map is also the fastest way to answer questions that arrive from outside the business. A customer asking to move to a different day, a technician asking to swap territories, an insurance broker asking how far the service area extends, and a buyer asking where the revenue is concentrated are 4 versions of the same question, and each has an answer on the same screen.
The number behind the decision
For the Phoenix pool company, the figure that mattered was 4. That was how many times the Tuesday route crossed the same intersection before anyone plotted it. Redrawing the week around 4 geographic zones cut the route to a single pass through that corridor and freed roughly 90 minutes a day, which at 5 days a week is more than 1 additional service call per technician per day, taken entirely out of driving.
This content is provided for informational purposes only and is not a substitute for professional advice. AFP editorial staff were not involved in the creation of this content.
Share
