How to Improve Electrical Contractor Dispatch and Scheduling

In most electrical companies, the schedule is a calendar someone fills in as calls come in. Jobs get placed where there is space, technicians get sent where the next customer is, and the day is considered successful if everyone was busy. Busy, though, is not the same as billable — and the gap between the two is where a surprising amount of margin quietly goes.

A crew of four working full days can produce very different amounts of invoiced labor depending on how the day is built. Travel between jobs on opposite sides of the service area, a technician waiting on a part, a callback that consumes an afternoon, a two-hour window missed by ninety minutes — none of these show up as a loss anywhere. They show up as hours you paid for that no customer paid you for.

This guide covers how to move dispatch from a reactive calendar to a capacity-management system: intake, prioritization, routing, skill matching, duration accuracy, buffers, communication, utilization and the daily and weekly reviews that keep it working.

From Calendar to Capacity

A calendar answers "when is this job?" A capacity system answers a harder set of questions: how many productive hours does the company actually have this week, how many are already committed, which of them are at risk, and what is the best use of the ones that remain?

That connection is worth sitting with. When you calculated what to charge, you divided loaded labor cost and overhead across an assumed billable-hour count. If the schedule delivers fewer billable hours than the model assumed, the effective rate falls below the one you priced — even if every individual job came in on estimate. Dispatch is therefore a pricing function as much as an operational one.

The shift in mindset is from filling slots to protecting productive hours. Every decision — which job goes where, who takes it, how long it is allotted, what the customer is told — either adds to or subtracts from the hours that reach an invoice.

Intake Quality

Nearly every scheduling failure can be traced to a call that was taken badly. If the information captured at intake is thin, the dispatcher is guessing about duration, skill and materials, and the technician discovers the truth on site.

Intake should reliably capture:

• The actual problem in the customer's words, plus enough detail to categorize it
• Property type, age and panel or service details where relevant
• Whether power is out, partially out, or the issue is non-urgent
• Access constraints — gates, tenants, business hours, someone who must be present
• Whether this is a new issue, a repeat of a prior problem, or a callback on your work
• The decision-maker and how to reach them, not just whoever called
• Any prior quote, work order or project this connects to

A structured intake script, even a one-page one, reliably outperforms experienced improvisation because it does not degrade on a busy morning. The dispatcher's job becomes far easier when the ticket in front of them describes a job rather than a symptom.

Intake quality also determines whether the lead converts at all. Response speed and qualification are covered in the electrical sales process guide — the same call that books the job creates the data dispatch runs on.

Job Prioritization

Not all work deserves the same place in the queue. Without a stated priority rule, jobs get scheduled in the order they were requested, which means the loudest customer displaces the most valuable one.

Useful dimensions for a simple priority framework:

• Safety and urgency. Hazards and no-power conditions come first, ahead of both convenience and revenue.
• Commitments already made. A scheduled appointment is a promise; moving it has a cost even when it is invisible on the calendar.
• Customer relationship. Maintenance agreements, repeat commercial accounts and referral sources represent future revenue, not just this ticket.
• Job economics. Work that fits your crew's strengths and your pricing model earns its slot over work you take reluctantly.
• Schedule efficiency. A job near an existing commitment costs fewer non-billable minutes than an identical job across town.

Write the rule down, even informally. The point of a priority framework is that decisions stay consistent when the phone is ringing and the person deciding is stressed.

Service vs Project Scheduling

These are two different scheduling problems and mixing them without acknowledgment is a common source of chaos.

Service scheduling

Service work is high-volume, short-duration and geographically scattered. Success is measured in jobs completed per day, travel minimized and windows met. Service scheduling is dynamic — it changes during the day and needs someone actively managing it.

Project scheduling

Project work is longer, planned further out, and dependent on other trades, inspections and material deliveries. Success is measured in crew continuity and staying on the planned hours. Project scheduling is about protecting committed blocks of time from interruption.

The friction appears when service demand raids project crews. Pulling an electrician off a project for a service call costs more than the hours moved: it costs setup, context and often project schedule. Companies doing both work types benefit from some structural separation — dedicated service capacity, defined rules about when project labor can be borrowed, and honest accounting of the cost when it happens.

Emergency Work

Emergency calls are unpredictable individually and highly predictable in aggregate. Over a few months you can see roughly how much of your capacity urgent work consumes — which means it can be planned for rather than absorbed by disruption.

Common approaches, each with trade-offs:

• Hold open capacity in each day, sized to your observed emergency volume
• Designate a technician or rotation that takes urgent work as the primary assignment
• Schedule non-urgent work with enough slack that it can absorb displacement
• Define in advance which job categories may be moved, and who calls the affected customer

