Business KPIs and dashboard metrics field guide for electrical contractors

What a KPI dashboard is, and why the bank balance lies

A KPI dashboard is the short list of numbers that tell you whether the business is healthy, put in one place and looked at on a schedule. KPI stands for key performance indicator, which is a fancy way of saying the few measures that actually move with the health of the company. Not fifty numbers. The handful that, taken together, tell you whether you are making money, whether the work is coming in, whether the jobs are run well, and whether the cash will be there to make payroll.

Most contractors do not run a dashboard. They run on the bank balance. The account has money in it, so the business must be fine, and the account is getting thin, so something is wrong. The trouble is that the bank balance is the last signal to move and the worst one to steer by. It reflects what happened weeks ago, it mixes a customer deposit with earned profit, and it tells you nothing about which jobs made money or whether the pipeline behind you is full or empty. By the time the balance tells you there is a problem, the problem has been building for a month or a quarter.

A dashboard catches the same problem earlier, as a trend. Close rate slips for three weeks before booked revenue falls. Utilization sags before the labor line shows it. AR days creep before the account runs dry. Watch the leading numbers and you see the wave coming. Watch only the balance and you find out when it hits the beach. Two companion guides feed this one: the job-costing guide is where the per-job margin numbers come from, and the work-order guide is where the field and cash numbers are captured.

Why the numbers beat the gut

You manage what you measure, and a contractor who does not measure is managing on feel. Feel is not nothing. Twenty years on the tools builds an instinct worth listening to. But feel is slow, it is biased toward the loud problems, and it cannot tell you that your residential service margin has drifted three points over six months while the commercial side quietly carried the average. The numbers can.

The real payoff is timing. A red number on a dashboard is an early warning, and early is the whole game. Catch a close-rate slide in week two and you can fix the follow-up, retrain the salesperson, or chase the lead source before a slow quarter is baked in. Catch utilization falling and you can sell harder or trim a truck before you are paying for idle hours. The same problem found at year-end on the tax return is a lesson. Found on a weekly scorecard, it is a decision you still get to make.

Say it plainly: the bank balance is the worst dashboard a contractor can use, and it is the one most of them use. It moves last, it mixes earned money with money you still owe in work, and it points at the symptom long after the cause. Running the company on the balance is like driving by watching the gas gauge instead of the road.

What is the difference between leading and lagging indicators?

A leading indicator predicts where the business is going. A lagging indicator records where it has been. Revenue and net profit are lagging: by the time you can count them, the work is done and the result is locked in. Leads, quotes out, close rate, and backlog are leading: they tell you what next month's revenue is going to look like while you can still change it.

This is the part most dashboards get backwards. They are stuffed with lagging numbers, because lagging numbers are easy to pull off the financial statements, and then everyone stares at last quarter's profit wondering why they cannot affect it. You cannot. It already happened. The leading numbers are the steering wheel and the lagging numbers are the rear-view mirror, and you need both, but you drive with the one in front of you.

Pair them deliberately. Backlog and quotes out lead booked revenue, which leads billed revenue, which leads net profit. Utilization and first-time fix lead labor cost, which leads gross margin. When a lagging number goes soft, trace it back to the leading number that fed it, because that is the one you can still move. A dashboard that is all lagging numbers is a history book. A dashboard that watches the leading numbers is a tool you can actually steer with.

Pick the few that matter, not the fifty you could track

The fastest way to kill a dashboard is to put too much on it. Software will happily report a hundred metrics, and a contractor who tries to watch all of them watches none of them, because no human acts on a hundred numbers a week. The skill is not collecting metrics. It is choosing the few that drive the business and ignoring the rest.

For most trade contractors the meaningful set is five to ten numbers, not fifty. A workable core: booked revenue and close rate on the sales side, gross margin and net profit on the financial side, billable utilization on the operations side, and AR days, cash, and backlog on the cash and pipeline side. That is eight. Eight numbers you look at every week and actually act on beat a hundred-line report nobody opens.

The test for whether a metric belongs on the dashboard is simple: if it went red, would you do something about it? If the answer is no, it is not a KPI, it is trivia, and trivia dilutes the numbers that matter by burying them. Cut anything you would not act on. The dashboard is a decision tool, not a museum of everything the system can count.

