another idle-time eater. The estimate is upstream of the route. Sloppy estimat- ing shows up as windshield time three weeks later.
WHAT TOP-PERFORMING CREWS DO DIFFERENTLY
When I look at the operators who have squeezed the drive-time number down into the 1.0-to-1.5-hour range per crew day, a few practices show up consis- tently: •They build routes geographically tight, even at the cost of waiting a day to schedule a job. A job that “could fit Wednesday” gets pushed to Friday if Friday is already routing through that ZIP code. •They have one person whose job is the dispatch board, full-time, during peak season. Not the owner. Not the office manager doing it on the side. One person, focused, with authority to move crews. •They send automated ETA noti- fications when the previous job closes out. Not the morning. Not the night before. The moment the previous truck closes out. •They treat the foreman’s phone as a dispatch endpoint, not a communication channel. The next address shows up. The job notes show up. The customer’s gate code shows up. No calls back to the office to “ask what’s next.” •They review GPS playback week- ly. Not to police the crew. To find the patterns: where the dead miles are, which customers consistently cause idle time, which yards-to-first- stop routes are always 20 minutes longer than they should be. According to contractors in landscape design-build, project profitability swings hardest on labor capture accuracy. Crews that clock in and out by job code rather than by day consistently surface margin issues earlier in the season. The same pattern holds in tree care. If you cannot see which jobs ate the labor, you cannot see which routes ate the day.
Route density matters because every minute of windshield time is a minute a crew is not producing revenue.
labor. Every one of them comes direct- ly out of margin. As ArboStar puts it, route density matters because every minute of windshield time is a minute a crew is not producing revenue. THE ESTIMATE QUALITY PROBLEM THAT DRIVES DRIVE TIME Here is a connection I did not see for years and now see everywhere: bad es- timates cause drive time. When a job is bid sloppily, the crew shows up to find the work is bigger than what’s on the work order. They either grind through it and blow the rest of the day, or they pack up and come back. Either path adds drive time to the week. Arborists pricing tree removal jobs see fewer scope disputes when estimates are built with itemized line items and photos rather than a single lump-sum number, particularly on jobs over a few thousand dollars. Those photo-and-line- item estimates also reduce the “Wait, that’s not what I thought we were pay- ing for” conversation on-site, which is
point where manual coordination can no longer keep pace with operational complexity. The real value of automation is not that software creates a better schedule on Monday morning. It is that software can continuously rebuild the schedule on Monday afternoon. When a chipper breaks down, a climber calls in sick, a storm emergency appears, or a job finishes two hours ahead of plan, the system can reshuffle routes, rebalance workloads, and account for travel time far faster than any dispatcher working from spreadsheets and phone calls. This is where profitability quietly lives. Most tree care businesses do not lose money because crews cannot cut wood efficiently. They lose money because trucks cross paths on opposite sides of town, crews wait for equipment that was sent to another site, or an entire af- ternoon disappears into what dispatch- ers politely call “adjustments.”
Every one of those adjustments is paid
54 | Summer 2026 ArborTIMES ™
Made with FlippingBook - professional solution for displaying marketing and sales documents online