By Greg Allan, tradesman and creator of Data First Coaching
Why does a technician route fall apart the moment something goes wrong?
Most routes are built for the best case: every technician on the road, every job running to time, every building manager available when planned. The moment one technician calls in sick or an emergency callout comes in, that plan has nowhere to absorb it, so the whole week's testing and inspection schedule starts sliding sideways.
A fire protection business runs on fixed appointments that cannot simply be moved. Routine service on sprinklers, fire alarms, hydrants, hose reels and emergency lighting is often tied to a strata or building manager's access window, and an annual statement has a date attached to it that compliance rules do not move for anyone. When the route has no slack built in, one disruption does not stay contained to one day. It cascades through the logbook, the certification deadlines, and eventually the client relationship.
What happens to the week's logbook and certification deadlines when one hydrant test slips?
When a route is drawn up assuming nothing will go wrong, a single missed hydrant test or a defect follow-up pushed to next week does not disappear. It sits in the logbook as an overdue item, and if it lines up with an audit or an annual statement, the business is now explaining a gap in compliance rather than closing one out.
This is the pattern that pulls an owner back onto the tools. A technician goes down, nobody else is free, and the owner ends up covering the route themselves to keep the building manager satisfied and the certification on track. That is not a one-off; it is what happens every time the schedule is built without room for the things that are entirely predictable, even if the exact day is not.
How do you plan a fire protection route around what could go wrong, not just what looks good on paper?
You plan the route with the breakdown built in, not bolted on afterwards. Before you commit a week of routine service, defect quotes and maintenance contract visits to the roster, you ask what happens if a technician is off, if an emergency callout lands mid-morning, or if a strata building needs access brought forward.
This is a discipline, not a feeling. It means looking at how many technicians are actually free on any given day once you take out the ones already committed to fixed appointments, and treating that number as the real capacity of the week rather than the number on the roster. A route with no spare capacity is a route that breaks the first time something ordinary happens, and something ordinary happens most weeks in this trade.
What number in the business actually shows whether a route has spare capacity?
The number that matters is not how many jobs are booked in, it is how much unbooked room exists across the technicians once the fixed, date-driven work, annual statements, scheduled routine service, logbook commitments, is locked in. That spare capacity figure, read fresh from the week's actual data rather than remembered from last month, is what tells you whether the route can absorb a sick day or an emergency callout without everything else moving.
This is a data first way of looking at the week. Memory tends to say "we're usually fine," because that is how the last normal week felt. The actual numbers, who is rostered where, what is fixed and what has slack, tell a different and more current story, and it is the one worth planning from.
How can AI agents help keep a technician route on track?
An AI agent is software that does a job the way you would do it yourself, using your own prices, your own wording and your own rules. In a fire protection business, agents can take on the non-billable work of watching the week's route against what is actually fixed, flagging where a technician's day has no room left before it is confirmed, rather than after a defect job gets bumped.
AI agents do not decide the route for you and they are not a dispatch system bought off the shelf for every trade. The value is in having them watch your own data, your own logbook, your own maintenance contract calendar, and surface the gap before it becomes a missed hydrant test or a certification chased at the last minute.
How does a tight route let you say no to jobs that don't fit?
A route you actually know, down to where the spare capacity sits, is what lets you turn away work that would blow out the week rather than squeezing it in and hoping. Saying no to a job that does not fit is not a loss, it is what protects the routine service and annual statement commitments you already have with building managers and strata.
Owners who do not know their real capacity tend to say yes to everything, because it feels like the safe option. It rarely is. The route that bends to fit every new request is the one that eventually drops a fixed appointment, and in fire protection a dropped appointment is a compliance gap, not just a late visit.
How does Data First Coaching approach this?
Data First Coaching starts from the technician route as it actually runs, not as it is remembered. Through the Trade Business Intelligence, Greg Allan looks at where the week's fixed work sits against the real spare capacity, and where the pattern of slipped jobs or last minute cover is coming from, because the route is rarely the root problem on its own.
Greg teaches that the owner's job is to plan for what could go wrong before it happens: “What's going to go wrong? What could happen? Someone could get injured. Someone could get sick.” The how, building that discipline into a working route week on week, is worked through inside the Academy, among members who are open minded, innovative and willing to share what they learn, because the Trade Business Intelligence is powered by every member.