The last point is the one most often skipped. Emergencies damage customer relationships not because appointments move but because nobody proactively tells the displaced customer. A rule that says who makes that call, and how quickly, converts a broken promise into a managed one.

Geographic Routing

Travel time is the largest category of paid, non-billable hours in most service companies. It is also the one most improved by simple sequencing discipline.

The core practice is clustering: group each technician's day within a geographic area rather than dispatching purely by call order. A day with four jobs in one quadrant produces materially more billable time than the same four jobs scattered across the service area, with no change to the work itself.

Practical routing habits:

• Assign loose geographic zones and default technicians to their zone
• Sequence the day to minimize backtracking, accounting for traffic patterns by time of day
• When a new call arrives, ask which technician is already nearest before asking who is free
• Start the day at the outer edge and work inward, or the reverse — whichever fits your area's traffic
• Treat a long drive as a real cost when deciding whether to take a job at all

None of this requires routing software. It requires someone thinking about geography at the moment jobs are assigned rather than after the truck is moving. And since every mile has a measurable cost, routing decisions are also fleet decisions — the fleet management guide covers cost per mile and vehicle utilization in detail.

Technician Skill Matching

Sending the wrong person costs twice: the job takes longer than it should, and it may need a second visit. Sending your most capable technician to routine work costs differently — the capability is available but idle where it was needed.

A dispatcher needs a working picture of what each technician can handle independently: troubleshooting depth, service-panel work, commercial systems, controls, code familiarity, and comfort with the customer-facing side of the job. In a small company this lives in the owner's head; as the company grows it needs to be written down, because dispatch decisions get made by people who did not train the crew.

Skill matching should also be developmental. Deliberately pairing a newer electrician with work slightly beyond their comfort zone, with support available, is how capacity grows. The structured version of that is covered in how to onboard a new electrician, and who to bring on in the first place is addressed in when to hire your first electrician.

Appointment Windows

An appointment window is a promise, and customers judge you on it more than they judge the wiring. The tension is real: narrow windows sell better, wide windows are easier to keep.

The resolution is to set windows from your own data instead of from hope:

• Measure how often you actually arrive within the window you promise
• Widen windows where you consistently miss, rather than repeating the miss
• Use narrower windows only for first appointments of the day, which are the most controllable
• Pair the window with an en-route notification — accurate real-time information beats a narrow promise
• When you will miss, call before the window closes, not after

A company that keeps a four-hour window ninety-five percent of the time generates fewer complaints than one that keeps a two-hour window sixty percent of the time, and it spends far fewer office hours managing the fallout.

Travel Time

Travel deserves explicit treatment because it is usually invisible in scheduling and entirely visible in the payroll. If your schedule allots two hours for a job that takes two hours of work plus fifty minutes of driving, the schedule is wrong every single day.

Handle it directly:

• Schedule travel as time, not as an assumption absorbed into the job duration
• Track average travel time per job as an operating number
• Know how travel is treated in your pricing — whether it is recovered in the rate, in a trip charge or in a minimum
• Watch service-area creep: jobs accepted well outside your zone are usually less profitable than they appear

How travel and diagnostic time get recovered in what you charge is covered in how to price an electrical service call.

Job-Duration Estimates

Scheduled durations are the foundation everything else rests on. If they are wrong, routing is wrong, windows are wrong, utilization targets are wrong and the day cascades.

Most companies estimate duration by feel, and feel is systematically optimistic. The fix is to build durations from completed-job data by work type — actual on-site hours for panel changes, troubleshooting calls, fixture installs, service upgrades and so on. That data already exists if you are job costing.

Track the variance between scheduled and actual duration the same way you track cost variance. Where a particular job type is consistently over, adjust the standard. Where a particular technician is consistently over, that is a training conversation, not a scheduling one. The framework for this is in electrical job costing, and the job cost calculator shows estimated versus actual labor hours side by side.

Schedule Buffers

A schedule with no slack is a schedule that fails on any imperfect day — and every day is imperfect. One job running ninety minutes long makes the next three appointments late, and the office spends the afternoon apologizing.

There is no universal buffer figure. The right amount depends on your work type, travel distances and how reliable your durations are. The diagnostic question is behavioral: does one long job routinely make your last appointment late? If so, the schedule is tighter than the work actually behaves.

Ways buffer shows up in practice:

• Slack between jobs, sized to typical overrun rather than to best case
• An unassigned block held for emergencies and same-day changes
• Backlog work that can fill a gap when a job finishes early
• A defined cutoff for how late in the day new work can be added

Buffer feels like waste on a good day and looks like foresight on a bad one. The cost of under-buffering — overtime, late arrivals, rushed work, callbacks — is real but distributed, which is why it is chronically underestimated.

