Your crew is probably not the leak. When crews themselves are asked what wastes their day, the top answers are hunting for tools and materials, waiting on decisions, and the owner walking on site. Measure one honest week in six buckets before you buy a tracking app, because the two largest leaks in most small shops are things you control from the office.
Ask the crew and you are on the list
In November 2025 someone posted a simple question to r/Construction: what is the one thing that slows productivity down the most on your site? It drew 161 comments. The ranking is worth reading carefully, because it is the opposite of what most owners assume.
The top answer, with 309 upvotes, was four words: "Having to hunt for materials/tools."
Second, with 136 upvotes: "The owner. If he gets involved everything gets fucked up or forgotten about."
Third, with 119: a complaint about a coworker with 24 years of experience who "can't do a damn thing without going to the truck 56 times an hour."
Fourth, with 91, was constant design changes. Fifth, at 69 upvotes, was a longer answer about material handling and staging, which ended on the line that unrealistic timelines and "the perception that all the work can be performed at once on top of each other makes things slower than if they were properly scheduled and layered."
Read that list again. Of the top five answers from the people actually swinging the hammer, exactly one is about a person being slow, and even that one is really about van organisation. The rest are staging, sequencing, and decisions. Those are office outputs. If you went looking for this article because you suspect your guys are milking the clock, the odds say the clock is fine and the dispatch is not.
Watch out
The second most upvoted answer in that thread was the owner. Before you audit the crew, be honest about how many times last week you walked on site and changed the plan mid task.
What a normal crew day actually looks like
Here is the benchmark that reframes everything. Field service platform Serfy, reporting across more than 5,000 companies and 2.4 million completed tasks, says teams typically find their wrench time sits at 30 to 40 percent when they measure it for the first time. That is about three hours of an eight hour shift with tools actually in hand.
Construction research lands in the same band. Lean Construction Blog's review of direct work studies puts the average direct work rate at 43.6 percent, with a large standard deviation of plus or minus 16.5 percent, and 70 percent of the sample falling between 24 and 58 percent. Kwant.ai's productivity breakdown cites the same 30 to 40 percent range as typical tool time, with best in class projects reaching 55 to 60 percent.
So if you run a stopwatch on your crew tomorrow and get 38 percent, you have not caught anyone. You have simply measured what a normal, unoptimised day looks like in this industry. The gap between 38 percent and 55 percent is the prize, and it is a systems prize.
The macro picture backs this up. Kwant.ai cites McKinsey's finding that global construction productivity has grown roughly 1 percent a year over the past two decades while manufacturing grew at nearly 3.6 percent, and Dodge Data and Analytics research finding that 61 percent of projects suffer productivity related delays, with labour inefficiency accounting for 20 to 30 percent of wasted project budget. An industry does not fall that far behind manufacturing because its workers are lazier. It falls behind because the work arrives at the worker badly.
The six leaks, ranked by what they cost a small shop
| Leak | What it looks like | Rough size | Where the fix lives |
|---|---|---|---|
| Second trips | Back tomorrow for the right part | 1 job in 5 | Pre-job info and van stock |
| Tool and material hunt | Twenty minutes finding the impact | ~1 hr/week/person | Staging and a kit list |
| Drive time | Three jobs across town in one day | 10 to 22% of hours | Routing and geography |
| Dispatch ambiguity | "Call the office and ask" | Unmeasured, large | The job record |
| Rework and callbacks | Doing it twice | ~5% of job cost | Scope clarity |
| Paperwork tax | Timesheets in the truck at 6pm | 20 to 40 min/day | Capture at the job |
1. The second trip
This is the most expensive line on the list and the one small shops almost never measure. IBM's field service guide puts the average first-time fix rate around 80 percent, which means one job in five cannot be completed in a single visit, and cites Aberdeen Group research that a rate under 70 percent damages customer retention, satisfaction, asset uptime and SLA compliance.
A second trip is not a fifth of a job. It is two more travel legs, two more setups, two more pack downs, and a customer who has now taken a second half day off work. On a residential HVAC or electrical call, a return visit can cost more in loaded labour than the original margin on the job.
Serfy's breakdown of what drives first visit failures is short and unglamorous: the wrong part, because the tech did not know the model or history before arriving; the wrong skill, because a generalist got dispatched to a specialist job; and an incomplete diagnosis, because the work order said something like "AC not working" and nothing else. All three are information failures that happen before anyone leaves the yard.
2. The tool and material hunt
ABAX puts the average at 38 hours per worker per year spent looking for tools, which is close to an hour every week. Across a ten person operation that is roughly 380 hours a year, which they price at nearly £10,000 at a £25 hourly rate, before you count the tools that get quietly re-bought.
That understates it for trades, because the answer that topped the r/Construction thread was not just tools but materials. A framing crew that cannot find the right fasteners, a landscaping crew hunting for edging in a trailer packed in reverse order, an electrician walking back to the van for the fourth time: none of it shows up on a timesheet as anything other than work.
3. Drive time
Kwant.ai's guidance is that well run operations keep transit under control, and they document a $180M multifamily tower where transit consumed 22 percent of total shift hours before a movement study brought it down to 14 percent. Serfy is blunter about small teams: poor route planning can eat two or more hours a day.
For a local service business this is a geography problem you created at the quoting stage. If you sell across a 90 minute radius because you are afraid to say no, you have already decided that a share of every paid hour goes behind a windscreen. Tightening the service area is a marketing decision with a labour payoff, and it beats optimising routes inside a footprint that is too big to begin with.
4. Dispatch ambiguity
This is the leak with no number attached, which is exactly why it survives. It is the phone call to the office asking what the model number is, whether the customer approved the upgrade, or which unit is being replaced. It is the crew standing on a driveway at 8:10am deciding what to do first.
One of the more thoughtful replies in a 2026 r/Construction thread on motivating workers made the point directly: a fair, competitive wage is the baseline, but past that, gains have to come from structure, because "ambiguity in timelines and expectations is also a huge moral sapper" and good hands start making their own calculations about what needs doing and in what order once they know what is expected. A pipefitter in the productivity thread described the same failure from the other side, working under a foreman who would not order material in the afternoon because it was "too late" in the day, on a crew that worked until 1:30pm.
5. Rework and callbacks
Contractor Foreman puts direct field rework at roughly 5 percent of project cost, rising to about 12 percent once you include delays and extended general conditions. Their worked example: a crew logging 160 hours in a week with 20 hours coded to rework is at a 12.5 percent rework rate, which at a $55 fully burdened rate is $1,100 of labour that moved the job nowhere.
Most small shops never see this number because rework does not get its own code. It gets logged as "finish upstairs bathroom" for the second time.
6. The paperwork tax
The last 20 to 40 minutes of the day, done badly, in a truck, from memory. It corrupts everything upstream. If your labour data is reconstructed at 6pm rather than captured at the job, then every leak above is being measured with a broken ruler, and you will end up arguing about whether Tuesday was seven hours or eight instead of fixing the reason Tuesday had two supply runs in it. We have written separately on how much time contractors waste on paperwork and where it actually goes.
Most of these six leaks are one problem wearing different hats: the job record is incomplete when the crew leaves the yard, and the truth about the day arrives too late to change anything. A custom CRM built around how your crews actually run puts the model, the history, the photos and the approved scope in the tech's hand before the truck moves, and puts the hours on the job the moment they are worked.
Measure before you manage: the five day audit
Do not buy anything yet. Run this first, because the leak ranking above is the industry average and yours will be different.
Give every field person a half sheet of paper with six buckets on it:
- Work. Tools in hand, on the thing you are billing for.
- Travel. Wheels moving between yard and jobs.
- Load and unload. Setup, pack down, staging.
- Waiting or looking. Waiting on a decision, a delivery, another trade, or looking for a tool.
- Supply runs. Any unplanned trip to a supplier or the shop.
- Paperwork. Timesheets, photos, forms, phone calls to the office.
The rule is one line per switch: write the time and the bucket number. Nothing else. It takes about four seconds per switch and produces a usable week.
Three things make or break this:
- Say what it is for, out loud, on day one. This measures the business, not the person. Nobody is in trouble for what their sheet says. If the crew thinks it is a performance review, you will get five days of beautiful fiction.
- Include yourself. Track your own site visits in bucket four for the crew you interrupt. You will not enjoy the result.
- Do not change anything during the week. Baseline first. Fixing while measuring gives you neither.
At the end of the week, total the buckets. Work divided by total gives you tool time. If it lands between 30 and 45 percent you are typical. Then look at which of buckets three through six is largest, because that is the leak you fix first, and it is very unlikely to be the one you assumed on Monday.
Why the tracking app is usually the wrong first purchase
The instinct after a bad week is to buy visibility. It rarely works, because GPS answers the question "where were they" and your actual question is "why did that take six hours."
A contractor in an August 2025 r/Contractor thread on tracking hours across job sites made the case against tracking apps about as directly as it can be made. His view was that any half decent contractor already knows how long a task takes, so reaching for a tracking app shows one of two things: the contractor does not know the job well enough to plan the time required, or does not trust the employees. Either way, in his words, it is a recipe for disaster, and he closed by asking why he would expect subs or employees to accept monitoring he would refuse from a GC.
That is not an argument for flying blind. It is an argument for a different default, and another contractor in the same thread described it well: his crews fill out paper dailies with their time and equipment checks, and he does not cross reference them at all unless a number is way off, at which point he can check the GPS on the trucks. Trust the report, verify by exception. The tracking exists, and it stays in the drawer.
The failure mode of the alternative is visible in the same thread: a contractor who described payroll turning into "a full-blown investigation every week" before geofenced clock-ins fixed the missed punches. Note what that fixed. It fixed data quality on hours, which is worth having. It did not, by itself, recover a single hour of tool time.
Tip
Buy tracking to make payroll accurate, not to make people faster. If your reason for buying it is that you suspect somebody, you have a management conversation to have, and no app will have it for you.
The four numbers worth running after the audit
Once you have a baseline, keep four numbers and ignore the rest. Every extra metric costs attention and none of these need software beyond what you already use.
| Number | How to get it | Where you want it |
|---|---|---|
| Tool time | Work hours ÷ total paid hours | Above 50%, per Serfy's target |
| Second-trip rate | Jobs needing a return ÷ jobs completed | Under 20%, per IBM's average |
| Drive share | Travel hours ÷ total paid hours | Under 20% of the workday |
| Idle share | Waiting hours ÷ on-site hours | Under 10%, per Contractor Foreman |
Contractor Foreman adds a useful guardrail on the other side: field crew utilisation above 85 percent is not a win, it is a signal of burnout or quality risk, and below 65 to 70 percent usually points at weak planning or admin delays rather than effort. The target is a well fed crew, not a sprinting one.
The upside is concrete. Take four people at 40 hours: 160 labour hours a week. At a fully burdened rate near $55 an hour, the figure Contractor Foreman uses in its rework example, that is $8,800 of weekly payroll. Move tool time from 35 to 45 percent and you recover 16 hours a week, worth $880. Across 48 working weeks, roughly $42,000 a year, from a crew you already employ. If you have not yet worked out your own burdened number, start with what your labor burden rate should be, because every figure on this page is wrong without it.
Kwant.ai documents what this looks like in practice: on a data centre build, electricians moved from 48 percent direct tool time to 60 percent purely by reorganising material delivery schedules, taking two weeks off the critical path. Nobody worked harder. The materials just arrived in the right place at the right time.
Fix order: what to change first
- Stage the day before, not the morning of. Pull and stage tomorrow's materials and kit at the end of today. This single habit attacks the top two leaks at once.
- Write a proper work order. Model, serial, history, photos, approved scope, site access. If the crew has to call the office to start, the work order was not finished.
- Set a hard cutoff for material orders. The pipefitter's complaint was a foreman who would not order after lunch. Pick a time, order everything before it, and take that decision away from whoever is having a bad afternoon.
- Give the second trip a name. Code it. Count it weekly. A number nobody records is a number nobody improves.
- Batch your site visits. Turn up at start or end, not mid task. You are the second most upvoted time waster in the thread for a reason.
- Capture hours at the job. Whatever the tool, the entry happens on site, not in a truck at six o'clock.
- Tighten the service radius before you optimise routes. You cannot route your way out of a footprint that is too wide.
What does not work
Paying more, on its own. It is the loudest answer on Reddit and it is half right. Pay keeps good people, and underpaying guarantees you will lose the ones worth keeping. But a well paid crew waiting on a material drop is still waiting.
Pizza and gestures. They help morale and cost little, so do them. They will not move tool time, which is a scheduling output.
Blanket bonuses on hours. A crew bonus tied to hours saved rewards rushing, which shows up later as rework at 5 to 12 percent of job cost. One operator in the motivation thread described weekly bonuses where slacking eats into everyone else's share and the crew self-polices, which works better because the crew is closer to the truth than you are. Tie it to jobs finished right the first time, not hours burned.
Yelling. Nobody in these threads credited shouting with fixing production. Several described what it did to their turnover.
The real constraint: finding out too late
There is one failure underneath all six leaks, and a window and door contractor with six installers named it precisely in r/Contractor in December 2025. He found out he made 8 percent on a job he had priced at 25 percent, and he found out six weeks after the job ended, running Excel and paper timesheets. By then, in his words, he had already started three more jobs on bad assumptions.
That is the actual problem with crew time in a small service business. It is not that the hours are unknowable. It is that they become knowable six weeks after they could have been changed. A crew that lost eleven hours to supply runs in June is not a management problem in August. It is a story.
Whatever you use, the requirement is the same: hours land against the job the day they are worked, second trips get counted, and you can see estimated against actual labour while the job is still open. Get that loop under a week and the six leaks stop being abstractions and become a list you work through. Get it under a day and most of them fix themselves, because the crew can see the same numbers you can.