Capacity & Backlog Forecaster: See Which Days and Skills Will Run Short

The problem this kills

Every service manager has been blindsided by a Thursday. The board looked fine on Monday — and then a flood of incoming jobs, two techs out sick, and a backlog of HVAC calls that all need the one certified guy collide into a day that was never going to work. The customers were already booked. The promise was already made. Now you're scrambling for overtime, subcontractors, and apology calls.

The reason it keeps happening is that demand and capacity live in different places that never meet. Booked jobs are in the dispatch board. The backlog is in a spreadsheet or somebody's head. Tech availability and PTO are on a paper calendar or a different sheet. Nobody is holding "hours of work coming in" next to "hours of work we can actually do" — by day, by skill, by zone — far enough ahead to do anything about it.

So the crunch always arrives as a surprise, when the only moves left are expensive ones. A capacity and backlog forecaster turns that surprise into a two-to-four-week heads-up — early enough to shift, subcontract, or schedule overtime calmly instead of in a panic.

What you'll build

A simple internal web app for your dispatch and planning team. You import your booked jobs and open backlog (each with an estimated duration), and your technician availability and PTO broken out by skill and zone. The tool converts every job into hours by type, adds travel time and a no-show / cancellation factor, and lays the resulting demand against the technician-hours you actually have available.

The result is a day-by-skill-by-zone capacity heatmap for the next two to four weeks: green where you have headroom, red where demand exceeds available hours. It flags the specific days and skills that will run short — surfacing the skill-specific bottlenecks (the one HVAC cert, the only tech who can do panel upgrades in the north zone) that a headcount-only view hides. The service manager reviews the forecast, picks a mitigation plan for each shortfall — overtime, reschedule, or subcontract — and approves it. Only then is the action list finalized and exported. Nothing gets rebooked until a person signs off.

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 you dispatch today, what your job types and skills are, how your jobs and availability exports are actually shaped, your typical and peak volumes, how you convert jobs to hours, your travel and no-show realities, and the messy exceptions (multi-tech jobs, partial-day PTO, a tech who covers two zones). It reflects a short tailored spec back to you and gets your thumbs-up before it builds anything, so the forecast matches how your shop really runs — not a generic template.

From there it walks the agent through the data model, the jobs-and-availability import with duplicate guards, the hours-conversion engine (with travel and no-show factors), the day/skill/zone heatmap, the shortfall flags, the service-manager approval gate on the mitigation plan, and the CSV export of the action list. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path that uses Google Sheet / CSV imports as the data source and produces a clean CSV export — so you can build and run the whole thing this weekend regardless of what dispatch system you're on.

The governance it includes (this is the point)

This tool moves real jobs and real people, so the controls aren't optional. The plan builds in login so only your team can use it, row-level security so you only ever see your own organization's jobs and techs, a complete audit trail of who changed which assumption and who approved which mitigation, a hard human-approval gate so no rebooking action is committed until the service manager signs off on the plan, and duplicate guards (dedupe on job id) so the same job can't be counted twice when you re-import.

Who it's for

Service managers, dispatch supervisors, and planners running a field-service operation — anyone who books work against a finite pool of skilled technicians and is tired of finding out about a capacity crunch the morning it hits. If you can explain your job types, your skills, your zones, and roughly how long a job takes, you can build this.

You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have your first capacity heatmap on screen before the weekend's out.