How to Use Revenue per Field Employee in an Electrical Business

What the Metric Means

Revenue per field employee answers one question: how much revenue does the company generate for each person who performs billable work? It is a productivity ratio, not a profitability measure, and it deliberately ignores everything happening in the office so that the field side of the business can be looked at on its own.

The reason contractors find it useful is that it moves for interesting reasons. When pricing improves, it rises. When crews spend more of the day billable, it rises. When job sizes grow, it rises. When callbacks eat productive hours, it falls. A single line that responds to pricing, utilization, and job selection is worth watching, because it catches drift in any of those areas before the income statement does.

What it cannot do is tell you whether you are doing well relative to other companies. Two electrical contractors with identical crews can differ by a factor of three purely because one sells service calls and the other installs gear. Treat it as a private measure of your own trajectory, and be skeptical of every published benchmark.

The Formula and the Denominator

The calculation is simple. The discipline is in the denominator.

"Average" matters more than contractors expect. A company that ends the year with ten electricians but started with six did not have ten all year. Using the ending headcount understates productivity badly during growth and flatters it during contraction. Average the headcount across the months in the period, and if you can, use full-time equivalents rather than bodies so that part-time and partly-billable people are counted as the fraction they actually represent.

The single biggest source of nonsense in this metric is a denominator that changes definition between periods. If Q1 counted the working owner and Q2 did not, the change you are looking at is bookkeeping, not performance. Write the definition down once, including how you handle owners, apprentices, and anyone who splits time between the field and the office, and do not revise it casually.

Revenue should be defined just as carefully. Use recognized revenue net of sales tax and net of any credits or refunds issued in the period. If you invoice progress billings on larger projects, keep the treatment consistent from quarter to quarter rather than switching between billed and earned as it suits the story.

Who Counts as a Field Employee

The denominator is billable field employees — the people whose hours are expected to appear on jobs. Journeymen, apprentices, service technicians, and working foremen belong in it. Dispatchers, estimators, office administrators, and bookkeepers do not, because their cost is recovered through overhead rather than through billable hours. Our overhead guide works through that separation and why it matters for pricing.

Partly-billable people need a fraction rather than a yes or no. A field supervisor who runs work two days a week and manages the rest is 0.4. A working owner who takes service calls most mornings might be 0.5. These estimates do not need to be exact; they need to be consistent and revisited only when the role genuinely changes. The organizational structure guide covers how those hybrid roles typically evolve as a company grows, which is usually when the fractions need updating.

Subcontracted labor is a separate decision. If you regularly use subs as an extension of your crews, excluding them will make your revenue per employee look excellent while hiding where the work actually came from. The cleanest approach is to exclude subs from the denominator and also exclude subcontracted revenue from the numerator, so the metric describes work your own people performed.

Service vs Project Businesses

Service and project work produce structurally different numbers, and a company running both should calculate the metric separately for each division before looking at the combined figure.

Service work is labor-dense. A technician driving to residential calls generates revenue mostly from their own hours, with modest material content, so revenue per head sits lower and moves almost entirely with pricing and utilization. That makes it a clean productivity signal — if service revenue per technician moves, something real changed in the rate, the ticket, or the number of calls completed.

Project work is different. A crew installing a service upgrade or a lighting package pushes significant material and equipment through the same headcount, so revenue per head is higher and far more volatile. One switchgear package can lift a quarter without anyone becoming more productive. This is the main reason a blended company-wide number is often uninterpretable: the mix between the two divisions moves the result more than the performance of either.

If you cannot split cleanly, at minimum note the revenue mix alongside the metric each period. A number that rose from 55% to 70% project work has explained most of its own movement.

Apprentice and Journeyman Mix

Crew composition changes the metric in ways that have nothing to do with management quality. An apprentice-heavy company will show lower revenue per field employee than one staffed entirely with journeymen, because apprentices bill at lower rates and complete less work per hour while they learn.

That is not a problem to be solved by avoiding apprentices. A well-run apprentice program is usually the cheapest source of future journeymen and it improves gross margin per hour over time even as it depresses revenue per head in the short run. What matters is knowing which force is moving the line. If revenue per field employee dropped 12% in a quarter where you added two apprentices, that is arithmetic, not decline.

The useful discipline is to track the mix alongside the metric — the ratio of journeymen to apprentices, period by period. When mix is stable, movement in the metric is real performance. When mix moved, adjust your reading before you act. Developing apprentices into productive field staff faster is largely an onboarding and field-leadership problem, which the onboarding guide and the field leadership guide both address directly.

How Pricing Moves the Number

Pricing is the fastest lever on revenue per field employee and the one most often overlooked, because contractors instinctively read a weak number as a productivity problem. A crew that is fully utilized, organized, and completing work efficiently will still produce a poor figure if the billing rate does not cover what the work is worth.

