The schedule lives in one person’s head. That is the risk.

The whiteboard is not the problem

It is genuinely good at its job. It is glanceable, everyone understands it, it never goes down, and it encodes years of judgement about which jobs pair well and which customer will not be home before four.

The problem is that it exists in one place and one head. When that person is sick, the business runs at half speed. When they leave, the judgement leaves too — and none of it was ever written down because it never needed to be.

What automating scheduling actually means

Not an algorithm deciding your day. In a business of five vans, an optimiser will produce a route that is technically shorter and ignores the reason you always send that bloke to that customer.

What it means in practice is: the schedule is visible to everyone from wherever they are, changes propagate without a phone call, and the job that moved is reflected in the job record rather than only on the board.

• Visible from the van Not a phone call to the office to ask what is next. This is most of the value.
• Changes propagate A job moved on the board reaches the person driving to it, without anyone remembering to ring.
• The record follows The job system knows the job moved. Otherwise you have two schedules and one of them is wrong.
• The judgement is captured Not automated — recorded. Which customer needs a morning slot, which pairing works. Written down at last.

Why we usually argue against the clever version

Route optimisation demos beautifully and disappoints in small businesses, because the constraints that actually govern your day are not in the data. Access hours, which customer will ring the office if a different person turns up, the apprentice who cannot be sent alone to that job.

You can encode those constraints, and on a fleet of thirty it is worth doing. On a fleet of five the encoding costs more than the optimisation returns — which is the same arithmetic as the build-vs-buy framework, applied to a feature rather than a system.

The failure mode to avoid

Two schedules. The moment the software schedule and the whiteboard disagree, everyone trusts the whiteboard — correctly, because it is the one being maintained — and the software becomes a thing somebody updates on Fridays for no reason.

So the migration matters more than the features. Either the board goes or the software does; running both is worse than either, and it is the most common way these projects quietly fail.

Where this does not pay

One or two people who talk to each other all day. You do not have a scheduling problem, you have a conversation, and it is working.

It also does not pay if the underlying problem is that you take on more work than you can do. Scheduling software will show you that more precisely and change nothing about it — automating a broken process makes it break faster.

The honest sequence for most businesses is: get the schedule visible from the van first, leave the board on the wall for a month while people learn to trust the new thing, then take the board down. Skipping the middle step is how you end up with two schedules; skipping the last is how you stay there permanently.

If the systems you would connect are ones we have built against, the estimate has a foundation — the checker tells you in two clicks. If not, expect the first increment to include discovery, quoted openly.

What we have not measured, and what we would measure for you

There is no reliable published Australian figure for how long scheduling and dispatch coordination takes in a small business, and we are not going to borrow one from a vendor whitepaper to make this page more persuasive. Most numbers you will see quoted for this were produced by companies selling the fix.

What we would do instead is count it on one of your jobs. Follow a single job end to end, note every time a human touches this step, and multiply by what that person costs loaded. That is a real number about your business and it takes an afternoon.

You can run the arithmetic yourself first — the leak calculator uses ABS, Average Weekly Earnings, Australia, May 2026 for the wage default and ATO, Super guarantee, current rate for super, and returns a range rather than a single confident figure. If the range comes back under our minimum engagement, that is a real answer and you should stop there.