Pressure Washing Route Density, Explained

Route density is not profit and it is not a single universal formula. It describes how tightly compatible work is grouped. Revenue per mile can be a useful proxy, but collected contribution per crew hour, drive minutes per completed stop, miles per stop, and schedule reliability reveal different parts of the decision. A dense calendar with underpriced or callback-heavy jobs can still lose money.

This guide shows how to separate the travel effect from price, production, collection, and risk. If you want the scheduling tactics, see how to reduce windshield time; for the full operating system, see how to route pressure washing jobs.

One note before the math starts: every dollar figure below is an illustrative example with round numbers. Swap in your own loaded cost, tickets, and drive times - the math is the point, not the digits.

What is route density?

Density can be expressed as completed stops, collected revenue, or contribution against driving distance or time. Picture the same five compatible jobs two ways. If all else truly stays equal, clustering can let one inbound leg serve several stops and reduce allocated travel. In practice, verify access windows, crew fit, setup, production time, payment, and callbacks before calling the schedules equivalent.

The reason it matters is that drive time is a real, loaded cost - wages, burden, and per-hour vehicle cost for everyone in the truck - that the customer never sees on the quote. Density is simply how thinly you spread that hidden cost.

Density reduces repeated travel only when the grouped jobs are real, compatible, completed, and collected.

Crew time includes travel, setup, production, documentation, breaks, disposal, fueling, and administration—not only wand or windshield hours. Travel is necessary delivery time even when it is not separately invoiced. Clustering can release capacity, but only measured schedules show whether the released time becomes productive work, a shorter day, or an unusable gap.

The tricky part is that low density never feels like an emergency. Nobody sends you a bill labeled "scatter." It just shows up as symptoms:

• You drive past a house you washed last month on the way to today’s job across town.
• Your crew clocks eight hours but only bills five of them.
• Fuel spend creeps up while revenue stays flat.
• Two jobs land in the same neighborhood in the same week - on different days.

Those symptoms justify a route audit; they do not prove density is the sole cause. Price, production estimates, dispatch, weather, equipment, crew readiness, or job mix may also explain them.

When does a nearby fill-in improve contribution?

A compatible job near a confirmed stop can have lower incremental travel than an isolated visit. The anchor does not make the second job free: the fill-in still uses qualification, quoting, schedule slack, travel between properties, setup, loaded labor, product, water, equipment, payment, proof, cleanup, callback allowance, and opportunity cost. It improves the day only when its expected collected contribution and operational fit beat the next-best use of that capacity.

Watch the same $360 ticket as density changes. Figures are illustrative - drop in your own loaded cost:

In the illustration, allocated drive cost differs by $40.33. That is a potential cost advantage, not an eleven-point profit guarantee. Production time, selling cost, payment, callbacks, and the effect on the existing schedule can reverse the comparison. A lower-priced nearby job is justified only when its complete expected contribution clears the floor.

Here is exactly where those numbers come from, so you can rebuild the table with your own costs. The example assumes a loaded crew cost of $55 per hour - wages, payroll burden, and the truck’s hourly cost combined:

1. Isolated job: 50-minute round trip. 50 ÷ 60 × $55 = $45.83 in drive cost carried by one ticket.
2. Zone day: the same 50-minute round trip now serves five stops. $45.83 ÷ 5 = $9.17 per job.
3. Fill-in: six minutes door to door. 6 ÷ 60 × $55 = $5.50.

Multiple nearby jobs can share part of the route, but each one also consumes capacity and adds uncertainty. A $360 anchor plus two $200 jobs is $760 of booked revenue only if all three scopes are accepted; it becomes useful economic evidence after completion, collection, and actual-cost reconciliation.

Second, price a requested return honestly. A different surface may require inspection, documentation, product, weather, crew skill, or customer presence that makes same-day work inappropriate. Offer the earliest safe compatible window and include its travel; never use route efficiency to rush consent or combine work the operating plan has not approved.

How do I calculate route density?

Use several complementary measures; no single one proves profit.

Revenue density = Collected revenue ÷ miles (or drive-hours)
Stop density = Completed stops ÷ drive-hours
Drive cost per job = drive-hours × loaded crew hourly cost ÷ completed jobs
Contribution productivity = Collected contribution ÷ total crew-hours

Track them across comparable periods and record cancellations, job mix, price, production, collection, and callbacks. Rising revenue density with falling drive cost is encouraging only if contribution productivity and service quality hold.

The table is directional, not a profit statement. To compare the weeks, hold job mix and production assumptions constant, then calculate actual collected contribution and total crew-hours.

