The scheduling sheet had eleven tabs, three colors with disputed meanings, and a cell — K17 — that two people were quietly fighting over with competing edits. It scheduled forty field technicians across three regions, and it worked, mostly, because one dispatcher held the whole thing in her head.
A spreadsheet is a confession
When a spreadsheet grows tabs like this, it’s the business writing its own requirements document without knowing it. Every tab is a screen someone needs. Every color is a status field. Every disputed cell is a permissions model waiting to be drawn.
We didn’t start by imagining a platform. We started by printing the sheet and asking the dispatcher to narrate a normal Monday.
What the off-the-shelf options got wrong
Two commercial scheduling products were trialed before I was called. Both failed the same way: they scheduled the way their model of a field business works — and this company’s edge, the reason customers stayed, was precisely the way its scheduling didn’t work like everyone else’s.
Buying software means adopting someone else’s opinion about how you should work. Sometimes that opinion is an upgrade. Sometimes it’s the death of the thing your customers pay you for.
What shipped
A small scheduling platform whose screens map one-to-one onto the old tabs, whose statuses are the old colors (meanings now written down), and where K17 became a rule with a name, an owner, and a log. The dispatcher approved every screen before it was built — she recognized all of them.
The sheet is retired. The dispatcher is not — she’s training her successor in an afternoon, because the system now explains itself.