Dana has run the board at a Lubbock mechanical shop for nine years. She knows Marcus will not go into a crawlspace, and that the property manager on Slide Road accepts only the senior tech. She knows that nothing scheduled out past Wolfforth should share a day with anything north of the Loop, because the drive eats an hour the two-hour arrival window does not have. None of it is written down anywhere, and this week she is at Possum Kingdom with her grandkids.
What the whiteboard doesn't show
The board itself is public: names, addresses, time windows. What produced the board is not. Which techs hold which EPA 608 certification, and therefore who can legally put hands on refrigerant. Whose truck carries the pipe threader and whose carries the 28-foot ladder. Which gate codes live on a sticky note in Dana's drawer. Which maintenance-agreement visits can slide a day without a phone call, and which demand calls absolutely cannot. Which customer on 19th Street wants a call before the truck pulls up, because she has dogs to put away.
The knowledge that makes a board good is the residue of nine years of small failures, and it lives in exactly one head. So the substitute dispatcher builds a board that looks plausible at 7 a.m. and is wrong in ways nobody sees until 10: the tech without the right certification standing in front of a refrigerant job, the ladder truck forty minutes from the two-story unit that needed it, the Slide Road property manager on the phone asking why she got the new kid.
The interview that turns habits into rules
The fix starts with a conversation, not software. Sit with the dispatcher and yesterday's board and ask why about every assignment. Why did Marcus get the strip-mall rooftop unit and not the house on Elgin? Every answer is a rule, and the rules sort into three kinds. Hard constraints: certifications, what equipment rides on which truck, promised arrival windows. Soft preferences: Marcus and crawlspaces — he will go in an emergency, he should not by default. Customer facts: the Slide Road requirement, the gate codes, the call-first houses.
Two afternoons of this produce a first draft. Its real value shows when Dana reads it back and says "that's mostly right, except—". The exceptions are the point of the exercise. They are the rules she did not know she was applying.
Rules propose; a person approves
Here is the mechanism. Overnight, tomorrow's calls are laid against the written rules — certifications checked, geography grouped so Wolfforth and the north Loop stay on separate days, promised windows respected, truck inventory considered — and a drafted board is waiting at 6:45. Whoever is running the desk looks at it, drags a job or two, and approves it.
The approval gate is not a training-wheels phase to be removed later. It is the design. Software does the assembly; a person keeps the authority. When Dana is in, she edits her own draft in ten minutes instead of building the board from memory in ninety, which on a normal Tuesday is the entire benefit. When she is out, her stand-in starts from her rules instead of from a blank whiteboard and a memory he does not have.
The vacation week is the test
The measure of this system is not a demo. It is the week she is gone. Did the promised windows hold? Did the right certification land on the refrigerant job? Did the Slide Road manager get the senior tech without anyone needing to remember to arrange it? If the answers are yes, something has changed that is bigger than scheduling: the business has stopped holding its breath every time one person takes time off.
There is a quieter benefit behind that one. A shop where the dispatch logic exists on paper can eventually train Dana's successor, promote her, or survive her retirement. A shop where it exists only in her head cannot do any of those things, and usually finds out at the worst time.
Rules go stale, and someone has to own them
Marcus finishes his certification upgrade in the spring. A fleet customer moves its yard across town. The threader migrates to a different truck after a trade-in. A rule list nobody maintains becomes next year's confidently wrong board — which is worse than no list, because people trust it.
So amending a rule has to cost less than a minute: one line changed, the day the fact changes, by the person who learned it. In practice the owner of the list is the dispatcher herself, which is fitting. The system is her knowledge, kept current, instead of her knowledge, kept private.
What this will not handle
Triage under pressure stays human. When water is coming through the ceiling of a dental office at 8:05, the draft can propose a resequencing, but deciding who gets bumped — and who calls the bumped customer to apologize — is judgment, and it should stay that way. A tech calling in sick at 6:50 means a redraft in minutes, which helps, but the apology calls do not automate and should not.
And if the real problem is four techs' worth of work and three techs on payroll, no board fixes arithmetic. What the drafted board does in that case is make the shortage visible weeks earlier, in writing, which at least turns a chronic emergency into a hiring decision.
Where to start
Spend one hour with your dispatcher and yesterday's board, writing down every "because." No software required. The list you produce has value even if nothing is ever automated — it is the continuity document the business currently does not have, and one hour is a cheap way to find out how much of the operation lives in one head.