Employee variance is the week-over-week variability in billable hours logged by an individual staff member. For professional services firms, it is an early warning metric — high variance in an employee's output indicates scheduling inconsistency, project gaps, or workload imbalance before those problems show up in monthly utilization averages. The formula is: Variance % = (Actual Hours − Target Hours) ÷ Target Hours × 100. A standard deviation below 20% of weekly target hours is considered stable. Industry practice: track rolling 8-week standard deviation per employee and flag anyone consistently above 35% variance.
Two measures of employee variance — the weekly point-in-time calculation and the rolling statistical measure for trend detection.
A consultant with a 75% utilization target — 8 weeks of actual output with elevated variance flagged.
Weekly billable hours: 32, 28, 35, 12, 31, 29, 38, 8.
Average = 26.6 hours (66.5% utilization — below target). Standard deviation = 10.1 hours. Variance as % of target = 10.1 ÷ 30 = 33.7% — elevated.
The two low-output weeks (12 hrs, 8 hrs) are dragging down the average and suggest a project gap or staffing problem. A PM should investigate whether those weeks involved between-project bench time and whether a new engagement was lined up in time.
Rolling standard deviation as a percentage of weekly target hours — the primary threshold for triggering review.
| Variance Level | Rolling StdDev (% of target) | Interpretation | Action |
|---|---|---|---|
| Stable | <20% | Consistent workload allocation | Monitor normally ESTIMATE |
| Moderate | 20–35% | Some scheduling inconsistency | Review project pipeline ESTIMATE |
| Elevated | 35–50% | Project gaps or logging issues | PM intervention needed ESTIMATE |
| Critical | >50% | Chronic instability | Immediate staffing review ESTIMATE |
A 72% average can mask an employee who alternates between 95% and 50% weeks. Those low weeks are project gaps — lost revenue that can't be recovered. Track both mean and variance.
Planned low weeks (internal projects, training, PTO) are acceptable. Unplanned low weeks (no billable assignment) indicate pipeline or scheduling failure. Your tracking system should flag the difference.
High variance is a scheduling problem, not necessarily a performance problem. Using it as a performance indicator creates perverse incentives for staff to log time to any available project just to reduce variance.
Low employee variance is a signal of operational maturity. It means the firm has consistent project pipeline, good capacity planning, and reliable time management practices — all attributes acquirers value.
Firms where 40% of staff exhibit high variance have hidden revenue volatility that doesn't show in monthly summaries. Building variance monitoring into weekly ops reporting is a low-cost way to surface capacity problems 2–4 weeks earlier than monthly utilization reviews.
The free ProServ Health Assessment scores your operational health in 5 minutes. Then see every metric calculated with your own numbers.