Your Technician Does Not Cost What You Think

What Burden Actually Includes

Labor burden is every cost of employing a person that is not their wage. The list is longer than most estimates assume, and the items people leave out are rarely the small ones.

The employer's share of payroll taxes is the obvious starting point. Workers' compensation is the one that does the real damage, because premiums are set by classification code and vary by a multiple, not a margin, between trades. Then come the costs people file mentally as overhead and never allocate to a technician at all: the truck, its fuel, its insurance and its maintenance; tools and their replacement; the phone; uniforms; ongoing certification and training.

Finally there are the paid hours nobody bills. Holiday, sick leave, training days and travel between jobs are hours you pay for and cannot invoice. They belong in the burden calculation because the money leaves the business regardless.

The Denominator Is Where It Goes Wrong

Most burden calculations fail on the bottom of the fraction rather than the top. A contractor carefully totals every employment cost, then divides it by 2,080 hours because that is what a full-time year contains, and produces a number that is confidently wrong.

A technician paid for 2,080 hours does not bill 2,080 hours. Subtract holiday and sick leave. Subtract training. Subtract drive time between calls, which on a dense service route can be a fifth of the day. Subtract the time spent at the counter waiting on a part, and the paperwork done at the kitchen table at seven in the evening that never makes it onto a work order.

What remains might be 1,500 hours. Spreading the same burden over 1,500 hours instead of 2,080 raises the true hourly cost by nearly forty percent — and that difference is the entire margin on a lot of service work.

This is why burden is not really an accounting exercise. It is a measurement problem, and it is only as good as your record of where technician hours actually went.

Working the Calculation

The method is simple once the inputs are honest. Take one technician. Total their annual gross wage. Total every burden cost listed above for that same person over the same year. Add the two together to get the annual cost of employing them. Then divide by the hours that person genuinely billed last year.

The result is the fully burdened hourly cost, and it is the floor beneath which any hour of that technician's time is sold at a loss. Your billable rate sits above it by whatever gross margin the business needs to cover overhead and profit.

Run it per role rather than once for the company. A service technician with a take-home truck and a helper who rides along carry very different burdens, and averaging them hides both.

1. Pick one employee and one twelve-month period.
2. Total gross wages paid, including overtime actually worked.
3. Total every employment cost above wages for that person in that period.
4. Add them for the true annual cost of employment.
5. Count the hours that person actually billed — not the hours they were paid.
6. Divide annual cost by billable hours for the fully burdened rate.
7. Repeat per role, and revisit whenever workers' compensation rates or benefit costs change.

Why the Number Drifts

Burden is not a constant you calculate once and paste into an estimating template for five years, though that is how it is usually treated. Workers' compensation classifications get reclassified. Health premiums move annually. Fuel moves weekly. A decision to put two more technicians in take-home trucks changes burden for those two people immediately and for the blended rate quietly.

The practical failure is not that the number is wrong on the day it is calculated. It is that it stays on the spreadsheet where it was calculated while the business changes around it, and estimates keep being priced off a figure that described the company two years ago.

The fix is to derive burden from the same system that records payroll, job costs and technician hours, so the rate moves when the inputs move rather than when somebody remembers to update a cell.