Route density is how much useful work you can schedule inside a compact geographic area. For a pressure-washing owner, the goal is not to draw the smallest service map possible. It is to reduce non-production time between jobs without accepting bad-fit work or automatically discounting nearby jobs.
A practical way to use route density is to compare whole workdays. Track completed revenue, onsite production time, between-job travel and other working time you deliberately include. Then compare similar days and ask whether tighter geography is actually releasing usable capacity.
Treat time saved as capacity first, not profit. A tighter route can create room for another job, an estimate, maintenance work or an earlier finish. It only changes job profit when your real labor, vehicle, travel or other cost assumptions also change.
Route density is different from route optimization
Route density asks a business question: how geographically compact is the work you have booked, and does that compactness improve the economics of the day?
Route optimization asks a routing question: given a set of stops, what order or assignment should make the route work better? Google Maps describes its Route Optimization API as a system that can generate route plans around objectives such as travel efficiency and constraints such as work hours and time windows, including field-service appointments. See Google Maps' Route Optimization overview.
You can have an optimized route that is still geographically scattered. You can also have a dense route with only a few nearby jobs that does not require routing software at all.
Measure a route day before trying to improve it
Start with a simple route-day record. For each completed workday, capture:
- Completed route revenue. Revenue from the jobs actually completed that day.
- Onsite production time. Time spent performing the work your customers bought.
- Between-job travel time. Time moving from one job location to the next.
- Other included working time. Only the job-day time you intentionally want in this comparison, such as a defined supply stop or another recurring route task.
- Optional travel inputs. Miles, tolls or other direct travel costs if you already track them reliably.
Then calculate two internal comparison measures:
Route hours = onsite production time + between-job travel time + other included working time
Revenue per route hour = completed route revenue ÷ route hours
You can also track a simple production-time share:
Production-time share = onsite production time ÷ route hours × 100
These are management measures, not pressure-washing industry benchmarks. Use them to compare your own similar days over time.
Worked example: the same three jobs on two different routes
This is a hypothetical example for showing the method. It is not a recommended pressure-washing price, service-area size, route target, labor rate or margin benchmark.
Suppose the same three jobs are each sold for $300. Total completed revenue is $900 and total onsite production time is 4.5 hours either way.
| Route-day input | Scattered day | Clustered day |
|---|---|---|
| Completed revenue | $900 | $900 |
| Onsite production time | 4.5 hours | 4.5 hours |
| Between-job travel / included non-production time | 2.0 hours | 0.75 hours |
| Total route hours | 6.5 hours | 5.25 hours |
| Revenue per route hour | $138.46 | $171.43 |
| Production-time share | 69.2% | 85.7% |
The clustered day releases 1.25 hours while completing the same hypothetical work and revenue. That is useful capacity. It is not automatically extra profit, because the example has not assigned a dollar cost to that time or assumed that another profitable job appears to fill it.
If your own records show that the tighter route also reduces a cost your pricing model actually includes, update that real input and rerun the economics. If not, keep the operational benefit separate from the financial claim.
What route density can change—and what it does not change automatically
Tighter geography may reduce some inputs, but only when your actual records support the change.
Inputs that may change
- between-job travel time;
- miles or direct vehicle cost you deliberately track;
- paid or valued working time spent moving between jobs;
- the amount of usable capacity left in the workday;
- how easily you can schedule a nearby estimate, callback or additional job.
Inputs that do not disappear because two customers are neighbors
- the actual onsite work required;
- property-specific complexity or access;
- job-specific materials or direct costs;
- quality-control requirements;
- the overhead your pricing model still needs to recover.
This is why a dense route is not a reason to slash prices across the board. Measure the operating difference first.
Route density and minimum charges solve different problems
A minimum charge protects the economics of mobilizing for a small job. Route density tells you whether the surrounding schedule makes that mobilization materially different.
For example, a small job on the opposite side of your service area may need to stand on its own economics. A small add-on beside another already-booked job may create a different incremental decision. That does not mean every nearby customer receives a discount; it means you can evaluate the actual additional time and cost instead of pretending every trip is identical.
Use How to Set a Pressure Washing Minimum Charge for the pricing-floor framework. Keep the route-density review focused on whether geography changes the inputs behind that floor.
A route-density decision tree for a distant or awkward job
- Does the job work on a standalone basis? Check the scope, minimum, labor, direct costs and overhead using your normal pricing process.
- Is the location already near booked work? If yes, quantify the actual incremental travel or time rather than assuming a generic savings amount.
- Could the job anchor a useful future cluster? Treat that as a marketing or scheduling opportunity, not guaranteed future revenue.
- Do you have real route data? If not, price the current job from standalone economics and start tracking.
- Has a repeated pattern emerged? Several comparable route days are stronger evidence for changing a standard assumption than one unusually convenient day.
If the answer is still uncertain, do not force a special travel fee or discount. Quote the work using the economics you can support.
Build denser routes without creating bad work
Route density is most useful when it helps you organize demand you actually want—not when it pressures you to take every lead inside a radius.
Use area-focused booking windows
When several customers are already near each other, offer sensible scheduling windows that keep nearby work together where customer needs allow. Do not promise an exact route before the jobs are confirmed.
Reactivate past customers near booked work
If you already have a job in an area, a small segment of relevant past customers nearby can be a better reactivation target than blasting the entire database. Use the Pressure Washing Customer Reactivation guide for the follow-up framework.
Use maintenance customers as route anchors only when the plan already makes sense
A recurring customer can make scheduling more predictable, but a maintenance plan should still stand on its own service need and per-visit economics. See Pressure Washing Maintenance Plans.
Look for repeat commercial stops that fit the route
Recurring commercial work can create planned route structure, but only when the contract itself is worthwhile. Use the recurring commercial contracts guide for that separate decision.
Do not turn route density into location-page spam
Operational geography and SEO geography are not the same thing. It can be useful to group customers, leads or schedules by service area internally. That does not justify creating dozens of thin city-name pages with essentially the same content.
Build route density through scheduling, customer history and genuine local demand—not by manufacturing duplicate search pages.
Run a weekly route scorecard
A simple weekly review can show whether geography is actually becoming more efficient. For each relevant workday, record:
- date;
- general route area or zone;
- completed job count;
- completed revenue;
- onsite production hours;
- between-job travel hours;
- other included working hours;
- miles or direct travel cost if you reliably track them;
- revenue per route hour;
- production-time share;
- notes explaining unusual delays, callbacks or exceptions.
Then compare like with like. A three-job residential day should not automatically be judged against a one-stop commercial project that occupies most of the day.
Use job costing to separate route problems from job problems
A route can be efficient while one job is badly estimated. It can also be scattered while every individual job performs exactly as expected.
Use Pressure Washing Job Costing to compare each completed job with its estimate. Use the route-day scorecard to analyze the time between those jobs. Keeping the two views separate makes the diagnosis cleaner.
When should route density change a quote?
Change a quote assumption only when geography changes a real input in your model.
Examples might include a measurable reduction in travel time, direct travel cost or working time that your pricing system actually accounts for. If those inputs do not change, “the jobs are close together” by itself is not a mathematical reason to lower the price.
When route software becomes useful
A calendar and map may be enough when one owner has a small number of daily stops. Dedicated routing or field-service tools can become more useful when you are balancing more appointments, multiple crews, time windows or frequent schedule changes.
The software decision should follow the operating problem. If your real problem is that the booked jobs are spread across a huge area, optimizing the order of those stops may help—but it cannot make distant customers physically closer together.
Frequently asked questions
Should I discount pressure-washing jobs that are close together?
Not automatically. Compare the actual incremental time and cost first. If the second job genuinely changes an input in your model, you can decide how to price it. Proximity alone is not a universal discount rule.
What is a good route-density percentage?
There is no universal SGL target for pressure-washing businesses. Track your own production-time share and route-hour economics across comparable days, then improve from your real baseline rather than borrowing an unrelated benchmark.
How large should my pressure-washing service area be?
There is no universal radius. Your workable area depends on job economics, customer demand, travel time, capacity and the type of work you want. Use actual route data and your minimum-charge logic to decide where standalone jobs stop making sense.
Is route density the same as route optimization?
No. Route density is about how geographically compact the booked work is and whether that compactness changes the workday. Route optimization is about assigning or sequencing the stops you already have.
Do I need routing software?
Not necessarily. Start by measuring the problem. Software can help when stop count, crew count or scheduling constraints become complex; a simple map, calendar and disciplined route-day record can be enough for a smaller operation.
Make geography earn its place in the decision
The useful question is not “How tight can I make the map?” It is “Does this route release time or reduce a real cost without weakening the jobs I accept?”
Measure whole route days, compare similar schedules and let repeated evidence—not a copied mileage fee or arbitrary discount—change your assumptions.
If you want a repeatable system for using customer history, reactivation and local marketing to build more intentional clusters, the Pressure Washing Growth OS is the natural next step.