Build your own Operator — the shop's first-wrench call

Eleven trucks down, three bays, and the same question every morning: whose wrench turns first? That answer was never a list — it's a judgment call across dispatch, compliance, weather, and money. Here's how a maintenance manager builds an Operator that makes that call at 5:30 every morning, grounded in his own SOPs — and how the Builder checks the simpler options before building anything.

Why build this one at all?

Fair question — and the Builder asks it before you do. A backlog list takes no building: the Maintenance Backlog Triage template ships with the platform and applies in one click. What the list can't give you is the order. Knowing that a two-hour clamp job on a truck due out at noon beats the big job that can wait, that a regulated test window is never traded away, that a winter front rewrites the whole board — that judgment lives in your head and your SOP binder, and it doesn't scale past you. The build captures exactly that: your judgment, written down once, applied every morning whether you're in the building or not.

The steps

1. Open Operators → Build an Operator and say the job like you'd say it to a new hire: “Every morning tell me what the shop fixes first and why. Not a list — the order.”
2. The Builder checks the simpler shelf before it builds anything. A plain reminder would be an Automation — instant, no build needed — and it routes you there. A backlog list is the Maintenance Backlog Triage template — it shows the card with a one-click Apply button. If a list is all you need, take it and stop here.
3. Say what the ready-made options can't know: “I have the list. I need the order — eleven trucks down and three bays.” Now the interview starts: how many bays, when trucks have to be out the door, what a day down actually costs you per unit.
4. It reads your SOPs while you talk. The Builder can see your approved Policies & Procedures, and it uses them: “Your Annual Vessel Test Windows procedure already sets those deadlines — I'll have the new Operator consult the current version each morning rather than copying the dates.” Grounded rules are living rules: revise the SOP and the Operator follows the revision the same day. Typed-in copies go stale; citations don't.
5. Give it the house rules and watch them become standing instructions: two-hour fixes jump ahead of big jobs when a truck's due out today · a regulated test window is never traded away, no matter what dispatch wants · a winter front reshuffles the board ahead of everything else.
6. It shows you the ranking brain before you commit. Cost-of-delay does the thinking — what each idle truck costs per day sets the order. On your screen the Operator reports the order and the days down; the dollar figures themselves stay on the owner's screens, where money always lives on this platform.
7. Dry run on today's real shop. Before anything is saved, the Builder runs the draft against this morning's actual trucks and shows the board it would have posted. If unit 114 is ranked wrong, say so — that's one more rule captured, not a rebuild.
8. Approve & save. The build conversation happens once; from tomorrow the Operator is simply on duty, every morning before the first bay opens. And everything it ever wants done is a proposal queued for a person to approve — no Operator on this platform acts alone or touches money.
9. When the rules grow, edit — don't rebuild. First cold snap of the year, open the Operator and add one sentence: “when a hard freeze is forecast, winter-prep items move up per the Winter Readiness procedure.” One sentence, grounded in the SOP by name, live the next morning.

Gotchas