Sales KPIs: leads, close rate, average ticket, booked revenue

Sales KPIs sit at the front of the business, and they are mostly leading indicators, which is what makes them worth watching. They tell you what is coming before it shows up as revenue. The four that carry the most are leads, close rate, average ticket, and booked revenue.

Leads are the count of opportunities coming in, the raw material everything downstream is made of. Close rate is how many quotes turn into signed work, quotes won divided by quotes sent, and it is the single most diagnostic sales number you have. Average ticket is revenue per job, and a rising ticket is good only if the margin holds, because selling bigger jobs at a worse margin is a way to grow yourself broke. Booked revenue is the dollar value of work you have signed but not yet performed, and it is the leading edge of next month's billed revenue.

Read them together, because each one explains the others. A high lead count with a low close rate points at pricing, follow-up, or lead quality, not a sales volume problem. A good close rate with falling leads is a marketing problem you will feel in sixty days. Booked revenue trending down while you are still busy is the early warning that the busy is about to end.

Financial KPIs: revenue, gross margin, net profit, overhead

Financial KPIs are mostly lagging, but they are the score, and you cannot ignore the score because you prefer the leading numbers. The four that matter are revenue, gross margin, net profit, and overhead as a percentage of revenue. Three of them are about profit, and only one is about size, which is the right ratio, because size without profit is just a bigger way to lose money.

Revenue is the top line, the total you billed. It is the number contractors brag about and the one that means the least on its own, because revenue with no margin is motion without progress. Gross margin is revenue minus the direct cost of the work, labor, material, equipment, and subs, expressed as a percentage, and it tells you whether the jobs themselves make money. Net profit is what is left after overhead comes off too, and it is the only number that says whether the company makes money. Overhead percentage is indirect cost divided by revenue, and it is the quiet killer, because an eight-point swing in overhead is an eight-point swing in net profit at the same gross margin.

Where these numbers come from is the per-job costing covered in the job-costing guide. The dashboard rolls up what that discipline captures one job at a time. If the jobs are not costed with burdened labor and allocated overhead, the financial KPIs are decorated guesses, and a confident guess is worse than no number at all.

What is a good gross margin for a contractor?

Gross margin is the percentage of each revenue dollar left after the direct cost of the work, and it is the clearest single measure of whether the business is healthy. As a reference, residential service electrical work often runs 40 to 55 percent gross at well-run shops, while competitively bid commercial and new-construction work often runs 25 to 35 percent. Those are ranges to orient by, not targets to hold yourself to, because the right number depends on your work mix, your market, and your cost structure.

Gross margin is the health number because it sits upstream of everything. Overhead and net profit both come out of it, so a thin gross margin leaves nothing to cover the office, the trucks, and the owner's pay, no matter how lean the overhead. A contractor at 25 percent gross with 18 percent overhead is making 7 points and one bad job from a loss. The same overhead on 45 percent gross is a comfortable business.

Two cautions. First, your own trend matters more than any published benchmark, because the benchmark does not know your mix. A margin sliding from 42 to 36 over three quarters is a problem even if 36 looks fine against someone else's average. Second, gross margin by job and by division tells you far more than the company-wide average, which hides a money-losing line behind a profitable one. The job-costing guide is where that per-job and per-division margin gets built.

Operations KPIs: utilization, first-time fix, callbacks, throughput

Operations KPIs measure how well the field runs, and they are mostly leading indicators of the labor cost that drives gross margin. The four that earn their place are billable utilization, first-time fix rate, callback rate, and throughput, usually jobs per day or per tech.

Billable utilization is the share of paid field hours that land on billable work, and it is the biggest lever on labor profitability there is. A range of 60 to 80 percent is generally considered strong, with top shops sustaining 75 to 85 percent without burning people out. Every point of utilization you lose is paid hours producing no revenue. First-time fix rate is the share of jobs resolved in one trip, commonly cited around 80 percent industry-wide, with best-in-class operations above 89 percent, and every job that needs a second visit is a truck roll you eat. Callback rate is the inverse signal, the share of jobs that come back for rework, and it points at quality, training, or rushed work. Throughput is how many jobs a tech completes in a day, and it is only useful read alongside margin, because fast cheap work that loses money is not productivity.