Callbacks

A callback is a scheduling event and a quality signal at the same time. It consumes capacity you cannot bill, and it usually arrives at the least convenient moment.

Dispatch practices that keep callbacks from compounding:

• Flag callbacks distinctly rather than scheduling them as ordinary jobs, so the volume stays visible
• Decide deliberately whether the original technician returns — continuity versus a fresh set of eyes
• Prioritize callbacks highly; a customer waiting twice is a customer telling other people about it
• Capture the cause, not just the resolution, so the pattern can be addressed upstream
• Review callback volume by technician and by job type at a fixed cadence

Rising callbacks often trace to schedule pressure rather than skill. Technicians pushed to make an unrealistic day work cut the last ten percent of a job — the checking, the labeling, the cleanup — and that ten percent is where callbacks originate. The upstream system — standards, checklists, classification and root-cause review — is covered in the quality control guide.

Parts and Material Readiness

A perfectly scheduled job fails if the technician arrives without what the work requires. Supply-house trips are among the largest sources of non-billable time in a service business, and they are largely preventable at dispatch.

Readiness practices:

• Use intake detail to anticipate likely materials before the truck rolls
• Standardize truck stock by job mix, and check restocking as part of the daily routine
• Confirm special-order and long-lead items have arrived before the job is placed on the calendar
• Sequence any needed supply-house stop into the route rather than mid-day from the far side of town
• Treat "materials confirmed" as a condition of a job being ready to schedule

Material cost and handling also flow through job costing and cash flow — buying ahead of billing ties up money, as covered in the cash flow guide.

Customer Confirmations

A confirmed appointment is worth more than a scheduled one. Confirmation reduces no-access visits, resets expectations, and gives the customer a chance to mention something that changes the job before the truck is committed.

A simple confirmation pattern:

• Booking confirmation immediately, with the date, window and what to expect
• A reminder the day before, with a way to reply if something changed
• An en-route notification the day of, ideally with a realistic arrival estimate
• A prompt call whenever the plan changes, initiated by you rather than by their complaint

Confirmations are also where access issues surface — a tenant who will not be home, a gate code, a business that closes early. Those discoveries are cheap the day before and expensive at the curb.

Same-Day Changes

Every day changes. A job runs long, a customer cancels, an emergency arrives, a technician calls out. The difference between companies is not whether this happens but whether there is a defined way to handle it.

What a same-day change process needs:

• One person authorized to make the call, so the schedule has a single source of truth
• A rule for which jobs are movable and which are not
• Immediate notification to both the technician and the affected customer
• A backlog of flexible work that can fill an opened gap the same day
• A record of what changed and why, so patterns become visible in the weekly review

That last item is what turns firefighting into improvement. If most same-day changes trace to duration overruns on one job type, the fix is a better standard duration, not a faster dispatcher.

Dispatch Ownership

Dispatch needs one owner. When the schedule is edited by whoever is nearest a screen, jobs get double-booked, customers get conflicting information and nobody is accountable for the day's productivity.

In a one-truck company, the owner is the dispatcher and the schedule lives on a phone. Around the third or fourth technician, that arrangement usually breaks: the owner is on a job when the decisions need making, and the day degrades. The transition to a dedicated dispatch function — even a part-time one — is one of the higher-leverage staffing moves in a growing electrical business, because it protects billable hours across the whole crew rather than adding one crew member's worth.

The dispatcher needs authority to match the responsibility: to move jobs, to decline work that does not fit, and to hold the line on capacity when the answer should be "not today."

Technician Communication

The best schedule fails if the field does not have what it needs. Technicians should start each job knowing the problem as described, the history with that customer, the expected duration, the access details and what is expected at completion.

Communication flowing the other way matters just as much:

• A status update when a job will run materially long, early enough to reschedule downstream
• A prompt heads-up when a job needs a part, a return visit or a different skill set
• Completion notification that closes the job for invoicing, not just for the calendar
• Notes on conditions found that will affect future work at that property

Establish this in the first weeks of employment. What "keeping dispatch informed" means in practice is one of the expectations set during onboarding.

Labor Utilization

Utilization is the number that connects dispatch to money. It measures how much of the labor you pay for reaches a customer invoice.

A technician paid for 40 hours who bills 28 is at 70% utilization. The remaining 12 hours are travel, shop time, waiting on materials, callbacks, meetings and gaps. Some of that is necessary; the question is whether the mix is intentional.

There is no universal target here. Appropriate utilization depends on work type, service area size, apprentice ratios and how your company defines billable. What matters is measuring it consistently against your own definition, watching the trend, and comparing it to the billable-hour assumption your labor rate was built on. If your rate assumed 1,500 billable hours per technician and dispatch is delivering 1,300, the pricing model has a gap that no individual job will reveal.