What does a full worked week look like?

Here is the same math with round, illustrative numbers filled all the way in. Say a crew completes 18 jobs for $6,300 in a week, at a loaded cost of $55 per hour.

Booked in call order, the week takes 14 drive-hours. Density is $6,300 ÷ 14 = $450 of revenue per drive-hour. Total drive cost is 14 × $55 = $770 - about $43 per job.

Booked into zones, the same 18 jobs take 4.5 drive-hours. Density jumps to $6,300 ÷ 4.5 = $1,400 per drive-hour, and drive cost falls to 4.5 × $55 = $247.50 - about $14 per job.

Under those intentionally controlled assumptions, estimated drive cost falls by $522.50 for the week. Do not annualize one modeled week as savings. Validate whether the same jobs could actually move and whether the alternative changed overtime, cancellations, production, or collection.

How do you track it in ten minutes a week?

You don’t need software or a dashboard to start. You need Friday and a notepad:

1. Pull the week’s completed revenue. Not booked - completed.
2. Add up drive minutes between stops from your maps timeline, a trip log, or the odometer.
3. Divide revenue by drive-hours. Write the number down.
4. Divide total drive cost (drive-hours × loaded hourly cost) by the number of jobs. Write that down too.
5. Compare both numbers with last week. Direction matters more than precision.
6. Inspect the weakest day and identify the actual contributors: one outlier, several short legs, access windows, reschedules, job mix, or bad estimates.
7. Test one change next week without breaking a customer commitment: offer a compatible date, resize a zone, adjust the floor, or decline an unserviceable outlier.

The one input that has to be honest is your loaded hourly cost. If you’re guessing at it, the whole calculation wobbles. A simple spreadsheet works; so does WashRoute Pro’s Costbook for storing owner-entered labor, drive-time, and chemical assumptions used in quoting. It does not capture actual costs per job, so the owner still reconciles and updates those inputs.

What counts as a good number? There is no industry benchmark worth trusting, because ticket size, territory, and traffic make raw comparisons between businesses meaningless. Compare you against you, week over week. If you track wider business numbers already, density slots in beside them - see the KPIs worth tracking for where it fits.

How do I build route density on purpose?

Density can be designed, but the calendar must still respect customer commitments, weather, crew qualifications, equipment, access, service duration, and urgency. Use three controlled habits.

Zone the area, anchor the day

Split the service area into a small number of operational zones derived from actual drive-time and completed-work data. Offer compatible windows near confirmed work, while keeping enough slack for weather, variance, breaks, and customer requirements. There is no universal zone count or diameter.

If you’ve never drawn zones, here is the whole exercise in five steps:

1. Put every job from the last 90 days on one map. Screenshots and pins are fine.
2. Identify recurring clusters, outliers, access windows, traffic barriers, and job types that should or should not share a crew day.
3. Draw a first set of zones around measured drive time and capacity; record the assumptions instead of forcing a fixed count or radius.
4. Give each zone a default weekday. Two light zones can share a day until they fill out.
5. From now on, offer the zone’s day first on every quote: "We’re in your area Tuesday - I can get you on that run."

Treat the map as a test. Review actual drive and service results regularly and revise boundaries when traffic, customer mix, or crew capacity changes.

Sell into the cluster

Nearby demand can reduce future travel, but geographic proximity does not create permission to contact or prove profitability. Test lawful, attributed local outreach; respect solicitation and messaging rules; use customer identity or property proof only with permission; and count owner time. WashRoute Pro’s RouteFill sorts mapped jobs from accepted quotes whose customers explicitly chose flexible timing by straight-line distance from a scheduled job; it does not surface past customers or arbitrary neighboring properties, contact anyone, or confirm an anchor automatically. A spreadsheet, map, or route-optimization tool can support the same owner-led decision.

If door hangers are permitted, run a small coded batch under a documented safety and distribution process. Never leave active equipment or a site unattended, trespass, use mailboxes, or imply a neighbor endorsement without permission. Count design, printing, walking, and response time. These door hanger templates cover the layout and controls.

A visible result may prompt a question. Respond when approached, qualify the scope, and offer an honest compatible window. Do not interrupt the job or solicit where rules prohibit it.

Protect the day you built

Offer the most route-compatible truthful window first: “We currently have an opening in your area Tuesday.” Do not imply the customer will accept it or hide a material schedule condition. If their access, urgency, or presence needs a different date, compare the full cost and capacity effect before confirming.

When a customer cannot use the proposed window, calculate the special trip, service promise, and opportunity cost. Offer another honest window or decline when the work no longer clears the floor. Do not claim how many jobs the choice will lose without your own data.