These numbers come off the work orders. The work-order guide covers capturing the hours, the first-time fix, and the callbacks on the ticket itself; the dashboard is where those captured numbers roll up into a picture of whether the field is running tight or loose.

Cash KPIs: AR days, cash on hand, WIP, current ratio

Cash KPIs answer the question that actually ends companies: not are you profitable, but will the money be there when payroll runs. A contractor can be profitable on paper and still go under because the cash is tied up in receivables and unbilled work. The four to watch are AR days, cash on hand, WIP, and the current ratio.

AR days, also called DSO or days sales outstanding, is the average number of days it takes to collect after you bill. The target is near your payment terms, so on net-30 terms a DSO drifting past the high 30s into the 40s is money sitting in someone else's account. A common rule is that when DSO runs more than about 25 percent over your terms, you have a collections problem, not a customer problem. Cash on hand is the buffer, often measured in weeks of payroll covered, and a contractor with less than a few weeks is one slow-paying customer from a crisis. WIP, work in progress, is the gap between work performed and work billed, and chronic underbilling means your cash is financing the customer's project. The current ratio is current assets over current liabilities, with roughly 1.5 to 1.6 commonly held as healthy in construction.

WIP and the balance-sheet ratios sit at the seam between the dashboard and the books, so set the exact treatment up with your accountant. The field data feeds them; the accountant makes them tie out.

What is backlog?

Backlog is the signed work you have not yet performed, measured in dollars or, more usefully, in how many weeks or months it would keep the crews busy. It is one of the strongest leading indicators a contractor has, because it tells you today what revenue is already committed for the weeks ahead, before you have billed a dollar of it.

Backlog is a staffing signal and a pipeline signal at once. Too little and you are about to have idle crews and a revenue gap, with no time to sell your way out of it. Too much and you are turning away work, stretching lead times, and risking the quality that comes from a crew that is buried. For project contractors a common comfort zone is several months of backlog, with industry surveys often landing in the range of six to nine months, while a service business thinks in weeks of scheduled work rather than months. The right number depends on your trade, your crew size, and how fast you can hire.

Watch the trend more than the level. Backlog shrinking for a few weeks running is the earliest warning that a slow season is coming, early enough to push sales while you still have runway. Backlog growing past what you can staff is a hiring decision you should make before the schedule slips, not after a customer complains. The number is only useful if you look at it before it becomes a problem you can feel.

A number without a target is trivia

A KPI with no target is just a fact, and facts do not drive decisions. Gross margin is 34 percent. Is that good? You cannot say until there is a target next to it. Set a target for every number on the dashboard, because the target is what turns the number from a reading into a verdict, green or red, act or leave it alone.

Build the target from three sources, weighted toward the last one. Industry reference ranges give you a sanity check on where you sit. Your own history gives you a realistic next step, because a shop at 32 percent gross does not target 50 next quarter. And your cost structure sets the floor, because you can calculate the gross margin you actually need to cover overhead and leave a profit, and that number is not negotiable with the market. The target that matters most is the one your own books say you need to survive.

Make the targets specific and visible. Close rate target 40 percent. DSO target under 35 days. Utilization target 75 percent. When the number and the target sit side by side on the dashboard, a red cell is unmistakable and a green one is earned. A dashboard of bare numbers with no targets sends everyone to argue about whether 34 percent is good. A dashboard with targets ends the argument and starts the fix.

Review on a cadence, or the dashboard is wallpaper

A dashboard you do not look at is useless, and the difference between a tool and wallpaper is the review cadence. Different numbers move at different speeds, so they get looked at on different clocks. Match the cadence to how fast the number changes and how fast you can act on it.

Three rhythms cover most contractors. Daily, you glance at the operational pulse: jobs scheduled, techs dispatched, anything stuck or behind, the cash position if it is tight. Weekly, you run the scorecard: booked revenue, close rate, utilization, AR days, backlog, the leading numbers you can still steer this month. Monthly, you sit with the financials: revenue, gross margin, net profit, overhead, the lagging numbers that grade the period that just closed. The weekly scorecard is the one that earns its keep, because it is frequent enough to catch a problem while it is still small and slow enough not to be noise.

