WeavrCRMWorker-Hours vs. Bay-Hours: Start With the Right Denominator
Most detailing bottlenecks are labor constraints, not space constraints. A mobile operator has no bay at all, and a one-bay shop with two technicians is limited by the technicians, not the bay. Before you calculate utilization, decide which resource is actually your binding limit. If you run out of technician time before you run out of bay or parking space, your denominator is worker-hours. If you consistently have technicians waiting for a bay to open, your denominator is bay-hours.
Worker-hours are calculated per person, per shift. A solo operator working five days at eight hours per day produces 40 raw hours per week. A shop with two techs on the same schedule produces 80. Bay-hours follow the same math but count available bays instead of bodies. Mixing them up produces a utilization number that hides the true bottleneck, so pick one definition and stay consistent across every period you measure.
Related resource: Measure Detailing Revenue per Labor Hour Without Misleading Yourself
Sellable Hours Are Not the Same as Scheduled Hours
Raw available hours overstate what you can actually sell. You need to subtract time that is structurally unavailable before you build your denominator. This includes your standard travel blocks for mobile routes, mandatory equipment setup and breakdown, end-of-day vehicle or bay cleaning, and any administrative time you cannot realistically sell around. What remains is your sellable capacity.
A common mistake is treating every hour an employee is on the clock as sellable. If your tech arrives at 8 a.m. but needs 20 minutes to load the van and another 20 minutes at the end of the day to clean and inventory supplies, you lose 40 minutes of sellable time daily before a single customer interaction. Annualized across 250 working days, that is roughly 167 hours of phantom capacity that was never real.
How Cancellations and No-Shows Affect the Calculation
Cancellations and no-shows reduce realized utilization but they do not change sellable capacity. The slot existed, it was available, and the hour passed unused. That is what capacity utilization is measuring. Do not subtract cancellations from your denominator; instead, let them show up as unfilled time in your numerator. That distinction matters because it tells you whether low utilization is a scheduling problem, a policy problem, or a demand problem.
Track cancellations separately so you can see two different utilization figures: scheduled utilization at the start of the week and realized utilization at the end. A wide gap between those two numbers points to a cancellation or no-show problem. A consistently low scheduled utilization number points to a lead volume or conversion problem. They require different fixes.
Buffers Are Structural, Not Waste
Every realistic schedule includes buffers between jobs, and those buffers belong in your sellable-hours calculation as a deliberate deduction, not an embarrassing gap. A 15-minute buffer between appointments allows for a job that runs over, a customer who shows up late, or a vehicle condition that was worse than quoted. Removing buffers to squeeze in one more job per day is a common pressure point for small operators, and it creates chronic lateness, quality shortcuts, and technician burnout.
The right question is not how to eliminate buffer time but how much buffer you actually need versus how much you are currently using. If your buffers routinely go untouched because jobs always finish on time, you may have room to tighten them slightly. If buffers are consumed almost every day, they are earning their keep and you should not cut them to inflate a utilization number.
Related resource: Detailing Business KPIs: A Small Set Worth Reviewing
Calculating Utilization for a Matched Period
Utilization is only meaningful when numerator and denominator cover the same time window. Pick a fixed period, typically a week or a month, and be consistent. Do not measure capacity for five days and revenue hours for four because of a holiday. Every exception should be explicitly handled: holidays reduce both sellable capacity and the opportunity to book, so remove them from both sides of the equation for a fair comparison.
The formula is straightforward. Realized utilization equals billable hours completed divided by sellable hours available in the same period, expressed as a percentage. Scheduled utilization replaces completed with booked. Run both weekly so you can see trends without waiting for month-end.
| Metric | Formula | What It Tells You |
|---|---|---|
| Raw available hours | Technicians x shift length x working days | Theoretical ceiling; not actionable alone |
| Sellable hours | Raw hours minus travel blocks, setup, cleanup, admin | Realistic denominator for utilization |
| Scheduled utilization | Booked hours / sellable hours x 100 | Demand and conversion health at week start |
| Realized utilization | Completed billable hours / sellable hours x 100 | Actual output after cancellations and overruns |
| Cancellation impact | Scheduled minus realized utilization | Isolates policy or reliability problems |
| Buffer consumption rate | Buffer time used / buffer time allocated x 100 | Whether buffers are appropriately sized |
Worked Scenario: Spotting a Bottleneck at a Two-Technician Shop
Hypothetical example: a shop owner runs two technicians Tuesday through Saturday, five-hour sellable shifts each after deducting setup and breakdown time. Sellable capacity is 2 technicians x 5 hours x 5 days, which equals 50 sellable hours per week. In a sample week the shop completes 38 billable hours. Realized utilization is 38 divided by 50, or 76 percent. Scheduled utilization at the start of that same week was 46 hours booked, or 92 percent. The 16-point gap signals that cancellations and a few jobs running short consumed roughly 8 hours of expected revenue.
Looking closer, the owner notices that Tuesday and Wednesday are fully packed with one technician while the second technician sits at around 60 percent on those same days. That is a scheduling distribution problem, not a capacity shortage. Thursday through Saturday both technicians are consistently above 85 percent realized utilization. The actionable insight is not to hire a third person but to redistribute bookings earlier in the week and tighten the cancellation policy, since the slack is concentrated and not systemic.
When High Utilization Is a Warning Sign
Consistently hitting 90 percent or above realized utilization sounds like success, but it often means you have no room to absorb a sick day, an equipment failure, or a job that goes sideways. Running at near-total capacity also means you are likely turning away new customers or making them wait so long they book a competitor. The goal is not to maximize the percentage but to operate at a level where quality stays high, technicians are not exhausted, and you can take on a high-value urgent job when one comes along.
A failure case worth recognizing: an operator who chases high utilization by cutting buffers and stacking appointments tightly will see strong numbers for a few weeks, then a cascade of quality complaints, refund requests, and technician turnover. The utilization metric looked great right up until it caused real damage. Sustainable utilization leaves deliberate room in the schedule.
Related resource: Estimate Detailing Customer Lifetime Value With Conservative Inputs
Tracking This in Practice
You do not need specialized software to measure capacity utilization. A weekly spreadsheet with five inputs, sellable hours, booked hours at week start, completed billable hours at week end, cancellation count, and buffer time used, gives you everything in the table above. Review it every Monday morning using last week's numbers. The pattern over six to eight weeks will tell you far more than any single week's figure.
If you use a scheduling tool like Weavr, the appointment and task records for a given period give you a reliable source for completed job time, especially if you use the optional process timer on jobs. The goal is a consistent data source, not a perfect one. Even rough weekly numbers reviewed regularly will surface the bottleneck decisions that are worth your attention: whether the problem is in demand, cancellations, or actual capacity.
WEEKLY CAPACITY UTILIZATION TRACKER Period: ____________ Technicians: ____ Working days this week: ____ 1. Raw available hours: ___ techs x ___ hr shifts x ___ days = ___ hrs 2. Deductions: Travel blocks: ___ hrs Setup / breakdown: ___ hrs Admin time: ___ hrs Total deductions: ___ hrs 3. Sellable hours (line 1 minus line 2): ___ hrs 4. Booked hours at week start: ___ hrs Scheduled utilization: line 4 / line 3 x 100 = ___% 5. Completed billable hours at week end: ___ hrs Realized utilization: line 5 / line 3 x 100 = ___% 6. Cancellation / no-show impact: line 4 minus line 5 = ___ hrs lost 7. Buffer time allocated this week: ___ hrs Buffer time consumed: ___ hrs Buffer consumption rate: consumed / allocated x 100 = ___% Notes on where gaps concentrated (days, technicians, job types): ____________________________________________________________ One action for next week based on this data: ____________________________________________________________
The practical takeaway
Define your sellable hours first, then track both scheduled and realized utilization weekly. The gap between them points to your real problem, and a consistently high number is a warning, not a goal. Use the tracker above for six straight weeks before drawing conclusions.
Explore the relevant WeavrCRM workflow · Review integrations and requirements