A rate increase flows almost entirely into this metric. Raise the labor rate by 8% with the same crews doing the same volume of work and revenue per field employee rises by roughly 8% — no new hires, no new efficiency, no additional risk. That is a materially better outcome than chasing the same increase through headcount, which requires demand, recruiting, training, and cash. Our pricing strategy guide covers how to build and defend those rates, and the labor rate calculator works out what your rate needs to be from wages, burden, billable hours, overhead, and target margin.

The reverse is equally true. A steadily declining revenue per field employee in a company whose crews are busy is very often a pricing problem developing quietly — discounting to win work, quoting from last year's rates, or absorbing wage increases without passing them through.

Labor Utilization

Utilization is the share of paid field hours that end up billable. It is the other main driver of this metric and the one most directly within operational control. Drive time, supply-house runs, waiting on access, rework, and idle scheduling gaps all consume paid hours that produce no revenue.

The arithmetic is unforgiving. A technician paid 2,000 hours who bills 1,300 has 65% utilization; getting to 1,450 billable hours without hiring anyone is an 11% increase in output from the same payroll. Almost all of that comes from scheduling density, better pre-job material staging, and fewer return trips — the substance of the dispatch and scheduling guide and the material management guide.

Because utilization and pricing both push the same metric, always look at them together. A rising revenue per field employee driven by utilization means the operation improved. The same rise driven by rate means the market accepted better pricing. Both are good; they call for completely different next moves.

Average Ticket and Job Size

Average ticket is the third structural driver. Two service technicians completing the same number of calls per week will produce very different revenue per head if one averages a $450 ticket and the other $780. The difference typically comes from diagnostic thoroughness, presenting options rather than a single price, and catching adjacent work while already on site.

On the project side the equivalent is job size. Larger jobs carry a fixed amount of mobilization, setup, and travel across more revenue, so they lift revenue per head even when hourly productivity is unchanged. This is why a company that lands two large projects in a quarter sees the metric jump without anything about its crews having improved.

Ticket growth is generally the healthiest way for this metric to rise, because it usually reflects better diagnosis and better selling rather than more hours. The sales process guide covers the field-level habits that move it, and the service call pricing guide covers structuring the call itself.

Callbacks and Rework

Callbacks are the quietest destroyer of this metric. A warranty return consumes paid hours, fuel, and often material while generating zero revenue — it hits the denominator indirectly by burning capacity that could have been billable, and it usually costs goodwill on top.

The effect compounds. A company running an 8% callback rate is effectively operating with roughly one field employee in twelve producing nothing. Cutting that rate in half is equivalent to finding half a person of free capacity, without recruiting, training, or adding a van. That is a far cheaper source of output than hiring, and it is why callback tracking belongs next to this metric rather than filed separately. The quality control guide works through measuring and reducing the rate.

Material-Heavy and Sub-Heavy Work

Revenue includes material and equipment, which means the metric can be inflated by work that is simply expensive rather than productive. A crew installing a large gear package may run enormous revenue through a small number of labor hours. Nothing about the company got better; the revenue mix changed.

Subcontracted work distorts it in the same direction and more severely, because subcontract revenue passes through your books entirely without touching your field headcount. A company that subcontracts trenching, fire alarm, or generator setting can post an impressive revenue per employee while its own crews produce the same output as last year.

There are two workable responses. Either exclude pass-through material and subcontract revenue from the numerator to get a labor-centric measure, or keep the full revenue and always pair it with the gross profit version below. The first is cleaner; the second is easier to produce from most accounting systems. Either is fine as long as you do not alternate between them.

Capacity and Overtime

Revenue per field employee and capacity utilization are close relatives. When the metric rises steadily while crews are already near their practical hour ceiling, you are approaching a genuine capacity limit rather than an efficiency gain. Beyond that point further revenue growth requires people, not scheduling.

Overtime is the warning light. Occasional overtime is normal and often profitable — premium hours against an unchanged overhead base. Persistent overtime is a headcount shortage being financed at a premium rate, and it will show up as an artificially high revenue per field employee immediately before it shows up as turnover and callbacks. A number propped up by systematic overtime is not sustainable output; it is borrowed output. The capacity planning guide sets out the available-hours math and the thresholds where adding a person becomes the right answer.

Seasonality

Most electrical contractors have a seasonal shape — heavier service demand in temperature extremes, project work that clusters around construction schedules, slow stretches around holidays. Because headcount is far stickier than revenue, the metric swings hard by season even in a perfectly stable company.

Two habits fix this. Compare each period against the same period a year earlier rather than the one immediately before it, and keep a rolling twelve-month figure alongside the monthly reading. The rolling number is what you should use for decisions; the monthly number is for noticing things early.

Seasonality also explains one of the most common misreadings. A drop in the slow quarter is not a productivity failure — it is the cost of retaining crews you will need in eight weeks. Cutting staff to defend the ratio through a predictable trough usually costs far more in recruiting and ramp-up than it saves.

Gross Profit per Field Employee

