Key takeaways
- A wage rate excludes benefits, legally required costs, paid leave, overtime premiums, supervision, and the productive-hour denominator.
- Burden should be calculated by labor pool and applied using a driver that reflects how resources are consumed.
- The denominator is often the largest modeling error: paid hours are not the same as productive, billable, or standard hours.
- Job-level labor variance should separate rate, utilization, efficiency, overtime, travel, rework, and mix.
- The model should reconcile to payroll and the general ledger before management uses it for pricing or profitability.
A company can pay a technician $30 per hour and lose money on work priced as if labor costs $45. The missing economics may include payroll taxes, health insurance, retirement contributions, paid leave, training, supervision, vehicles, tools, travel, unbillable meetings, bench time, overtime premiums, and rework. None of those costs disappear because the estimating system starts with wages.
Fully burdened labor cost is not one universal percentage. It is a model that assigns employment and support costs to a credible productive-hour base. The right design varies across field service, professional services, installation, construction, healthcare, staffing, repair, maintenance, and manufacturing support.
BLS measures employer compensation as wages plus paid leave, supplemental pay, insurance, retirement, and legally required benefits per employee hour worked. IRS and DOL guidance establish additional payroll-tax and overtime obligations.
Company pricing requires its own payroll and operating data, but the official categories show why wages alone are incomplete.
A burden model should reconcile actual cost categories and the hours over which those costs are recovered.
Direct labor
Labor traceable to a job, customer, project, work order, or service activity
Labor burden
Employer costs and support costs added to direct wages under a documented allocation policy
Productive hour
An hour available for the activity used to recover cost, such as billable, standard, installation, production, or service time
The burden rate is only as credible as its denominator. Dividing by paid hours can materially understate cost when leave, training, travel, bench time, and internal work are substantial.
Define the labor pools before calculating a rate
Do not average employees whose economics differ materially. Separate labor pools by role, geography, benefit structure, union status, overtime profile, vehicle or equipment requirement, billability, and operating model. A senior implementation consultant and an entry-level support analyst should not carry the same rate merely because both sit in professional services.
Be explicit about which question the rate answers. A direct labor rate supports job performance. A contribution rate supports short-term pricing decisions. A fully loaded rate supports long-run service-line economics. Mixing the three creates arguments where each participant is using a different cost definition.
Build the productive-hour denominator
Start with paid hours, then subtract hours unavailable for the activity being costed. For an hourly field technician, that may include holidays, vacation, sick time, training, company meetings, shop time, and nonrecoverable travel. For salaried professionals, begin with scheduled annual hours and apply the same logic using time records or a defensible capacity study.
If annual employment and direct support cost is $118,400, dividing by 2,080 produces $56.92 per hour. Dividing by 1,480 productive hours produces $80.00. The $23.08 difference is not an accounting technicality. It determines whether quoted work actually recovers the cost of maintaining the labor capacity.
Avoid double counting. If paid leave remains in annual cost and leave hours are removed from the denominator, do not also add a paid-leave percentage to the numerator. Document the convention and reconcile the model to actual payroll.
Operating workflow scan
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Move from a burden rate to job and service-line economics
Apply labor-pool rates to actual or standard productive hours by job. Then separate the reasons actual labor economics differed from estimate. A single unfavorable labor variance is not actionable.
Labor Cost Model Flow
1. Reconcile cost
Tie wages, taxes, benefits, and support pools to payroll and the general ledger.
2. Define labor pools
Group employees with similar economics and operating use.
3. Bridge capacity
Convert paid hours into productive-hour assumptions.
4. Calculate rates
Divide recoverable costs by productive hours under a documented policy.
5. Apply to work
Cost actual and estimated hours by job, customer, and service line.
6. Explain variance
Separate rate, efficiency, utilization, overtime, travel, rework, and mix.
7. Update decisions
Refresh pricing, staffing, scheduling, process, and customer terms.
A field-services company believed one national account was attractive because technician wages represented less than 35 percent of revenue.
A burden model showed long travel, certification time, supervisor coordination, and low route density reduced productive hours materially.
The account remained profitable at contribution level but failed to recover the labor platform at the contracted price. Management renegotiated minimum charges and territory coverage rather than imposing a generic price increase.
Controls that keep the model credible
A burden model should have a named owner, effective date, source schedule, allocation policy, and reconciliation. Finance should own cost completeness; operations should own productive-hour and workflow assumptions; commercial leaders should own how the rate enters estimating and pricing.
Labor Burden Control Checklist
- Reconcile annual wages and burden pools to payroll and the general ledger.
- Separate materially different labor pools.
- Document productive-hour assumptions and exclusions.
- Prevent paid-leave double counting.
- Use actual timekeeping and job codes where available.
- Separate direct, contribution, and fully loaded cost views.
- Explain labor variance by driver rather than one total.
- Track estimated versus actual productive hours.
- Refresh rates after material compensation or operating changes.
- Protect individual compensation data through pooled reporting.
Frequently asked questions
Should every employee have an individual rate?
Not necessarily. Stable labor pools are usually easier to govern and avoid exposing individual compensation.
Should general overhead be included?
Include it when testing long-run price sufficiency or service-line viability; keep it separate for incremental contribution decisions.
How often should rates change?
Reconcile monthly, review assumptions quarterly, and refresh when compensation, benefits, staffing, utilization, or operating design changes materially.
Work with Glacier Lake Partners
Build a Labor Burden Model
We help service, project, and field businesses connect payroll, timekeeping, utilization, job costing, pricing, and customer profitability.
Explore Operational Advisory →Operating workflow scan
Find the reporting or execution workflow worth automating first.
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Research sources
Disclaimer: Financial figures and case-study details in this article are anonymized, composite, or representative examples based on middle market operating situations, and are not guarantees of outcome. Statistical references are drawn from cited third-party research; individual transaction and operational results vary based on business characteristics, market conditions, and deal structure. This content is for informational purposes only and does not constitute legal, financial, or investment advice. Consult qualified advisors for guidance specific to your situation.
Explore adjacent topics