The cadence only works if it is a standing commitment, not a thing you do when you remember. Put the weekly review on the calendar, run it the same way every time, and act on what it shows. A red number that gets noted and not acted on trains everyone to ignore the dashboard. The review is where the numbers turn into decisions, and a number that never gets reviewed never turns into anything.

Garbage in, garbage out: the dashboard is only as good as the data

Every number on the dashboard is downstream of data captured somewhere in the field, and if that capture is sloppy, the dashboard is confidently wrong. A gross margin built on labor hours reconstructed from memory on Friday is fiction. A utilization rate built on time that was never clocked to a job is a guess. The most dangerous dashboard is not the one with no numbers. It is the one with precise-looking numbers built on bad data, because it gets trusted.

The three feeds that have to be clean are job cost, time, and the work order. Job cost has to capture burdened labor and allocated overhead, the discipline the job-costing guide covers, or every margin number is overstated. Time has to be clocked to the job as it happens, or utilization and labor efficiency are made up. The work order has to capture the parts, the hours, the first-time fix, and the sign-off on site, the discipline the work-order guide covers, or the operations and cash numbers are full of holes.

This is where a field tool the crew actually uses pays off. FieldOS puts the work order, the time clock, and the material logging on the tech's phone, so the hours land on the right job, the parts get recorded as they come off the truck, and the captures happen at the moment the work happens instead of in a Friday reconstruction. The dashboard is only as honest as that capture, and capture at the source is the only version that comes out true.

A scorecard by role, not one number for everyone

The company dashboard tells the owner whether the business is healthy. It does not tell a tech what to do differently tomorrow. For the numbers to change behavior, each role needs its own scorecard, the few numbers that person actually controls, because a number you cannot influence is noise to you and a number you own is a target.

Cut the numbers by who moves them. A field tech owns utilization, first-time fix, callbacks, and hours against estimate, because those are set by how the tech works. A salesperson or estimator owns close rate, average ticket, booked revenue, and bid margin, because those are set at the sale. A project manager owns gross margin by job, schedule, WIP, and change orders, because those are set in how the job is run. A service manager owns days to invoice, AR days, jobs per day, and backlog. The owner owns the company numbers: net profit, cash, overhead, and total backlog.

Giving each role its own scorecard does two things. It makes the number actionable, because the person looking at it can actually move it, and it makes accountability clear, because there is no hiding a red number inside a company average when it has your name on it. A foreman who consistently beats the hours estimate should see that and get recognized. One who consistently blows it should see that and get coached. The role scorecard is what makes that possible.

A red number is an action, not a report

The point of a dashboard is not to know the numbers. It is to do something when one goes wrong. A red number that triggers no action is a report, and a report changes nothing. The whole value of measuring is the decision the measurement forces, and a dashboard that gets reviewed and never acted on is an expensive way to feel informed.

Build the action into the review. When a number goes red, name the cause and assign the fix to a person with a date, the same way you would handle a failed inspection. Close rate dropped: who is calling the dead quotes back, by when. DSO climbed: who is working the aging report this week. Margin slipped on a job type: pull the job costs and find which cost code blew out. The red cell is the start of a task, not the end of a meeting.

The failure mode is the standing review where the same number has been red for three months and everyone has stopped seeing it. Once a red number becomes furniture, the dashboard is dead, because the team has learned that red means nothing. Either the number gets fixed or the target was wrong and needs resetting. What it does not get to do is sit there red and ignored, because that teaches everyone to ignore the next one too.

Vanity metrics: revenue without margin

A vanity metric is a number that looks impressive and drives nothing, and the classic in the trades is revenue without margin. Revenue is the number contractors put on the truck and brag about at the supply house, and it is close to meaningless on its own, because you can grow revenue every year and lose more money every year by selling unprofitable work faster.

The tell of a vanity metric is that it goes up when you do something that makes the business worse. Cut prices to win more bids and revenue climbs while margin craters. Add trucks to chase volume and total jobs per week rises while utilization and net profit fall. Total leads, total jobs, hours worked, social media followers: all of them can look great while the business gets sicker, because none of them is tied to profit.

