A full calendar can still be an inefficient route
Five nearby customers and five customers scattered across town can produce the same number of visits and very different working days. Route density means having enough compatible work close together to reduce unnecessary travel. It does not mean promising the shortest possible route regardless of access, skills or customer timing.
Start with the actual promises. Some customers need a fixed arrival window. Others have a flexible service day. A gate may open only after a certain time; one site may require equipment another crew does not carry. These constraints belong in the plan before you group stops by neighborhood.
Measure the route from departure to return, not just between customer addresses. Load-up, breaks, disposal, supply stops and pack-up occupy capacity too. A map that shows a short drive cannot tell you how long the crew needs to complete an overgrown lawn or negotiate access.
Build a route sheet with time and constraints
Use this original planning sheet for each candidate stop. Estimate with actual past visits where possible. Mark unknown durations as uncertain so the office knows which jobs need a site review or additional space.
| Field | Planning question |
|---|---|
| Area and service | Which neighborhood and agreed tasks? |
| Customer promise | Exact appointment, arrival window or flexible day? |
| Crew and equipment | Who can do the work with the necessary equipment? |
| Duration and travel | Expected elapsed visit time and consistent travel allocation? |
| Access and dependencies | Gates, parking, customer presence or earlier work needed? |
| Exception space | Where can delays fit without breaking later promises? |
Keep elapsed crew time separate from person-hours. A two-person crew working for forty minutes uses forty minutes of route capacity but eighty minutes of labor. You need the first number to build the day and the second to review the cost.
Worked example: the same work, less driving
Consider a fictional day with five visits. Each needs forty minutes of elapsed crew time, so service takes 200 minutes. Allow another sixty minutes for loading, breaks, disposal and pack-up. Before any travel, the day uses 260 minutes.
In one plan, total depot-to-depot travel is 140 minutes. Total modeled time is 400 minutes. In a geographically grouped plan, total travel is 80 minutes, making the modeled day 340 minutes. The difference is sixty minutes in this example. It is not a promise that routing software or a neighborhood strategy will save an hour every day.
Now check the grouped plan against customer windows and access. If the second customer cannot admit the crew until noon, the apparent saving may disappear into waiting time. A plan is useful only if it can actually be delivered. Verify travel using realistic departure times, then leave room for uncertainty.
Do not fill every recovered minute immediately. Use several completed route days to learn whether the estimate holds. Extra capacity can absorb delays, protect the last appointment or support another suitable stop once the assumptions are dependable.
Offer route days without silently changing appointments
When taking an inquiry, check whether its area fits a service day you can support. Give the customer an honest choice between the available day and any separately priced exception. A nearby customer is not automatically a good fit if the service, crew or timing is incompatible.
We currently serve [area] on [day/service window]. For [agreed scope], we can offer [price and frequency] on that route. Your visit will be [accurate arrival promise]. If you need a different day or a fixed appointment, let us know before booking so we can check availability.
For existing recurring work, agree a change rather than editing the series and hoping customers notice. Say whether one occurrence is moving or the ongoing schedule is changing. The rain-delay guide covers why that distinction matters when the week is disrupted.
Keep one revised plan visible to the office and crew. Notify people through their agreed channels, but do not make an old group text the only source for today's route. Record moved or cancelled visits clearly so planning does not erase the history needed for billing questions.
Review travel minutes, late arrivals, unplanned waits and actual service time after the week. Revenue per route hour can help compare like-for-like plans, but it is not profit: labor, vehicle use and other costs still need review. Use the costing guide before deciding an outlying customer is worth keeping or dropping.
Frequently asked questions
Should I always take the nearest customer next?
Not if it breaks an access window, equipment requirement or service promise. Geography is one constraint, not the whole plan.
Does a route map automatically optimize my business?
No. Review whether a tool actually optimizes routes or simply displays addresses. You still need reliable durations, customer constraints and crew capacity.
How many stops should a crew complete per day?
Work backward from measured durations and all-day capacity. A count without scope, travel and crew size does not describe a deliverable schedule.
How should I plan for a stop that takes longer than expected?
Keep some capacity for realistic variation and record the actual duration. If one stop repeatedly overruns, revise its estimate or move it to a day with enough room. Tell affected customers when their agreed window changes instead of compressing the remaining jobs into an impossible plan.