The cheapest way to schedule and dispatch engineers

Last updated: September 2026

What the free method really costs

Most small trades businesses schedule with a whiteboard, a paper diary or a group chat, and all three cost nothing up front. The cost arrives later, in a form that never appears on a bank statement.

Price one wasted visit honestly: two hours of an engineer, the fuel, and the job it displaced. Price one double booking: the apology, the rebooked slot, and the customer who quietly rings someone else next time. Price one visit that nobody wrote up: the invoice that goes out three weeks late, if it goes out at all.

A business doing that once a fortnight is losing more than the monthly cost of almost any scheduling tool. That is the real comparison, not the subscription against zero.

What cheap scheduling has to include

Cheap is not the same as minimal. A tool that saves money has to cover the whole loop, or the savings leak back out through the part it does not cover:

• A week you can see, with visits against people, not a list of dates.
• A warning when you double book, at the moment you do it.
• The job attached to the visit, so the engineer arrives knowing the fault, the access and the history.
• The customer told automatically when a visit is booked, moved or cancelled, because the confirmation call is the admin cost nobody counts.
• Something the engineer can read on a phone, or the schedule lives in the office and the office spends its day reading it out loud.

Anything that does not close that loop leaves you paying twice: once for the tool and once for the phone calls it did not remove.

What you should refuse to pay extra for

Three pricing shapes quietly turn a cheap tool into an expensive one:

1. Per-seat pricing with a low seat cap. Fine at one user, punishing at four. Look at the price of the plan you will be on in a year.
2. Scheduling on one plan and invoicing on another. The savings come from the two being joined up, so paying to separate them is paying for the problem.
3. Tracking you do not need. Live vehicle tracking and route optimisation sell well and suit a fleet of fifteen. With three vans and a known patch, the person driving already knows the quick way round.

Where Dispatch fits

Dispatch has a free plan for a single user, and every feature is on every plan: paid plans buy seats and report templates, not capability. So the scheduling, the quoting, the invoicing and the customer emails are the same on the cheapest plan as on the dearest. The figures are on the pricing section of the home page.

Scheduling itself is a week grid. Drag a job onto a day, timed or all day, assign it to a person, add a note. Double bookings warn rather than block, which matters in a trade where you sometimes genuinely do want two things on one slot. When you book, you can tick to email the customer, and they get a confirmation when the visit is booked, moved to a different day or cancelled.

Engineers can put their own jobs into their existing calendar app as a private read-only feed, or get an email invite per job. It is one way, out only, off until they switch it on, and only the job number and the site postcode travel. The detail stays in the app where the permissions are.

The whole thing runs in a phone browser, so the cost of putting a fourth engineer on the schedule is a seat, not a device.

Making it cheaper still

Two habits save more than any feature. The first is booking by area rather than by order of arrival: a day that runs across one postcode district beats a day that crosses town twice, and the map view with a radius search makes those clusters obvious.

The second is protecting a slot. Most trades businesses need one or two flexible hours a day for the emergency that will arrive anyway. Booking the week solid guarantees that every callout breaks a promise to someone else.

Neither costs anything, and both are easier once the week is somewhere you can actually see it rather than reconstructed each morning out of a chat thread.

The honest caveats

It needs a connection. There is no offline mode, so an engineer in a basement or a plant room reads the job before they go down and updates it when they come back up.

There is no live vehicle tracking and no automatic route planning. For a small team that is usually a relief rather than a gap, but if you dispatch fifteen vans across a county, you want a different class of product and you should expect to pay for it.

If you are weighing this up alongside the wider question, choosing job management software covers the rest of the loop, and scheduling a small team goes deeper on the week itself.