Electrical Dispatch Software: The Utilization Test

Electrical scheduling and dispatch software is worth buying only if it moves one number: the share of your paid electrician hours that end up on an invoice. Published field service benchmarks put the average at 55 to 60 percent, with top performers at 75 to 80 percent, according to utilization benchmarks compiled by FieldEdge and technician utilization definitions from Attainment.

Nobody in a software demo will ask you for that number. They will show you a drag-and-drop board and a map with truck icons on it.

That is the whole problem with how this category gets sold. The dispatch board is the visible part, so it is the part vendors compete on. It is almost never the constraint. The constraint is that a licensed electrician you are paying for eight hours is billing for four and a half of them, and a calendar does not know why.

Start with the number the demo will never ask for

Utilization is billable hours divided by paid hours. If you pay an electrician for a 2,080 hour year and 1,200 of those hours land on customer invoices, you are at 58 percent, which is dead average.

Here is why that matters more than any feature comparison. A residential service electrician in Tennessee posted his overhead math to r/electricians in July 2025, working out that he needed roughly $311 per billable hour to stay solvent. The key line is buried in the calculation: he divided by 1,000 billable hours per technician per year and called it "about a 50% efficiency score."

A commenter in the same thread, running a four electrician shop in the northeast, did the identical calculation with a different divisor. He spread roughly $300,000 of annual overhead across 2,080 hours per man and arrived at about $105 per man hour of cost.

Same trade, same arithmetic, roughly double the answer. The difference is not pricing philosophy. It is an assumption about how much of the day is billable, and neither owner had a system that measured it.

Write your current number down before you take a single demo. If a platform cannot show you that number after twelve months, you have no way to know whether it worked.

Why electrical dispatch is not HVAC dispatch

Most software sold as "electrical dispatch software" is a general field service platform with the word electrical in the page title. The dispatch engine was designed around an HVAC or plumbing service call: one technician, one address, one visit, two hours, done. Electrical service work breaks that model in three specific ways, and how a platform handles them is the actual buying decision.

Your dispatchable unit is a licensed pairing

Most field service software models a technician as an interchangeable resource with skill tags attached. Electrical work does not permit that, because supervision ratios are set in law and they vary sharply by state.

Massachusetts regulation holds that a journeyman shall have no more than one apprentice under direct supervision. Utah allows two apprentices per journeyman on residential work but drops to one to one on commercial. Oregon and Washington require one to one direct supervision. Maine and New York use a stepped structure, requiring one journeyman for the first apprentice and three journeymen for each additional one, per a Connecticut General Assembly comparison of neighbouring state apprenticeship ratios.

The consequence for your dispatch board: an apprentice showing as "available" at 10am is not dispatchable alone. The free resource on the calendar is a legally invalid one. Across a shop with two journeymen and three apprentices, the number of valid crew combinations is far smaller than the number of open slots.

Nearly every tool in this category expresses this only as a skill tag and a manual habit. Ask in the demo whether the system can prevent an invalid pairing from being booked, or whether it just colours the box differently.

You do not own half of your schedule

The second calendar in an electrical business belongs to your local authority having jurisdiction, and you have almost no control over it.

Rough-in inspections must be called before drywall goes up, commonly with 24 to 48 hours notice. Availability is not uniform. PermitFlow's contractor guide to electrical permits and related jurisdiction guidance describe urban areas running two to five day waits during busy construction season, rural jurisdictions inspecting only one or two days a week, and last minute requests pushing out as far as two weeks where inspector availability is thin.

Then there is the failure case. A failed rough-in generates a re-inspection that has to be booked into the same constrained queue, holds a general contractor's drywall crew, and consumes an electrician's half day at a site where nothing billable happens.

This is the gap in every dispatch board demo. The board shows you jobs you scheduled. It does not show the appointment you are waiting on from someone else, and it usually does not create the re-inspection task automatically when an inspection fails. If you do new construction or any permitted work, that automation is worth more than route optimisation.

Electrical job time varies more than the pricebook assumes

The third constraint is the one that quietly kills software implementations, and it is the reason so many electrical contractors abandon platforms that other trades love.

A 40 year old service only electrical company with 26 employees laid this out in a detailed r/electricians post. The owner, who describes himself as an engineer and MBA used to running real ROI justifications, wrote that his company had "tried switching over to 3 different software platforms (Service Titan, FieldEdge, and 360e) and we have cancelled each one soon after."

His reasons are worth quoting because they are not the reasons vendor comparison pages anticipate. Cost was one. The other was structural: "Some of this comes from the feeling of being forced to change our business model to THEIR model."

The model in question is flat rate. And his objection is a genuinely electrical one. In a follow up comment he gave the arithmetic:

"Fish a wire down a wall? Easy and 15 minutes maybe, if that. Does the wall have fireblock and blown in hardened insulation solid as a rock? Possibly 2 hours and drywall repairs. We don't want to have to charge 2 hours labor to fish all wires down a wall 'just in case'."

That is an eight to one duration spread on a single task, driven entirely by what is behind a wall you cannot see when you price the job. A flat rate pricebook has to price near the worst case to survive, which is exactly how you end up with the pricing the same owner encountered as a customer: an $840 invoice for a 100 amp main breaker swap that dropped to $430 the moment he questioned it.

Flat rate works fine in trades with tighter duration variance. It fits electrical service worse, and platforms that assume it will be adopted are selling you a pricing model with a dispatch board attached. That is a legitimate reason to walk away from an otherwise capable tool. Our take on the pricing question itself is in flat rate vs hourly pricing for contractors.

What electrical contractors actually paid