The fix is to pair every volume number with a quality number and watch the pair, never the volume alone. Revenue with gross margin. Jobs per day with margin per job. Leads with close rate. Average ticket with the margin on those tickets. When the volume number rises and the quality number holds, that is growth. When the volume rises and the quality falls, that is a contractor working harder to make less, dressed up as success. Track what drives profit, and let the impressive-but-empty numbers go.

Benchmark against the industry, but trust your own trend

Industry benchmarks are useful for one thing: a rough sense of whether you are in the right neighborhood. If well-run residential service shops run 40 to 55 percent gross and you are at 22, the benchmark just told you something real, that your pricing or your cost capture has a problem worth chasing. As a sanity check on where you sit, the published ranges earn their place.

But benchmarks are blunt, and leaning on them too hard misleads you, because no benchmark knows your work mix, your market, your wage rates, or your overhead structure. A shop doing mostly competitive commercial bid work and a shop doing mostly residential service have different margin realities, and comparing either to a blended industry average tells you little. Treat a benchmark as a hypothesis to test against your own numbers, not a grade to be assigned.

Your own trend is the comparison that matters most. A margin moving from 42 to 36 over a year is a problem even if 36 beats the industry average, and a margin climbing from 28 to 33 is a win even if it still trails. The question that drives decisions is not how you compare to a survey, it is which direction your numbers are moving and how fast. Benchmark to orient, trend to steer, and when the two disagree, trust the trend, because the trend is measuring your actual business and the benchmark is measuring someone else's.

Automate the dashboard from the system, not a month-late spreadsheet

A dashboard built by hand in a spreadsheet is a dashboard that is always late and often wrong. Someone pulls numbers from the time system, the accounting package, and a stack of work orders, types them into a sheet, and by the time it is done the month is over and the data is stale. A KPI you see thirty days after it went red is not an early warning, it is a slightly faster autopsy.

The version that works is a dashboard the system builds itself, live, from the data captured as the work happens. When the time, the work orders, the material, and the invoicing all live in one place, the numbers roll up on their own and the dashboard is current to today, not to last month's close. That is the difference between steering with the road in front of you and steering with a photo of the road taken in April.

FieldOS is built to be that source on the field side. Techs clock to the job, run the work order, and log material on the phone, so utilization, first-time fix, days to invoice, and the per-job cost data are captured live and roll into the dashboard without anyone re-keying a spreadsheet. Pair the field capture with your accounting system for the financial and balance-sheet numbers, and the scorecard you review on Monday reflects the work that happened Friday, not a number someone reconstructed three weeks later.

Even a one-truck shop needs five numbers

A small contractor often thinks dashboards are for big companies, and skips the numbers entirely until a cash crunch forces the issue. That is backwards. A one or two-truck shop has less cushion to absorb a bad month, so the early warning a dashboard gives is worth more, not less. The difference is that a small shop should start with five numbers, not fifteen.

The starter five for a small contractor: gross margin, so you know the jobs make money; booked revenue or backlog, so you know work is coming; AR days, so you know the money is being collected; cash on hand, so you know you can make payroll; and close rate, so you know the sales effort is working. Those five, looked at weekly, tell a small shop almost everything it needs to steer, and they fit on an index card.

The point is to start simple and start now, not to wait until you can afford a complicated system. FieldOS gives a small shop the field capture, time clocked to the job and work orders run from the phone, that feeds those five numbers without a bookkeeper assembling them by hand. Five numbers reviewed every week beats a perfect dashboard you keep meaning to build. Start with the five, add to them as the shop grows, and you will be running on the numbers while your competitors are still running on the balance.

How the dashboard fails in practice

The failures are predictable, and they are almost never about the math. They are about discipline, focus, and follow-through.

Running on the bank balance is the first and most common, the contractor who watches the account instead of the leading numbers and finds out about every problem a month late. Tracking too many metrics is the second, the hundred-line report nobody reads, which buries the few numbers that matter under the many that do not. Tracking vanity metrics is the cousin of that, watching revenue climb while margin falls. Numbers with no targets is the third, a dashboard of bare readings where nobody can say whether 34 percent is good or bad. No review cadence is the fourth, the dashboard that exists but never gets looked at on a schedule, so a red number sits unnoticed for a quarter. Dirty data is the fifth, precise-looking numbers built on time reconstructed from memory and parts that never got logged, trusted because they look exact. And a red number with no action is the sixth, the standing review where the same cell has been red for months and everyone has stopped seeing it.

