The Service Operator

Stop Swiss-Cheese Days: Dispatch Rules Lift Capacity


Listen Later

Stop Swiss-Cheese Days: Dispatch Rules Lift Capacity

If your board looks full every day but your techs are still running late, burning overtime, and you're turning away the jobs that actually pay—you don't have a scheduling problem. You have a dispatch board with no rules.

The Problem: Swiss-Cheese Scheduling

Most shops book first-come, first-served: phone rings, CSR finds the next open slot, books it. This works fine in March when you're running twelve calls a day across four trucks. But nobody changes the rules when volume doubles in June.

The hidden cost: If each truck loses one job a day to a blown window or late cancellation—and that job averages $300—that's $1,200 a day across four trucks. Over a five-day week, that's $6,000 in work you booked and didn't complete.

The Solution: Three Dispatch Board Rules
Rule One: Arrival Buckets by Zone

Stop booking exact times. Book into arrival buckets.

  • Option A: AM (8-noon), PM (noon-4)
  • Option B: Three buckets (8-11, 10-1, 1-4) for busier metros
  • Zone integration: Split your service area into 2-5 zones. Book into the bucket that keeps each tech in the same zone or adjacent zone for that block.

    Customer acceptance: HVAC contractors commonly use 2-4 hour windows for demand service. One-hour windows are sold as a premium upgrade, not the default.

    Rule Two: Travel Buffers and Job Tiers

    Explicit travel buffers:

    • 15-30 minutes between stops (dense urban)
    • 20-40 minutes (suburban/rural)
    • Built into the schedule, not optional
    • Job tiers control window sizes:

      • Short: Diagnostics, tune-ups, simple fixes (2-hour window)
      • Standard: Typical repair, replacement quote (3-hour window)
      • Long: Complex diagnosis, evap coil, sewer camera (4-hour window)
      • Rule Three: The Rescue Slot

        Hold one block (60-90 minutes) in mid-afternoon on every crew, every day. Don't book it with regular work.

        Reserved for:

        • Urgent, high-value calls (compressor replacements)
        • Warranty/callback work threatening tomorrow's schedule
        • Saves that keep installs on track
        • If nothing urgent comes in: Release to waitlist at 2 PM and fill it.

          Implementation by Platform
          ServiceTitan
          • Zones: Set up by ZIP, filter dispatch board by zone
          • Buffers: Minimum Booking Lead Time in Adaptive Capacity
          • Tiers: Estimated durations on job types tied to bookable windows
          • Rescue slot: Non-job event titled "Rescue, Crew A"
          • Jobber
            • Buckets: Company-level default arrival windows in Work Settings
            • Zones: Custom property tags (Zone North, Zone South)
            • Buffers: New Schedule suggests shortest drive times, auto-reorders visits
            • Rescue slot: Calendar event on each tech's schedule
            • Housecall Pro
              • Zones: Service area tool for drawing zones
              • Buffers: Optimize by Drive Time feature
              • Tiers: Job types with expected durations
              • Rescue slot: Schedule an event to hold the time
              • The Daily Huddle: 10-Minute Enforcement

                When: Every morning, 7:45 AM, standing up at the board

                Agenda (5 lines):

                1. Yesterday: Where did gaps or overruns hit? Any blown windows?
                2. Today: Confirm each crew's rescue slot and first two calls by zone
                3. Constraints: Tech PTO, parts runs, training, weather
                4. Risks: Which calls are at risk of sliding? What's Plan B?
                5. Close: One change to today's routes/windows, one reminder for CSRs
                6. Timebox: If it goes past 10 minutes, you're doing it wrong.

                  What to Measure (Weekly)
                  • Window hit percentage (tech arrived inside promised window)
                  • Overtime minutes per crew
                  • Completions per crew day
                  • Rescue-slot utilization (used vs. released)
                  • The Counterargument

                    "Aren't we losing a job a day per crew?"

                    On paper, yes—you're booking fewer jobs per block. But you're gaining:

                    • Jobs you already booked that you're currently losing to blown windows
                    • Overtime you're not paying
                    • High-value rescue calls you're currently turning away
                    • For tight-window customers: Offer a paid express option (one-hour window, higher trip fee). But that's the exception, not the rule.

                      Your Question This Week

                      Pull up last week's board. Where did the gaps show up—the blown windows, the late arrivals, the overtime? Which one of these rules (buffer, bucket, tier, or rescue slot) would have prevented it?

                      That's your starting point.

                      Resources:

                      • Dispatch Board Rules Checklist - One-page implementation guide with platform-specific settings
                      • ...more
                        View all episodesView all episodes
                        Download on the App Store

                        The Service OperatorBy Mike, Chris