• Replies 12 replies
  • Subscribers 2 subscribers
  • Views 3 views
  • Users 0 members are here
Options
Related

How are you handling emergency or same-day jobs without disrupting the schedule?

Gwen Albright

We've been wrestling with this one for months and I want to hear how others are solving it.

We run 8 technicians across 3 zones. Our bread and butter is scheduled maintenance, but we get 3-5 emergency calls per week that need same-day response. The problem: every time we shove an emergency into the schedule, we break 2-3 other appointments. Customers get bumped. Technicians run late. Dispatchers spend their whole day replanning.

Here's what we've tried:

  • Keeping one "float" slot per day — but that's revenue we're not capturing, and emergencies don't conveniently arrive one per day
  • Overbooking the first appointment of each day assuming cancellations — works 60% of the time, creates chaos the other 40%
  • Asking technicians to absorb extra jobs — they're burning out, and I'm getting pushback on overtime

I'm curious what your actual operational rules look like. Do you have a written policy customers agree to? How do you decide which scheduled job gets bumped? And has anyone found a way to make this not feel like a daily crisis?

Gwen

Parents

  • We split our fleet into two pools:

    • Maintenance pool: 5 techs, tightly scheduled, no interruptions
    • Response pool: 3 techs, loose schedules with 60-90 min buffers, handle all same-day and overflow

    Response pool costs more per job but our maintenance efficiency is up 23% since we stopped breaking those schedules.

    Requires right-sizing the pools — we adjust monthly based on emergency volume trends.

  • in reply to Sylvia Chen

    Yes — response pool is measured on resolution rate (emergency closed same-day) and customer satisfaction specifically, not utilization. They're expected to have downtime.

    Maintenance pool: utilization, on-time arrival, jobs per day.

    Different scorecards, different comp structures. Took a year to get right.

  • in reply to Sylvia Chen

    Another way to think about it: the two-pool model essentially creates a service level agreement with your own operation. You're protecting predictable revenue by explicitly funding response capacity.

    We've taken a similar approach but with floating technicians who rotate into the response role weekly — prevents burnout and cross-trains the team.

    Worth noting: we found response pool techs need different soft skills. They're walking into crises, not following a checklist. Hiring profile changed significantly.

Reply
  • in reply to Sylvia Chen

    Another way to think about it: the two-pool model essentially creates a service level agreement with your own operation. You're protecting predictable revenue by explicitly funding response capacity.

    We've taken a similar approach but with floating technicians who rotate into the response role weekly — prevents burnout and cross-trains the team.

    Worth noting: we found response pool techs need different soft skills. They're walking into crises, not following a checklist. Hiring profile changed significantly.

Children
No Data