The Operator's Brief · No. 01 · The Play · Four weeks
The Override Tax
Four weeks, on the software you already own. Twelve rules out of two people's heads and into boxes the schedule reads, one dead rule buried, and about five hours of your own time. Two things have to happen in the same month and they pull against each other: getting the rules out of people's heads, and getting those same people to believe the plan is finally worth following.
Free to readBy Ben Guthmiller, Founder & Editor5 minThe move for Monday
The technical half is the easy half, for the reason UPS spent six years learning: a correct route nobody drives is worth nothing. Your own time in this is about five hours across the month — one sentence on Monday, three AI passes you can hand to whoever is best with a keyboard, and ten minutes standing up in week four.
Week One
Write it down. Both kinds. Nobody is in trouble.
DoDana writes down what she moved before the day started and why. Miguel writes down what he changed on the road and why. One sentence each, no more. Don't build a form — a form dies by Thursday. Use the group text, and let people send voice notes if they'd rather.
The sentenceWhat decides whether this week works is one sentence you say out loud on Monday: nobody is in trouble for overriding anything; we are finding out what the system doesn't know. Skip it and you get a beautifully clean list full of lies, which is worse than no list.
What you get: forty to sixty scribbled notes. Under fifteen and your routes are too thin for this play — stop here and save yourself three weeks. What it buys you: a team that believes you meant the sentence.
Week Two
Sixty notes become twelve rules
First AI passPaste the whole list in and ask it four things: group these into rules that keep coming up and name each one; mark each a hard rule or a preference; split them by whether they came from the office before the day or from the field during it; and flag any rule where nobody gave a reason.
Why the split paysOffice notes become rules you type in. Field notes are usually a wrong number in a rule costume — "these take ninety, they're booked at forty" is not a rule, it's a number that has been wrong for two years. The fourth question finds the dead rule: somewhere there will be one nobody can explain — ours is we don't run the north side on Fridays — that traces back to a dispatcher who left in 2019 and has been blocking every Friday for six years.
What you get: about twelve named rules, a list of wrong numbers to fix, and one dead rule finally buried. Finding yours is worth the four weeks on its own.
Week Three
Put them where the software can see them
Second AI passTell it which platform you run, paste the twelve rules, and ask which screen and which box each one belongs in. Two-thirds land in boxes you already pay for — arrival windows, service days, skill tags, preferred techs, job times. Two or three are a setting, not a rule. One or two have nowhere to go and become four lines on a written list Dana works from. That is still a win: yesterday it lived in one person's head; today it survives her being on holiday.
Third AI passExport your customer list, hand the AI that file with your rule list, and have it fill the new columns and give you back a file your platform can take. Twenty minutes instead of two days. Check thirty rows by eye before you upload.
Then the ten minutes that decide the month: put the twelve rules in front of Dana and let her correct them. Two will be wrong. She'll fix them in ten minutes, and that conversation is the whole reason this sticks — she is being asked to trust twelve rules she dictated, not a black box. UPS learned the same thing expensively: a driver will not follow a route he can't question. Neither will Dana.
Week Four
Change the game, or lose the month
DoPut the number on the wall as a game, not a scorecard on people — weekly override count, by name, where everyone can see it. A number that feels like an accusation on Monday feels like a scoreboard by Friday. Framing is not a soft skill here; it is the mechanism.
Close the loopStand up on Monday and tell them what changed: Miguel told us the school is locked until three, so the system knows that now. Dana told us those pumps take ninety minutes, so they're booked at ninety now. People write things down when it visibly worked.
What you get: around fifty overrides in week one, under fifteen by week eight. That's the read you're looking for.
If you count overrides and punish them, your people don't stop overriding — they stop telling you. The number on your wall goes green and you have lost both the minutes and the reason for them. Never attach this number to pay. Ever.
—
What you say, and what you ask
Brief your ops lead, and question a vendor
To your ops lead, in three sentences: We are writing down every schedule change for four weeks, both office and field, one sentence each. Nobody is in trouble and this is not about anyone's judgment. At the end we turn what we learn into rules the software can read, and you check them before they go live.
To a vendor, before you sign: Show me the box where an arrival window lives on a customer. Show me how a skill tag on a job type gets matched to a tech. How do I upload a spreadsheet into these boxes? And — the one that matters — when your software builds a route my dispatcher overrides, where does her reason go? If a vendor cannot answer the fourth one, you are buying the 2003 version of this. It ran the wrong rules faster for six years.
Know an owner whose schedule lives in one person's head?
The reading was free. This is the workbench.
Run this on your own routes, with the tools that execute it.
You have read the whole case — the Brief, the Workup, and the four weeks. The Bench is the instruments: the tested prompt chains for the three AI passes, the box-name maps for Jobber, Housecall Pro, ServiceTitan and Workiz, and the thirty-row upload check. The writing stays free. The Bench is the tools.