runbookify
← All plans
Field Service & Dispatch / Scheduling & Dispatch

Emergency Job Bump Optimizer: Squeeze an Urgent Call Into a Full Board

Drop an urgent job into a day that's already booked solid and get a ranked list of which lower-priority, non-SLA jobs to bump — each option showing the real customer impact — so your dispatcher picks the least-harm move and approves it before anyone is rescheduled.

IntermediateAn afternoonBuilds onNext.jsSupabaseResend
What you'll build

A web tool where a dispatcher enters an urgent job, the app finds where it could fit on today's board, ranks which lower-priority non-SLA jobs to bump or reschedule by least customer harm (with added travel and each bumped customer's new window spelled out), the dispatcher approves one option, and only then does the tool reshuffle the board and send the bumped customer a reschedule notice via Resend — plus a clean CSV export of the revised board and bump list.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.

Before you start

  • A Supabase account (free)
  • A Vercel account (free)
  • A Resend account (free)
  • Today's board as a CSV/sheet
  • Your priority & SLA rules as a CSV/sheet
  • Tech and customer contact details
  • Claude Code or any AI coding agent

The problem this kills

A high-priority job just came in: the freezer's down at a restaurant, or a tenant has no heat, and it has to be seen today. Your board is already full. So now your dispatcher is squinting at a route, doing mental math about drive times, and trying to remember which of today's jobs has a contract behind it and which is just a "whenever you can get to it." They bump someone — usually whoever's easiest to reach, not whoever it hurts least to move — and then spend the next twenty minutes apologizing on the phone.

Get it wrong and you blow an SLA you didn't realize applied, or you bump a contract customer to make room and torch the relationship, or you reshuffle the route so badly your tech burns an extra hour in traffic. Worst of all, nobody can later reconstruct why that job got moved. The decision lives entirely in one stressed person's head, under time pressure, with no view of the trade-offs. You don't need to be a developer to take that pressure off them.

What you'll build

A simple internal web tool that does the cruel arithmetic for your dispatcher. They type in the urgent job — where it is, the skill it needs, how long it'll take, and its deadline — and the tool looks at today's actual board: every scheduled job, who's assigned, the windows, and (crucially) which jobs are SLA-protected or contract jobs that must never be casually moved. It then finds the realistic insertion points and produces a ranked list of bump options, each one scored by least customer harm and showing the real consequences: which job would move, that customer's new window, the extra travel the reshuffle adds, and a clear flag if an option would touch anything SLA-protected. Your dispatcher reads the options, picks one, and approves it. Only then does the tool commit the revised board, draft and send the bumped customer a reschedule notice via Resend, and let you export the whole revised board and bump list as a clean CSV.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how your board is structured today and where it lives, exactly what makes a job "urgent" enough to bump for, how your priority tiers and SLA / contract rules actually work, how you think about travel and drive time, what data you have on each job and customer, and the messy edge cases (a job already half-done, a tech with a special skill only they have, a customer you can't reach) — and then it tailors the priority model, the bump ranking, and every later step to your answers. This is not a generic template; the agent reads a short spec back to you and waits for your thumbs-up before it builds a thing. From there it walks the agent through importing the board and rules, the urgent-job intake, the least-harm ranking engine, the approve gate, the reschedule + customer-notice send, and the CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build and run the whole thing today even with no integration to your scheduling software.

The governance it includes (this is the point)

This tool moves real jobs and sends real customers a "we have to reschedule you" message, so it ships with the controls a serious dispatch operation needs: login so only your team can use it, row-level security so you only ever see your own company's board, a complete audit trail of who entered the urgent job, which option was chosen, who approved it, and when, a hard human-approval gate so nothing on the board is moved and no customer is messaged until a dispatcher signs off on a specific bump option, a built-in rule that never auto-bumps an SLA-protected or contract job without an explicit override flag, and duplicate guards keyed on the work-order id so the same urgent job entered twice can't trigger two reshuffles.

Who it's for

Dispatchers, service managers, and route coordinators at HVAC, plumbing, electrical, refrigeration, restoration, property-management, and facilities operations — anyone who owns a daily board and regularly has to find room for the call that can't wait. If you can describe how you decide what's urgent and which jobs are safe to move, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll watch your first least-harm bump option ranked and approved this same afternoon.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.