How to Allocate Lawn-Care Overhead Per Visit

Decide what belongs in overhead

Insurance does not arrive as a neat charge attached to Tuesday's fourth lawn. Neither do software, storage or administration. An overhead pool groups the indirect costs that the defined work needs to support.

Start with your records. Potential categories include business insurance and licences, software and phone service, storage, accounting and administration, and fixed vehicle or equipment ownership costs. Include only the relevant business portion and write down what each allowance covers.

Keep costs that you already assign directly to a visit outside that pool. If a vehicle allowance includes fuel, insurance and maintenance, do not also put those same amounts in overhead. Fixed versus variable and direct versus indirect describe different things; a fixed cost can sometimes be traced directly to particular work.

BDC's costing guidance distinguishes traceable direct costs from indirect costs that need allocation, and recommends relating allocation to resource use. Your category map should explain the chosen method, not claim a universal accounting treatment. Use an appropriate accountant for bookkeeping or tax decisions.

Choose a denominator you can defend

The numerator is your defined cost pool. The denominator is the relevant work expected to carry it. Use realistic visits or usable route hours for the same planning period, not every hour theoretically available on the calendar.

Document the active season, holidays, weather allowance, maintenance and unsold capacity behind the workload estimate. Missing information is not zero; a zero or negative workload denominator cannot produce a valid allocation.

Match scope as well as dates. If several routes or service lines share the overhead, allocate it across their combined relevant workload or document a split into separate pools. Do not assign the entire annual pool to every route. Different frequencies need their actual planned visit counts, not just a count of customers.

Use a visit-based allocation

This method gives every included visit the same share. It is straightforward to review when visits consume broadly similar resources.

Example: $9,000 ÷ 1,200 annual visits = $7.50 per visit

Check it backwards: $7.50 × 1,200 visits = $9,000. Keep the source cost records, the reason for the visit count and the date beside this calculation.

The limitation is visible: a 20-minute visit and a 70-minute visit receive the same allowance. Those durations are examples, not typical visit lengths. If differences in time describe resource use better, consider the route-hour method below; neither method is universally right.

For this example, the free one-stop calculator's Overhead allocated to stop field takes 7.50 dollars per visit. Calculate the allocation in your own records first. The tool does not build an annual cost pool or track its recovery.

Use a route-hour allocation

Use elapsed service, setup and allocated driving time consistently in both the annual denominator and each stop. Include each stop's share of outward, between-stop and return driving once. Keep more detailed observations in your own records.

Overhead per route hour = annual overhead pool ÷ realistic usable route hours

Overhead per visit = overhead per route hour × allocated route hours for that visit

Route hours are not automatically person-hours. In an illustrative two-person crew working together for 45 minutes, elapsed time is 0.75 route hour while total labor is 1.5 person-hours. Do not multiply an elapsed-hour overhead allowance by crew size. If multiple crews share a pool, document a consistent crew-route-hour denominator that counts their separate route activity.

The free route calculator accepts Overhead per route hour: enter 10 for this example. The one-stop calculator accepts dollars per visit: enter 7.50 after the conversion, not 10. These are two ways to apply the same pool, not two allowances to add together.

The one-stop tool models one owner's field-pay allowance. The route tool applies a combined field-pay cost to elapsed route hours and uses average stop inputs, not saved individual properties. Keep mixed crew arrangements or materially different stops separate where an average would conceal them.

Prevent double counting

For each amount, identify its source, period, allocation and one place in the model. Check these common overlaps:

• Vehicle use: fuel, insurance or maintenance included in both a direct vehicle allowance and overhead.
• Equipment ownership: the same cost represented by depreciation, replacement and a wear allowance. These can describe different things; do not stack overlapping amounts without reconciling what each covers.
• Payment processing: fixed or percentage fees entered in their dedicated calculator fields and again in direct cost or overhead. Allocate a flat transaction fee over the visits that payment covers; use the effective percentage on modeled pre-tax revenue.
• Owner time: the same hour included in field pay and an administration allowance. Separate non-route administration from service, setup and driving, and avoid also treating the same pay allowance as an extra profit cost.

Enter zero only after checking that a cost does not apply or is deliberately covered elsewhere. An unknown statement or missing record is not evidence of zero cost. The cost-based pricing method shows how the distinct inputs fit together.

Reconcile the allocation with annual cost

Multiply the chosen allowance back across the matching planned workload. The examples reconcile as $7.50 × 1,200 visits = $9,000, or $10 × 900 route hours = $9,000. For a varied route, sum each stop's allocated allowance multiplied by its planned visits. Retain full precision in the working calculation and document any final rounding difference.

This checks the plan's arithmetic. It does not prove that visits happened, invoices were collected or actual bills were recovered. Compare the underlying pool and actual relevant workload with your assumptions during the year.

If the same $9,000 pool must be carried by 900 visits instead of 1,200, the revised illustrative allowance is $10 per visit. Changing Planned visits per season in the one-stop tool does not make that update for you: it scales the seasonal result, not the entered per-visit overhead. Recalculate externally, then update the overhead field deliberately.

A shorter route can reduce allocated time at an unchanged hourly allowance without reducing fixed bills. The route-density example explains that distinction. Recheck the whole allocation if workload assumptions change; a lower modeled floor is not an instruction to lower a customer's price.

Keep the old pool, denominator and result beside the revision, with its evidence and review date. Use the annual route-audit workflow to connect the allocation with time, visit counts and the next operating decision. No allocation predicts customer acceptance or guarantees earnings.