Landscaping business growth strategies

Calculate the Cost of Crew Waiting Time in Landscaping

June 01, 2026

The cost of crew downtime waiting on the owner is simple to calculate: minutes waited, times people on the crew, times your loaded labor cost per person-hour, added up across every wait. Log one normal week, multiply out to a season, and you will have a real dollar figure instead of a feeling. Then rank the fixes by how fast each one pays for itself.

Updated October 9, 2026

The waiting-cost formula

Use one formula and apply it the same way every time:

Waiting cost = (minutes waited ÷ 60) × people on the crew × loaded labor cost per person-hour

"Loaded" means wage plus payroll taxes, workers' comp, and benefits, the same rate you use in job costing. A fifteen-minute wait for a three-person crew is 0.75 person-hours, or $22.50 at $30 per person-hour. Small on its own, but it happens several times a day across every crew.

If you are still deciding whether you are the bottleneck at all, start with the signs a hands-on owner has become the bottleneck. This post is about the number.

Log one week of waits

For one normal week, have each crew leader record every time the crew stopped because they needed something from you:

  • Start and end time of the wait.

  • How many people were affected.

  • What decision or information they needed.

  • Whether they had other useful work they could do while waiting.

  • How it was resolved: phone call, text, or you driving out.

Only count time when the crew genuinely could not keep working. If they switched to edging while waiting, that is not lost time.

Example: one week of logged waits for three crews, at $30 per person-hour
DayCrew (people)MinutesPerson-hoursCostWaiting on
MonA (3)201.0$30OK to swap a plant variety
MonB (2)301.0$30Price for extra work the customer asked for
TueC (4)453.0$90Missing material; approval to buy locally
WedA (3)402.0$60Which beds to mulch first, scope unclear
ThuB (2)451.5$45Approval to rent a replacement mower
FriC (4)302.0$60Gate code and customer contact
Total21010.5$315

From one week to a full season

In this example, 10.5 person-hours a week cost $315. Over a 30-week season, that is 315 person-hours and $9,450 in paid labor that produced nothing.

Now look at it as capacity. If you bill labor at around $60 per person-hour, those 315 hours are about $18,900 of work your crews could have done. That is a capacity number, not guaranteed cash. Payroll may stay the same either way; what changes is how much work the same crews finish.

For a larger company, the math climbs fast. Five three-person crews each losing fifteen minutes a day over 200 working days is 250 crew-hours, or 750 person-hours. At $30 per person-hour, that is $22,500.

The log also shows ripple effects, like a late finish that pushes the next stop or Friday overtime. Track those separately with evidence. Waiting time also turns up inside labor overruns, so cross-check with the estimated versus actual labor-hour review.

Fixes ranked by payback

Group the waits by cause, then match each group to a fix. Rank the fixes by how quickly they pay back the time it takes to set them up.

Example: fixes for the week above, ranked by payback (setup time valued at $50 per hour, crew time at $30 per person-hour)
FixWaits it removesPerson-hours saved per weekWeekly valueSetup costPayback
Load list checked the night beforeTue missing material3.0$90$150 (3 hours)1.7 weeks
Job packet with scope, photos, access codes, customer contactWed scope, Fri gate code4.0$120$300 (6 hours)2.5 weeks
Written decision limits for crew leadersMon plant swap, Thu rental2.5$75$200 (4 hours)2.7 weeks
Change-order process for crewsMon extra work1.0$30$250 (5 hours)8.3 weeks

Every fix pays back well inside one season. Start at the top. Decision limits, such as "swap any plant of the same size and price" or "rent equipment up to $300 without calling," are covered in how to set decision boundaries for landscaping crews. The extra-work waits go away with a clear change-order process. For equipment, give crews a breakdown plan they can follow without you.

Document each handoff, with the outcome, the authority, and when you will review it, using the delegation handoff template. Then run the one-week log again a month later and compare.

Rules for an honest number

  • Count only real waiting, not time a crew spent on other useful work.

  • Use person-hours, not crew-hours, and state the crew size.

  • Use your actual loaded labor rate, the same one you use in job costing.

  • Keep paid-labor cost and lost-capacity value as two separate numbers.

  • Do not add assumed lost jobs or employee turnover as if they were measured losses.

A number you can defend is worth more than a big one.

For financial recordkeeping context, see the SBA business management resources. Apply consistent definitions with your accounting professional.

Frequently asked questions

How do I convert crew waiting into person-hours?

Multiply the elapsed waiting time in hours by the number of people affected. A 30-minute wait for a four-person crew is 2.0 person-hours. Add up all logged waits for the week, then multiply by your loaded labor cost.

Does eliminating waiting save the full calculated payroll cost?

Not necessarily. Payroll often stays the same; what you gain is capacity to finish more work with the same crews. Cash savings only show up if that capacity becomes billed work or reduces overtime.

What data should I collect before estimating the cost of crew downtime?

Record each wait's start and end time, the number of people affected, the decision needed, and whether other useful work was available. One normal week is enough to start. Use the same loaded labor rate you use in job costing.

Explore 7 Figure Landscape Network's business systems programs or book a strategy call to discuss the operating problem you want to work on. Learn about Jim Wertz and the network.

For the broader crew operations and delegation process, use How to Delegate Landscaping Work: A Practical Handoff Template as your starting guide, then return to the specific issue covered here.

Back to Blog