When weather or another stop condition hits, reassess every affected commitment. Moving a whole group may preserve density, but customer availability, surface conditions, crew hours, and promised priority can require a different recovery. Confirm each change; never move appointments silently. The same constraint-based approach supports crew scheduling.

What can a dense-week model show?

It can show the effect of route assumptions while holding other inputs constant. It cannot promise half the driving or a self-filling calendar. Here is an illustrative one-truck model.

Monday is the north zone: an anchor house wash at 8:30, two driveways booked onto the same street, and a fill-in from last Monday’s door hangers. Four jobs, eleven miles. Tuesday is the southeast zone with three stops and twenty door hangers on the way out. Wednesday holds the week’s one far-flung commercial job - priced with its full drive included, so it carries its own cost. Thursday is the west zone, where a past customer two doors from the anchor said yes to a "we’re on your street Thursday" text. Friday cleans up two small north-zone jobs, and the truck is home by 1:00.

Compare that with the same jobs booked in call order:

Under the modeled assumptions, estimated drive cost differs by $330 and six crew-hours are released. The model does not prove those hours can sell, that outreach will create fill-ins, or that all appointments can move. Reconcile an actual week before treating the difference as savings.

How do season and region change route density?

Density is local math. Build zones from actual drive times, traffic, bridge or road constraints, parking, crew and equipment bases, service duration, weather loss, daylight, freeze or heat risk, drought and runoff restrictions, customer access windows, and demand history. A mile in a dense city, a suburb, and a rural county can represent very different time and cost.

Review zones when a material input changes—not on a universal seasonal script. Sparse periods may justify fewer service days or wider zones, but only when the consolidated schedule still meets commitments and produces better contribution. Use property-specific service need and consent for rebooking; geography and climate do not create an automatic annual cadence. How often to rebook customers covers that decision.

How does density connect to price?

Expected drive time belongs in the price floor. A compatible nearby job can lower its allocated or incremental travel input, but the floor changes only after every other expected cost and capacity effect is updated. Density does not lower product, production, selling, payment, callback, or overhead cost automatically.

Illustrative math: if expected drive cost falls from $45 to $9 while every other input truly stays equal, expected direct cost falls $36. Under a 50% gross-margin planning formula, that changes the calculated floor by $72. It does not guarantee actual margin; collection, production variance, callbacks, and the accuracy of every input still control the result.

You can preserve the standard price, test a truthful route-window offer, or reserve the capacity. If you discount, define eligibility, scope, real comparison price, end condition, and effect on contribution. Never assume proximity earns a discount or that a lower number will win the block.

What are the most common route density mistakes?

The most common mistakes are booking in call order, saying yes to any day, and measuring only revenue. All of them are quiet, and all of them are fixable this month:

1. Booking without a travel check. The next open slot can create avoidable travel. Offer the best truthful compatible window first, then respect the customer's constraints.
2. Showing an unconstrained calendar. Offer a small set of real windows the operation can fulfill instead of implying every open cell is equally serviceable.
3. Chasing the far-away big job without pricing the drive. A $700 job 45 minutes out can net less than a $400 job in your zone once the round trip and the lost fill-ins are counted. Take it only if it clears the floor with the drive included.
4. Calling local outreach free. Distribution has print, labor, permission, safety, and compliance cost. Attribute a small test before repeating it.
5. Ignoring compatible-date opportunities. Ask whether nearby work can share a day, but do not move an accepted appointment without agreement.
6. Rescheduling without rebuilding constraints. Re-evaluate weather, customer availability, crew hours, equipment, and route cost before confirming each change.
7. Measuring only revenue. Eighteen jobs looks the same in the bank whether the truck drove 110 miles or 260 - right up until fuel and payroll clear. Revenue per drive-hour catches what the top line hides.
8. Drawing zones once and never again. Review them on a stated schedule and after material changes in traffic, service mix, crew base, demand, or customer commitments.

Read a representative period against this list. Some fixes are quoting language; others require pricing, service-area, crew, or contract changes. Measure the result rather than assuming the rule worked.

Does software build density for you?

No - habits build density, and software just makes the habits cheaper to keep. The zone map, the "we’re in your area Tuesday" line, and the five-doors habit all work from a paper map and a text thread.