Each one on its own quietly defeats the dashboard. Stacked, they produce a contractor with a screen full of numbers who is no better informed than one with none, because every signal is either wrong, ignored, or buried. The fix for all six is the same shape: pick the few that matter, set a target and a cadence, keep the data clean at the source, and act on the red.

The core dashboard at a glance

A working contractor dashboard fits on one screen and covers the sales, financial, operations, and cash sides without sprawling. The set below is a starting point, not a mandate, because the right numbers depend on your trade and your work mix. The discipline is to keep it short, set a target on every line, and look at it on a cadence.

Read the table as the few that earn a permanent spot. Add a number only when it would change a decision, and cut one whenever you find yourself skipping past it every week.

Common mistakes

• Running on the bank balance, the last and worst signal, instead of the leading numbers that move first.
• Tracking fifty metrics or vanity numbers like revenue without margin, so the few that matter get buried.
• Putting numbers on the dashboard with no target, so nobody can tell green from red.
• Having no review cadence, so the dashboard exists but a red number sits unnoticed for a quarter.
• Feeding the dashboard dirty data, time reconstructed from memory and parts never logged, then trusting it because it looks precise.
• Letting a red number trigger no action, until the team learns that red means nothing.
• Comparing only to industry benchmarks and ignoring your own trend, which is the comparison that actually steers.

Field checklist

Practice and references

Running a business on KPIs is a management practice, not a code-driven one, so the references here are methods to set up with your books and your team rather than enforceable standards. The leading-versus-lagging distinction and the discipline of choosing a meaningful few rather than tracking everything come from standard performance-management practice, and they hold across trades. The framework is simple to state and hard to keep: pick the few numbers that drive the business, set a target and a cadence for each, and act on the ones that go red.

The financial and operational reference ranges in this guide come from construction and field-service industry benchmarks, and they should be treated as orientation, not targets. Gross margin, net profit, overhead, utilization, first-time fix, DSO, backlog, and the balance-sheet ratios all vary with trade, work mix, market, and company size, so confirm where you sit against your own history and your own cost structure before you judge a number good or bad. Where a metric touches the financial statements, the WIP treatment, the balance-sheet ratios, and revenue recognition, set the exact definitions up with a construction-literate accountant so the dashboard and the books agree.

Three things hold across every version of this. Pick the meaningful few rather than the impressive many. Set a target and a review cadence, because a number without either changes nothing. And keep the data clean at the source, because the dashboard is only as honest as the capture under it. Get those three right and the specific list of numbers can flex to fit your business.

Terms and definitions

KPI work carries its own vocabulary, and the same idea shows up under different names across a dashboard, an accounting package, and a banker's request. The terms below are the ones that matter when you build and review the scorecard.

A KPI is also called a metric or a measure. AR days is also written DSO, days sales outstanding. Backlog is sometimes called signed or committed work. Gross margin and gross profit refer to the same thing expressed as a percent or a dollar figure. Whatever the label, the discipline is the same: a short list of numbers, each with a target, reviewed on a cadence, acted on when it goes red.

KPI

Key performance indicator: one of the few numbers that move with the health of the business

Leading vs lagging

Leading numbers predict (leads, backlog, close rate); lagging numbers record (revenue, net profit)

Gross margin

Revenue minus direct cost (labor, material, equipment, subs), as a percent of revenue

Net profit

What is left after overhead comes off gross margin; the company's true profit

Billable utilization

Share of paid field hours that land on billable work

AR days (DSO)

Average days to collect after billing; days sales outstanding

Backlog

Signed work not yet performed, measured in dollars or weeks of work ahead

Vanity metric

A number that looks impressive but drives no decision, such as revenue without margin

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is job costing?
• What is a work order?
• How do contractors get paid faster?
• What is cash flow management?
• What is a WIP schedule in construction?