The revenue version tells you how much work is flowing through each person. The gross profit version tells you how much of it the company actually kept, and it is the more important of the two.

Tracked side by side, the two lines diagnose each other. Both rising means the company is genuinely producing and keeping more per person. Revenue rising while gross profit stays flat means volume grew without value — usually material or subcontractor pass- through, or larger work sold at thinner margins. Gross profit rising while revenue is flat is the best pattern of all: better pricing or better job costing on the same volume.

Run both versions from your own numbers with the revenue per field employee calculator to see the period-over-period change and which force is moving the number.

Gross profit per field employee is also the number that connects productivity to overhead. Total gross profit has to cover overhead before anything reaches net profit, so gross profit per head multiplied by headcount is effectively your capacity to carry the office. Contractors who add field staff without checking that relationship find their break-even climbing faster than their gross profit — the arithmetic behind the break-even revenue guide. Getting the underlying job data accurate enough to trust is the subject of the job costing guide.

Why Higher Is Not Always Better

Several of the ways this number can rise are outright bad. Systematic overtime raises it while burning out crews. Pushing subcontracted work through the books raises it while transferring margin to someone else. Skipping quality steps to move faster raises it for a quarter and then reverses when the callbacks land. Cutting apprentices raises it immediately and quietly removes the pipeline that would have staffed the company in two years.

There is also a ceiling that is simply physical. A person can only be on site so many hours, and past a certain point the only ways to raise revenue per head are price, job size, or mix. Companies that keep pushing on effort after that point get turnover instead of output.

Reading the Trend

Treat any single period as noise. What carries information is the direction across four or more quarters and, critically, whether the two versions of the metric move together.

Work through the reading in a fixed order. First, did the denominator definition change? Second, did the crew mix change — apprentices added, a supervisor moved off the tools? Third, did revenue mix change between service and project, or toward material and subs? Only once those three are ruled out are you looking at a genuine change in pricing or productivity. Most confusing movements in this metric are answered by one of the first three questions.

Keep the history visible rather than recalculating it each time. A twelve- or sixteen-quarter table with revenue per head, gross profit per head, average headcount and the service/project split next to each other will answer most questions at a glance, and it belongs alongside the other measures in your financial dashboard.

Using It for Staffing Decisions

The legitimate staffing use is as one input among several. A hire is indicated when revenue per field employee has been rising for multiple quarters, utilization is high, booked backlog is extending, and overtime has stopped being occasional. That combination says demand is outrunning the crew you have.

Expect the metric to fall when you hire, and plan for it. A new field employee joins the denominator on day one and reaches full productivity months later, so the ratio dips before it recovers. The question to ask two quarters later is not whether the number dropped — it did — but whether it has begun climbing back toward where it was. A recovery means the addition was absorbed. A permanently lower plateau means you added capacity the demand did not support, or the person is not being developed. Both the hiring guide and the recruiting guide cover making that decision before the pressure forces it.

Using the metric in reverse — cutting staff to raise it — is almost always a mistake outside a genuine sustained downturn. Field employees are the hardest thing to replace in a tight labor market, and the ratio will look excellent right up until you cannot staff the work you win.

Common Mistakes

Comparing Against Published Benchmarks

Industry figures aggregate companies with incompatible mixes, geographies, and definitions. Your own trend is the only benchmark that survives scrutiny.

Changing the Denominator Mid-Stream

Including the working owner one year and not the next creates a movement that looks like performance and is not. Document the definition and hold it.

Ignoring the Gross Profit Version

Revenue per head alone will happily reward pass-through volume and thin-margin work. Always read the two lines together.

Reacting to a Single Month

One large invoice, one week of vacation, or one delayed billing swings a month enough to mislead. Decide on rolling and quarterly figures.

Blaming Crews for a Pricing Problem

A low number in a busy company is more often a rate problem than an effort problem. Check the rate before you address the crew.

Blending Service and Project Divisions

A combined figure mostly measures the mix between them. Split it wherever the data allows.

Monthly and Quarterly Review

Calculate it monthly, decide on it quarterly. The monthly reading exists so that a sharp move gets noticed within weeks rather than at year end; it should take a few minutes and produce a comment, not usually an action. Track it as a rolling twelve-month figure beside the monthly one so seasonality does not generate false alarms.

The quarterly review is where it earns its place. Look at four quarters of both versions of the metric, the average headcount behind each, the crew mix, and the revenue split between service and project. Then answer three questions: what moved, why, and does it change a pricing, staffing, or job-selection decision this quarter? Write the answer down, because next quarter's review is much faster when you can see what you concluded last time.

It belongs on the standing agenda rather than in an occasional deep dive. Most companies review it at the monthly financial close and discuss it properly once a quarter, with any resulting action assigned in the weekly management meeting where commitments get owners and dates. Alongside the other measures in the KPI guide, it gives you a compact answer to the question every growing contractor eventually asks: is this company getting better, or just getting bigger?

Frequently Asked Questions