Route density and travel time in residential lawn maintenance

Measure a full route, including its first and last legs

Route density is useful only when it reduces the crew time needed to complete the promised work. Count the drive from the yard to the first property, every move between properties, and the return from the last property. Allocate those end legs across the day’s completed visits. A low average between neighbors can hide a long drive into the neighborhood. Track route miles as a separate measure: minutes govern capacity, while distance, vehicle use and equipment use help test fuel and maintenance costs.

Time-stamp departure, arrival, start of service, completion and return. Record unloading, gates, parking, trimming, clipping handling and loading once, in a clearly named bucket. Here, visit-specific handling belongs in on-site time; the daily allowance covers common support activities. If your real scope includes off-site disposal or a supply trip, include it in the relevant visit or route allocation rather than omitting it from both.

The linked case pays one employee and a working owner. Its 40.0 crew clock-hours are 80.0 person-hours for the two people together; they still share one vehicle and one route calendar. Federal DOL guidance counts an employee’s travel between job sites during the workday as hours worked. Ordinary commuting is a different category. Employee travel-time scope

Start with the hours both travel and service consume

The case’s 90.0% routing fraction leaves 36.0 route hours per week. It already deducts 48 minutes of common support per assumed working day. Do not deduct that allowance again for every stop. Actual loading, paid breaks, maintenance and administration may exceed it; validate a roster that identifies which person performs each task. A statutory unpaid meal, if applicable, would need its own schedule treatment.

Each retained visit uses 48 minutes on site, plus 12 minutes of allocated travel. This is a substantive residential-maintenance visit, not an observed price or duration for a quick mow. The retained $185 receipt and $158.45 contribution remain case assumptions and model outputs. Retained case scope

Compare the same service on three route patterns

The calculation is route hours divided by on-site plus allocated travel hours per visit. Average monthly capacity uses the same 52-week, 12-month convention as the model. Dense and dispersed travel times are new article hypotheses, not measured industry averages. They change a capacity worksheet only. The original demand, fuel allowance, payroll and all sixty monthly outputs are preserved.

Capacity is an upper bound. If signed work remains below it, a shorter drive first releases time; it does not automatically create sales. To assess a real improvement, compare equivalent service scopes and traffic periods. Removing an unusually large lawn from a route can improve the average time without proving that routing itself became better.

Book whole visits inside a real day

The base schedule leaves 0.2 route hours after its booked visits, separately from common support time. The other two choices consume the entire routing allocation. A continuous monthly visit-equivalent can be useful for a financial forecast, but it is not permission to promise a fraction of an extra appointment each day. Check whole visits, gate restrictions and return time before selling the next stop.

The dense schedule has potential additional daily contribution of $158.45 against the base choice, conditional on another customer buying and receiving the same service. That amount is before the already paid roster, overhead, debt and collections. It is not a payroll saving: neither employee nor owner compensation disappears when driving becomes shorter. Fuel cost is held constant for this comparison; time saved is not evidence of a measured fuel saving.

Test a remote customer against the hours it displaces

A distant visit can look attractive when evaluated only by its receipt. At the retained price it earns $158.45 of contribution, but its longer route slot produces $132.04 per route hour, compared with $158.45 under the base allocation. When the route is full, the relevant question is which completed work the new commitment would replace.

The alternative bid uses the case’s 3.0% payment fee and unchanged material and fuel dollars. It is a comparison, not a recommended neighborhood surcharge or a local quotation. Re-estimate access, mileage, disposal and the service itself before quoting. A higher bid does not create another hour in an already full day. A customer willing to join an existing zone day may be a better fit than one requiring a separate fixed-time detour.

Grow through zone days and test the whole route change

Assign a neighborhood to a repeatable service window and offer nearby prospects that window. Keep a waitlist by zone and service scope. Compare adding a prospect between two existing stops with adding it at the end of the day; the change in the complete route matters more than distance from one convenient neighbor. Record the customer’s access constraints before promising a date.

For a new zone, set a launch condition based on confirmed work and a timed route, rather than assuming future neighbors will sign. If a canceled account was the bridge between two clusters, rebuild the route before accepting its apparent replacement. Review repeat visits over the season, because leaf handling and overgrowth can change service time even when addresses stay the same.

Use a flexible window for routine mowing where the agreement permits it, with a clear notification process for changes. Keep fixed appointments for tasks that actually require customer presence or access. A routing tool can propose an order, but the dispatcher must check trailer parking, turnaround, gates and whether the proposed sequence fits the paid shift.

Keep weather recovery and mowing quality in the promise

A route with no spare routing time is a capacity ceiling, not a dependable weekly promise. Hold recovery space based on observed delays and the service commitments you have sold. When a day is lost, move a compact group together where feasible; spreading isolated make-up visits across the next routes can recreate the travel problem.

Maryland Extension advises mowing according to grass growth, avoiding wet or dormant stressed turf, and removing no more than one-third of the blade at a cut. These are mowing principles; that source is not a national weekly frequency standard. The operating implication is to inspect conditions and notify customers when timing changes, rather than rush every missed visit into a wet day or cut excessively to recover the schedule. Mowing conditions and scope

Write down how an overgrown return visit changes the allotted time and whether a separate scope must be agreed. Check mower readiness before dispatch. If a recovery plan needs overtime or another crew, price and schedule that change explicitly; do not pretend it fits the original fixed roster.

Use a dispatch record to decide which account to renew

Review the register at renewal time. Keep customers whose scope, access and window fit a repeatable zone; renegotiate or decline those whose constraints consume disproportionate calendar time. Keep customer names and precise addresses in the private dispatch system, not in a public case study.

The landscaping unit-economics guide connects visit contribution to the retained monthly capacity. The profitability guide carries fixed payroll, owner pay and debt through the seasonal cash ledger. Use measured route changes as inputs to a future checked revision, rather than treating this sensitivity table as a new published forecast.