Job scheduling for a small trades team

Last updated: August 2026

The problem is copies, not the calendar

Ask a struggling three-van business where the schedule lives and you will get four answers: the whiteboard in the office, the owner’s phone, a group chat, and whatever each technician wrote on the back of a job sheet. None of them is wrong, exactly. They are just never the same at the same time.

Every scheduling disaster in a small trades business traces back to that. Two vans sent to one address. A customer waiting for someone who was reassigned that morning. A cancellation that reached the office but not the technician already parked outside.

The fix is not a more elaborate system. It is one schedule that everyone reads from, updated in one place.

What a scheduled visit actually needs to carry

A time and a name is not enough. By the time a technician is looking at tomorrow, they need to know where they are going, what they are walking into, and what has already been agreed. A useful calendar card carries:

• The job reference, so it ties back to the report and the quote rather than floating free.
• The time, and honestly how long you think it will take.
• Where it is: the town and postcode at a glance, because travel time between jobs is the thing small teams consistently underestimate.
• What was reported, including the customer’s own photos, so nobody arrives without the right parts.

That is roughly what a Dispatch calendar card shows: the job reference, the time, and the town and postcode. The full fault report, the photos and any quote sit on the job behind it.

Handle clashes as warnings, not walls

Software that refuses to let you double-book sounds sensible until you use it. Real weeks contain a ten-minute call squeezed between two jobs, a second technician joining halfway through, and a visit that deliberately overlaps because two people are meeting on site.

A scheduling tool that blocks those cases does not prevent the mistake; it just pushes the real schedule back onto the whiteboard, and now you have two systems again. Dispatch warns on a clash rather than blocking it, on the basis that you know your week better than the software does.

Tell the customer, automatically

A large share of the phone calls a small trades office takes are some version of “are you still coming?” Every one of those is a customer who was told something once, by someone, at some point, and has no way to check.

Confirming automatically when a visit is booked, moved or cancelled removes most of those calls. Dispatch sends the customer a confirmation on each of those three events, which is exactly when they would otherwise have had to ring you to find out.

Match the view to the question

Different questions want different shapes of the same data, which is why one view is rarely enough:

• The week calendar answers “who is where on Thursday?”
• A list answers “what is outstanding, oldest first?”
• A board answers “what is stuck, and at which stage?”
• A map answers “who is nearest to this emergency?”, the question that actually decides your afternoon.

Dispatch offers all four over the same jobs, so switching view does not mean maintaining a second copy.

Decide who is allowed to move things

As soon as more than one person can reschedule, you need to agree who does. The usual sane arrangement is that the office moves bookings and the field team updates job status: technicians say what happened, the office decides what happens next.

Dispatch has fixed roles for this: Owner, Office Admin and Field Technician, each with defined permissions. The roles and permissions page sets out exactly what each one can do, so you can decide who gets which before you invite anyone.

Once the week is under control, chasing unpaid invoices is usually the next thing quietly costing you money.