Service Manager Dispatch SOP for Contractors: The Daily Operating Rhythm

Ask ten contractors what their service manager does all day and you'll get ten versions of "puts out fires." That's because dispatch usually grows by accident — one person, one phone, tribal knowledge. The SOP below turns it into a repeatable daily rhythm: same sequence, same standards, same closeout, every day. When the service manager is out sick, anyone trained on the SOP can run the board.

0600–0700: The morning board review (before the first truck rolls)

The day is won or lost before 7 AM. The service manager's first hour:

1. Review today's board. Every job, every tech, every window. Look for: double-booked techs, jobs with no tech assigned, windows that don't match drive time, parts flagged "need to order" with no order placed.
2. Check yesterday's carryover. Any job not completed yesterday gets a decision: rebooked today (where?), parts pending (ordered?), or customer waiting on a call (who's calling, by when?). Nothing carries over silently.
3. Confirm tech status. Who's out sick, who's on PTO, whose truck is in the shop. Adjust the board now — reassign or reschedule before customers are expecting someone who isn't coming.
4. Scan the emergency queue. Overnight texts, voicemails, after-hours triage flags. True emergencies get first slots; everything else gets scheduled in priority order.
5. Send the morning dispatch text to each tech: their job list, first-job address, and any special notes (gate code, "customer has dogs," parts on the truck). One text per tech, before they leave the shop.

The capacity rules (written, not felt)

"The board feels full" is not a capacity system. Write the numbers:

• Jobs per tech per day by job type: e.g., 5–6 tune-ups, 3–4 service calls, 1–2 installs. The board enforces these; the service manager doesn't negotiate with it daily.
• Flex capacity: hold 15–20% of daily slots unblocked for emergencies and same-day requests. A board booked to 100% at 7 AM has no room for the no-heat call at 10 AM.
• Drive-time buffers: minimum 30 minutes between jobs in different zones; batch same-neighborhood jobs on the same tech's route. The board should show geography, not just times.
• The overbooking rule: overbook only with the service manager's explicit approval, never by default, and never the flex slots. Every overbook gets a named backup plan ("if this runs long, job 4 moves to Tech B").

Tech communication standards (the non-negotiables)

Customer complaints about communication almost always trace back to techs not following a standard that was never written down. Write it:

• En-route text: every tech texts the customer when leaving for the job — name, photo optional, ETA. Automated from the field-service software if available; manual if not. No exceptions.
• Running late protocol: if the ETA slips more than 30 minutes, the tech notifies dispatch immediately, and dispatch (not the tech) calls the customer with the new window. Customers forgive delays; they don't forgive silence.
• On-site updates: diagnosis communicated before work begins, price approved before work begins, completion summary texted after ("here's what we did"). No surprise line items on the invoice.
• Parts-run rule: tech calls dispatch before leaving for parts — dispatch checks whether another tech nearby has the part, or whether the job can be completed on a return visit without a 90-minute supply-house round trip. Unmanaged parts runs are the #1 schedule killer.
• End-of-job closeout: job marked complete in the system before leaving the driveway — photos uploaded, notes entered, invoice sent or scheduled. "I'll do the paperwork tonight" is how jobs go unbilled.

Midday: the 11 AM board check (15 minutes)

One scheduled check-in, same time daily:

• Which techs are on track, which are slipping — and what's the recovery plan for the afternoon.
• Any new emergency calls since morning, slotted into flex capacity or bumping the lowest-priority job (with that customer called immediately).
• Parts runs in progress — who's where, when they're back on jobs.
• Tomorrow's board: first pass. Any gaps (unassigned jobs, thin coverage) get flagged now, not at 6 AM tomorrow.

End of day: the closeout (the discipline that compounds)

The last 30 minutes of the service manager's day:

1. Board reconciliation: every today's-job has a status — complete, rescheduled (with new date), or parts-pending (with order status). No job left in limbo.
2. Tomorrow locked: tomorrow's board is final — techs assigned, customers confirmed, morning dispatch texts scheduled.
3. Callback review: any customer called back today gets a same-day or next-morning return visit scheduled. Callbacks age badly; schedule them while the details are fresh.
4. Uncontacted leads at zero: every lead that arrived today has been contacted. The service manager verifies; the CSR executes.
5. Notes for tomorrow: anything the morning self needs to know — the unhappy customer, the tricky job, the tech who's struggling. Written, not remembered.

The weekly layer (Friday, 30 minutes)

• Numbers review: jobs completed vs. scheduled, on-time arrival rate, callback rate, average ticket, uncontacted-lead count. Five numbers, trending.
• Pattern check: same tech always running late? Same job type always needing parts runs? Same neighborhood generating callbacks? Patterns get fixed; incidents get noted.
• Next week's capacity: PTO, holidays, expected volume — the board for next week gets its first pass before the weekend.

Three mistakes that break the rhythm

• Dispatch by memory. If the board only exists in the service manager's head, the company has no dispatch system — it has a person. Everything above goes in the software, visible to everyone.
• No flex capacity. A 100%-booked board is a fragile board. The first emergency of the day cascades into five late arrivals. Protect the flex slots like revenue, because they are.
• Skipping the closeout. The end-of-day routine feels optional until the morning the board is a mess, two customers were never called back, and nobody knows which jobs are actually done. Thirty minutes prevents all of it.

Related guides in this series

Extend the system with Dispatching Without a Dispatcher, Night Dispatch for Multi-Truck Shops, and HVAC Dispatch Communication.

The done-for-you version

This post is part of the Leveraged Owner 8-system framework — the done-for-you version with the full setup guides, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems.

Stats sourced as labeled: BrightLocal 2026 (68% 4-star+ threshold) — directionally useful, always measure your own numbers.