Vendor pages are silent on price and comparison listicles quote MSRP. Operators quote what they were actually offered. The most useful data point comes from an electrical contractor with 12 field employees and one office employee, doing 99 percent new construction residential, who ran demos with three vendors and posted the quotes: roughly $300 to $400 a month for Jobber, roughly $600 a month for FieldPulse, and roughly $1,500 a month for ServiceTitan at his business size.

Published tiers line up with the lower two. Jobber's Core plan is commonly listed at $49 a month for a single user with Connect and Grow tiers stepping up and per user fees on top. Housecall Pro publishes Basic near $59 to $79, Essentials near $149 to $189 and MAX near $299 to $329, with user counts bundled into each tier. Another electrician in a 2026 thread confirmed running Housecall Pro Essentials at $189 a month and being satisfied with it.

ServiceTitan does not publish pricing. Independent 2026 cost analyses place it at roughly $245 to $500 per technician per month with implementation fees between $5,000 and $50,000 and an onboarding period measured in months rather than weeks.

The pattern is consistent enough to state plainly: below roughly ten technicians, the enterprise tier rarely survives contact with an ROI calculation. A contractor who left ServiceTitan in 2026 put it flatly: "for the cost we were extremely disappointed with the support and the workflow just really did not work for us."

The ratio that tells you whether it worked

Here is the test almost nobody applies. Dispatch software is sold on administrative efficiency, so measure administrative efficiency: office staff per field electrician.

An r/electricians thread from a technician at a shop with 9 field technicians and 9 office staff drew a stream of operator responses with their own ratios. The numbers are more useful than any vendor case study because nobody was selling anything.

The top rated reply to the 9 and 9 shop was blunt: "50% of the companies staff is non revenue producing. That's not good." Another operator suggested "a 1 to 2 person office staff MAX" for nine field electricians.

Note the direction of the effect the original poster described. His shop had implemented new field service management software, and work moved onto the technicians rather than off the office: "The new software has us changing statuses constantly, estimating (flat rate), doing the work, collecting the payment, updating the notes." Office headcount stayed put.

That is the failure mode to guard against. Dispatch software can shift administrative labour from the office to the field, which looks like adoption on a dashboard and shows up as lower utilization on the invoice. Your technicians are now doing data entry at $110 an hour of loaded cost.

So set the target in writing before you sign. If you are at 3 field electricians per office person and the software is meant to get you to 5, the ratio moves within twelve months or the tool did not do its job. If your problem is upstream of dispatch, see signs you have outgrown your CRM.

Four tests to run before you sign

Feature grids are useless here because every platform in this category has a dispatch board, a mobile app, GPS tracking and a QuickBooks sync. Test the four things that actually differ.

1. The invalid pairing test. In the trial, try to book an apprentice alone on a job in a state with a one to one supervision rule. Does the system stop you, warn you, or happily schedule it? If it schedules it, your licensing compliance still lives entirely in a dispatcher's head, and you should price the tool accordingly.

2. The failed inspection test. Mark a rough-in inspection as failed. Does the platform automatically create a re-inspection task, hold the downstream schedule, and flag the general contractor notification? Or does the job simply sit there marked failed until someone notices? This is the single biggest difference between a production system and a calendar.

3. The time and materials test. Invoice a real T and M job end to end, with materials added from the truck. If the workflow fights you, or T and M is clearly a second class path bolted next to a flat rate pricebook, you have found the reason shops cancel these platforms in month four. Test it before you migrate three years of job history.

4. The bad week test. Run the trial through a genuinely bad week, not a quiet one. A storm, a callback cluster, a sick journeyman, an inspector who fails you on a Friday. One contractor migrating off ServiceTitan recommended running both systems in parallel on a subset of jobs for 30 days and only cutting over when the new tool stops dropping work, because migrating off is messier than migrating on.

A fifth check costs nothing: ask what a data export actually contains. Job history, photos, invoices and customer notes are the asset. If the export is a customer list and nothing else, you are not buying software, you are renting your own operating history.

Where a custom build actually earns its keep

Buy off the shelf first. That is the right default for most electrical shops, and anyone telling you otherwise is selling something.

A custom system earns its keep in one situation: when a constraint of your business cannot be modelled in any platform you have trialled, and the workaround costs you real billable hours every week. In electrical that is usually licensing logic your state enforces and your software does not understand, a genuine dual schedule where a service board and a construction schedule compete for the same electricians, or a billing structure a flat rate pricebook cannot express.

If none of those describe you, an off the shelf tool you actually use beats a bespoke one you have to maintain. If one of them does, you already know, because you are the shop that trialled three platforms and kept the spreadsheet. More on that threshold in custom CRM vs off the shelf CRM, and the trade version in CRM for electricians.

The bottom line

Electrical scheduling and dispatch software is a genuinely good purchase when it converts unbilled hours into billed ones. It is a bad purchase when it converts office admin into field admin, which is the more common outcome and the harder one to notice.

Three numbers decide it, and you can gather all three this week without talking to a vendor. Your current technician utilization, so you have a baseline. Your field electricians per office person, so you have an ROI target with a deadline on it. And your realistic monthly ceiling, priced at the headcount you expect next summer rather than the one you have today.

Then buy for the constraints that are specific to your trade rather than the ones on the feature grid. Licensing ratios that make a free electrician undispatchable. An inspection queue you do not control and a failed rough-in that has to generate its own follow up. And a pricing model that fits how you actually bill, because the fastest way to abandon a platform is to discover in month four that it assumed you would change how you charge.

The shop that knows on Monday morning which technicians are legally dispatchable, which jobs are waiting on someone else's calendar, and what percentage of last week was billable does not need a better dispatch board. It already has the thing the dispatch board was supposed to give it.