The right tool does remove friction, though. General field-service platforms like Jobber, Housecall Pro, and Service Autopilot are capable systems that serve many home-service trades, and some include route optimization that sequences booked stops. WashRoute Pro takes a different, owner-controlled approach: its scheduler persists the stop order and dispatch priority the owner chooses, and RouteFill sorts mapped jobs from accepted quotes whose customers explicitly chose flexible timing by straight-line distance from the scheduled anchor. It does not calculate a shortest road route, surface past customers or arbitrary neighboring properties, contact anyone, or confirm a fill-in automatically. Weigh both kinds of tools against your week; if you want to test the owner-led candidate workflow, there’s a 14-day free trial with no credit card and nothing charged automatically.

Whatever you choose, keep the Friday numbers. A tool you never check against revenue per drive-hour is just a prettier calendar.

The one-paragraph version

Route density describes how tightly compatible completed work is grouped. Track stops and collected revenue per drive hour or mile, but pair them with collected contribution per total crew-hour so low prices, long production, callbacks, and uncollected work stay visible. A nearby fill-in may reduce incremental travel, yet still needs a full cost and capacity check. Offer truthful compatible windows, keep customer commitments, test lawful local demand, and reconcile actual results before changing zones or prices.

Connect density to an actual booking decision

At the start of the week, choose an anchor job and define the territory you can serve without creating a late day. Then review accepted work that is genuinely flexible, not merely nearby on a map. Ask three questions: can the crew perform the sold scope in the open time, did the customer authorize flexible scheduling, and does the added stop still clear the price floor after real road time?

Measure density with paid production hours, drive minutes, average ticket, and late or rescheduled jobs. A full map is not a dense route if the crew spends the day crossing town or waiting on access. Keep the reason for accepting or declining a candidate; that history becomes a better territory rule than a colorful map.

RouteFill in WashRoute Pro sorts mapped jobs from accepted quotes whose customers chose flexible timing by straight-line distance within 15 miles of a selected scheduled job. The owner still checks road conditions, service time, price, and the exact appointment with the customer. It is a screening aid for contribution—not automatic route navigation or booking.

Use three density measures, not one

“Jobs per day” can improve while route quality gets worse. Track:

• Geographic density: average or median road travel between stops inside the route.
• Economic density: revenue or amount left after recorded job costs per route hour.
• Operational density: paid production time as a share of paid crew time.

A day of four tiny stops may look geographically dense but produce weak economics after four setups. A two-stop commercial day may be economically excellent even with fewer pins.

A route-day comparison

Illustrative numbers:

The dense day gained 1.5 production hours without extending payroll. The exact revenue effect depends on the work available and its margin; density creates capacity, not guaranteed demand.

Build a density ladder

1. Define a core territory small enough to recognize repeat patterns.
2. Create zone days and offer those days during booking.
3. Ask for timing flexibility clearly and record only explicit approval.
4. Market around booked work with permission-safe proof, neighbor outreach, or existing-customer follow-up.
5. Review accepted unscheduled work when a real gap appears.
6. Prune chronic outliers by raising the trip minimum, changing the service day, or referring them out.

Know when density is not worth it

Do not force a nearby job into a day when the crew lacks the equipment, the service duration breaks later promises, the surface or weather does not fit, the customer has not confirmed, or the job value fails the floor. Proximity is one constraint, not the decision.

WashRoute Pro can help review certain accepted flexible jobs near a scheduled anchor and keep the sold scope with the crew workflow. It does not measure true road-route density automatically or optimize a road route. Track the actual drive minutes and production share from completed days; those are the business signals that matter.

Build a neighborhood flywheel around completed work

The safest anchor for route density is a real booked job, not a speculative map full of leads. With the customer's permission, use the completed result to contact nearby existing customers, distribute truthful neighborhood material, or offer two clear dates for similar work in the same zone.

Track the chain from anchor job to surrounding revenue. Record how the neighbor heard about the company, distance from the anchor, quote date, booked date, service, price, and actual drive time. This distinguishes density created by reputation from random jobs that merely share a ZIP code.

Use a trip-minimum ladder rather than rejecting every outlier. A remote customer can accept a higher standalone minimum, choose a designated zone day, add enough scope to make the trip work, or wait for another nearby job. Present the choices plainly; do not invent a hidden “distance fee” after the quote.

Review density by day and territory. Useful measures include median travel between stops, production hours as a share of paid hours, revenue after recorded direct job costs per route day, on-time starts, and reschedules. One tight Thursday should not hide four scattered days.

Density is a compounding advantage when it shortens travel, creates visible local proof, increases referrals, and makes future booking choices easier. It becomes a trap when the owner accepts low-value work merely because the pin is close. Preserve the price floor, crew fit, customer confirmation, and service standard. Nearby is an advantage only after the job is worth doing.