How much work can we actually take? Capacity for trade businesses

The overbooked week never feels like a decision; it feels like enthusiasm. A good month of enquiries, a few yeses that should have been "week after next", and suddenly the crew is doing twelve-hour days, quality wobbles, and the forum post writes itself: "How do you know when to stop taking work?" The answer is a number most trade businesses have never calculated: real capacity, in bookable hours per crew per week, derived from their own history rather than optimism. Once the number exists, protecting it is mostly mechanical.

Real capacity is smaller than the calendar

A tech on a 40-hour week does not produce 40 billable on-site hours; travel, merchant runs, quoting help, callbacks and the tasks nobody logs consume a share that your own records will reveal. Pull a month of clock-on data and compute genuine on-tools hours per person: most businesses land between 60 and 75 percent of paid hours, a range consistent with utilisation and productivity measurement across service industries, the discipline national productivity statistics formalise. That percentage, times crew, is your true weekly inventory. Everything else in this article is defending it.

Book to 85 percent, not 100

Full-looking calendars fail because reality is variable: jobs overrun, the emergency arrives, someone is sick. Booking to roughly 85 percent of real capacity leaves the shock absorber that keeps promises intact, the same slack that makes cancellations and weather survivable. The visible version of this is board hygiene: float slots held per crew, emergency windows in emergency-heavy trades, and the discipline to see white space as resilience rather than waste.

Honest durations from quoted-versus-actual

Capacity maths dies if a "two-hour" job type reliably takes three. Your quoted-versus-actual history, the loop from job costing, recalibrates duration templates until booked hours resemble real ones. This single correction fixes more overbooking than any policy: the calendar was not too full, the jobs were fictionally short.

Saying not-yet without losing the work

Capacity discipline sounds like turning work away; in practice it is scheduling honesty. "We can do it properly in the week of the 9th" wins more long-term revenue than a squeezed yes delivered late and rough, and the customer who cannot wait was priced on urgency anyway. Tools that show live availability make the conversation easy, and the standby list converts genuine gaps into opportunistic wins. Premium urgency pricing for genuine squeeze-ins is legitimate and disclosed, not apologised for.

Capacity tells you when to hire

The number's final gift is timing your next hire on evidence: when bookings sustainably push past 85 percent for six-plus weeks and the enquiry pipeline holds, the next tech pays for themselves, the arithmetic our first-hire guide runs. Hiring off a hot fortnight builds payroll for a spike; hiring off a capacity trend builds a business. The same dashboard flags the opposite move early, a soft quarter showing as sagging utilisation months before the bank balance says it.

Frequently asked questions

How do I calculate my crew's real capacity?

Pull a month of clock-on data and compute on-tools hours per person against paid hours; 60 to 75 percent is typical once travel, merchant runs and callbacks take their share. Multiply across the crew for weekly bookable inventory, then book to about 85 percent of it.

Isn't leaving 15 percent unbooked just lost revenue?

It is the shock absorber that keeps every promise you did make: overruns, emergencies and sickness land in the slack instead of on customers. Businesses that book to 100 percent still deliver about 85, just late, rough and with burnt-out crews. The slack also monetises: emergencies pay urgency rates.

When does capacity data justify hiring?

When utilisation holds above your booking ceiling for six or more weeks and the enquiry pipeline is not a blip, the next hire is funded by work you are currently declining. Hire on the trend line, not the hot fortnight, and the new tech arrives to a full board.

The bottom line

The pattern across every topic on this blog repeats here: the businesses that win are not working harder, they are keeping better records and letting systems carry the routine. Start with one change this week, measure it for a month, and let the results argue for the next one. And if you want the whole loop, scheduling, field app, safety and invoicing in one place, start a free SKEDS trial and test it on a real week of your own jobs.