Scroll any trade subreddit and you will find the owner confessing: "Dave is booked three weeks out, my other two guys are washing vans. Customers only want Dave. What do I do?" Uneven load is rarely laziness; it is invisible scheduling physics. Work flows to the person the scheduler trusts, the one whose skills are known, the name customers ask for. Left alone, the imbalance burns out your best tech, stalls the others' development and caps your revenue at one person's capacity. Rebalancing is a visibility problem first and a habit problem second.
See the imbalance before arguing about it
On a whiteboard or a shared calendar, uneven load hides in plain sight. On a dispatch board with a column per person, it is unmissable: one column solid, three gappy. Start every scheduling session with that view. Owners consistently report the same discovery in week one: the imbalance was worse than they thought, and half of it was habit, not necessity, jobs Dave got because Dave was the default.
Tag skills so trust stops being a bottleneck
The scheduler routes to Dave because the scheduler knows what Dave can do. Fix the knowledge, not the scheduler: tag each technician's certifications and strengths, gas, HV, cranes, customer-facing polish, in your system, and tag jobs with what they need. Now "who can take this" is a filter, not a gut call, and the mid-level tech with the right ticket finally gets the job that grows them. Our licence tracking guide covers keeping those tags current and compliant.
Book the person, sell the business
Customers asking for Dave by name is a compliment that becomes a constraint. The escape is deliberate: pair juniors onto Dave's jobs so faces multiply, brand the quality standard as company process, checklists, photos, sign-off, rather than personal magic, and offer "Dave's next slot is the 28th, or we can have Maria there Thursday with the same checklist Dave built". Some customers wait; most take Thursday, and Maria earns the next direct request.
Balance by hours and margin, not job counts
Six short services and one all-day switchboard are not equal columns. Balance on booked hours against available hours per person, and keep an eye on margin mix so one tech is not hoarding all the profitable work our job costing guide teaches you to spot. Utilisation targets around 75 to 85 percent leave room for travel, quotes and the emergency that always comes; a tech at 100 percent for weeks is your next resignation letter, a pattern well documented in trades workforce research from bodies like the US Bureau of Labor Statistics on overtime and turnover.
Rebalance weekly, in ten minutes
Make Friday's last task a ten-minute rebalance: eyeball next week's columns, drag two or three jobs from the heavy column to the light ones, confirm skills tags match, done. Send automatic notifications so the crew learns changes from the app, not the grapevine. A month of that habit and "everyone books through Dave" quietly becomes "the board looks level", which is what a business that scales past its best tradesperson looks like.
Frequently asked questions
What utilisation should I target per technician?
75 to 85 percent of real bookable hours. Below that you are leaving revenue idle; above it there is no room for travel variance, quotes or the daily emergency, and you are borrowing against burnout. Measure against genuine on-tools hours, not the 40-hour fiction.
Customers only want my senior tech. How do I spread demand?
Multiply trusted faces deliberately: pair juniors onto the senior's jobs so customers meet them under the halo, encode the senior's standards into checklists so quality reads as company process, and offer the concrete choice of waiting for the name or taking a sooner slot with the same checklist. Most take the slot.
Should I balance by number of jobs per tech?
No, job counts lie: six short services and one all-day switchboard are not comparable columns. Balance booked hours against each person's available hours, and glance at margin mix so profitable work is not pooling on one van. Hours-based balance is what the board should show by default.
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.
Key takeaways
- A per-person board makes imbalance visible instantly
- Skills tags turn routing from gut feel into a filter
- Multiply trusted faces deliberately; sell the standard, not the person
- Balance on hours and margin at 75 to 85 percent utilisation
- Ten-minute Friday rebalance, notified through the app
Stop running the job from a spreadsheet
Schedule your crew, run jobs from the van, and invoice the moment they are done. Free for one user, forever.
Start free trial