Capacity Planning

Capacity planning is looking forward: how many productive hours does the company have available in the coming weeks, and how much of that is already committed?

Doing this even roughly answers questions owners usually guess at:

• Can we take this project without damaging service response times?
• Are we booked far enough out to justify another hire, or is this a busy fortnight?
• Where is the schedule thin enough to warrant marketing attention?
• What does time off, training or a vehicle out of service do to the coming weeks?

Capacity is also the honest input to hiring decisions. Sustained full commitment weeks out, with utilization already high and callbacks climbing, is a capacity signal. A stressful fortnight is not. The measurement side of that judgment — available capacity hours, utilization and backlog weeks — is covered in the capacity planning guide, and the financial side is worked through in when to hire your first electrician.

Backlog Visibility

Backlog is sold or committed work not yet performed. It is one of the most useful forward indicators in a contracting business, and many companies cannot state theirs.

Worth knowing at all times:

• Total committed hours or dollars not yet performed
• How far out the schedule is effectively booked
• The split between flexible work and date-committed work
• Approved quotes not yet scheduled — the most commonly lost category
• The trend: is backlog growing, flat or shrinking?

Approved-but-unscheduled work deserves particular attention. That is revenue the customer already agreed to that sits unbooked because nobody owns the step between yes and the calendar. It is usually the fastest available source of additional billable hours.

Missed Appointments

Missed and no-access appointments consume capacity and produce nothing. They are also largely preventable.

Common causes and their fixes:

• No confirmation sent — add a day-before reminder with a reply option
• Window too narrow to keep — widen it and communicate en route
• Access requirements not captured at intake — add them to the intake questions
• Wrong contact confirmed — confirm the person who will actually be present
• Customer never received the details — send written confirmation, not just a verbal one

Track the rate and the reason. A missed-appointment log reviewed monthly usually points at two or three fixable process gaps rather than at unreliable customers.

Dispatch KPIs

A handful of numbers make scheduling performance visible. None of them carry a universal benchmark — their value is in your own trend and in the conversations they trigger.

• Jobs completed per day. Per technician, by work type. Falling counts with steady work suggest travel, duration or readiness problems.
• Average travel time. Per job. The clearest measure of routing discipline and service-area sprawl.
• Schedule fill rate. Committed hours against available hours, looking forward. Shows where demand and capacity are diverging before it hurts.
• Callback rate. Callbacks as a share of completed jobs. A quality signal that consumes capacity twice.
• Duration variance. Scheduled versus actual hours by job type — the input that makes every other number more accurate.
• Missed or no-access appointments. Pure lost capacity, and highly fixable.

These belong alongside financial measures in one operating review rather than in a separate operations silo; the electrical contractor KPI guide shows how the daily, weekly and monthly layers fit together.

Daily and Weekly Review

Daily — confirm tomorrow is ready

1. Walk tomorrow's schedule job by job: assignments, durations, sequence
2. Confirm materials and special orders are on hand for each job
3. Verify customer confirmations went out and any replies were handled
4. Check today's incomplete work and place it deliberately rather than by default
5. Identify gaps and fill them from backlog or approved-but-unscheduled work
6. Flag anything at risk — access, weather, an inspection, a tight window

Weekly — improve the system

1. Review utilization by technician and for the company
2. Review callbacks: volume, cause and pattern
3. Review duration variance by job type and update standards where the data is clear
4. Review missed appointments and their causes
5. Look at backlog and schedule fill for the coming two to four weeks
6. Note capacity constraints worth acting on — hiring, training, service-area limits

Daily review keeps the work running. Weekly review is what actually improves the system, and it is the layer most often skipped. Building both into a standing operating rhythm is what Contractor Core is designed to support.

Common Mistakes

• Scheduling by call order. Ignoring geography, skill and priority because the ticket arrived first.
• Optimistic durations. Feel-based estimates that make every day late by mid-afternoon.
• No buffer. A schedule that only works if nothing goes wrong.
• Windows you cannot keep. Narrow promises that generate more office work than they win business.
• No dispatch owner. Multiple people editing the schedule with no single source of truth.
• Ignoring travel. Treating drive time as free because it is not on an invoice.
• Unmeasured utilization. Assuming a full calendar means the priced billable hours are being delivered.
• Invisible backlog. Approved work that never gets scheduled because no one owns the handoff.
• Absorbing emergencies without a rule. Letting urgent work silently destroy committed appointments.
• No weekly review. Fixing the same day-level problems forever instead of the system producing them.

Frequently Asked Questions