Dispatching a small crew: scheduling board best practices

Dispatching a small crew is a strange job. With three technicians it feels like you could do it on a whiteboard. With eight, one sick call can wreck the whole day. Either way, the person running the board is making dozens of small decisions that decide whether the crew is profitable and whether customers call back angry.

This post is a set of habits that keep small-crew dispatch calm. They work on a whiteboard, a spreadsheet, or software. Where it helps, we note how the dispatch board in LLUMIFIELD supports them.

Lay out the board by technician, not by time

A calendar view answers "what is happening at 10 am?" A dispatch board should answer "what does each tech's day look like, and who has room?" That means one lane per technician, with jobs as cards along the day or week.

Keep three things visible at all times:

• Unassigned jobs. Work that is booked but has nobody on it is the most dangerous thing on your board. It belongs in its own column you look at every morning.
• Who is out. Approved time off should show on the board, not live in someone's inbox.
• Where jobs are. A map next to the board stops you sending one tech across town twice.

LLUMIFIELD's dispatch board shows technician lanes in a day or week view, an unassigned column, approved time off, and a live map, and you drag cards between lanes and days to reassign or reschedule. Overlapping jobs for the same technician are flagged as a double booking.

Plan the week, publish it, then protect it

The best dispatchers plan in two passes:

1. End of the week: lay out next week's known work. Recurring maintenance, multi-day installs, callbacks.
2. Each afternoon: lock tomorrow. Fit in new requests, confirm parts, and send reminders.

A draft schedule should not reach techs or customers until it is ready. LLUMIFIELD lets you keep appointments unpublished while you work on them; unpublished work stays off technicians' screens, and no customer reminders go out for it, until you publish it. Recurring and multi-day jobs are supported, so a three-day install is one job, not three you have to keep in sync.

Build in buffer

Every job runs long sometimes. If your techs' days are packed edge to edge, one overrun pushes every later customer and you spend the afternoon apologizing.

• Add drive time between jobs, based on real distance, not a flat guess.
• Leave a floating slot each day, or one per tech on busy days, for emergencies and overruns. If nothing comes up, pull tomorrow's first job forward.
• Book in windows, not exact times. "Between 8 and 10" is a promise you can keep; "8:15" is not.

When you schedule a new job in LLUMIFIELD, it can suggest route-aware time slots that favor openings near jobs a technician already has that day, so the drive time works for you. You can also set up time windows such as Morning and Afternoon as quick picks.

Route each technician's day

The order of stops matters as much as the stops themselves. A good route cuts drive time and makes ETAs believable.

Once a tech's jobs for the day are set, put them in a sensible order. LLUMIFIELD has a route optimizer that calculates a better stop order for a day, which you can review and apply or open in your maps app. Technicians get Directions from each job card.

Match skills, not just availability

"Who is free?" is the wrong first question. "Who can do this job well?" is the right one. Keep it simple: know which techs handle which types of work, and assign accordingly. Pair a junior tech with a senior one on jobs that need two people. LLUMIFIELD lets you put more than one technician on an appointment, and you can control which staff are offered for each service on your online booking page.

Handle the sick call in five minutes

It is 6:45 am and a tech is out. A calm process beats heroics:

1. See the damage. Pull up the absent tech's lane for the day.
2. Triage. Emergencies and jobs with parts already ordered come first. Routine maintenance can move.
3. Reassign what you can to techs with room nearby.
4. Move the rest to the next open day, and tell those customers before they wait at home.

In LLUMIFIELD you can select several jobs at once and move them together, and each job card has a menu with shortcuts like Tomorrow, same time, Next week, same time, and Same time, another technician. Moves can be undone if you slip, and a moved job's pending reminders move with it. A board move does not text the customer on its own, so tell them yourself; the card menu can send a reminder.

Fit in the emergency without wrecking the day

When a no-heat call comes in at 11 am:

• Check the map for the nearest tech whose current job is finishing soon.
• Use your floating slot if you kept one.
• If you have to bump someone, bump the most flexible job (routine maintenance) and call that customer yourself.
• Charge for it. Emergency or after-hours rates exist for exactly this.

Keep customers informed automatically

Most "where is my tech?" calls are avoidable. Customers relax when they know what is happening:

• Reminder the day before, by text and email.
• On My Way with an ETA when the tech leaves the previous job.
• A heads-up if things slip, sent by the dispatcher, not discovered by the customer.

LLUMIFIELD sends appointment reminders by SMS, email and push, and technicians tap On My Way from their Today view to send the customer an ETA text. You can also send a reminder by hand from the dispatch board.

Give technicians one screen

Technicians should not have to interpret the dispatch board. They need their day in order, the address, the scope, and the customer's history. LLUMIFIELD's Today view gives each technician their route and next stop, with the time clock, completion checklists with photo proof, signatures and job chat on the job itself.

Review the board once a week

Spend fifteen minutes every Friday looking back:

• Which jobs ran long, and was it the job type or the estimate?
• How many jobs sat unassigned for more than a day?
• Which customers had to be rescheduled, and why?
• Did any tech drive far more than the others?

Small patterns, fixed weekly, add up to a crew that is on time.

A daily dispatch routine

1. Morning: check unassigned jobs and absences; confirm every tech has a full, routed day.
2. Midday: check progress, respond to new booking requests (see online booking without phone tag), fit in emergencies.
3. Afternoon: lock and publish tomorrow; send reminders.
4. End of day: make sure finished jobs are invoiced (see getting paid on site).

Try it with your own crew

The fastest way to judge any dispatch board is to rebuild one real, messy day in it. Start a 14-day LLUMIFIELD trial (no credit card), add your techs and a week of jobs, and try the sick-call drill. Every user is included in one flat plan, so adding the whole crew costs nothing extra: see pricing, the comparison page, or our 2026 field service software roundup.

Frequently asked questions

How should a small crew lay out a dispatch board?

One lane per technician, with jobs as cards across the day or week, plus a column for unassigned jobs, visible time off, and a map. That answers who has room and where they are, not just what happens at a given time.

How much buffer should I leave between jobs?

At least the real drive time between stops, plus a floating slot each day for overruns and emergencies. Booking customers into arrival windows instead of exact times makes the schedule easier to keep.

What should a dispatcher do when a technician calls in sick?

Pull up that tech's jobs, prioritize emergencies and jobs with parts ordered, reassign what you can to nearby technicians, and move the rest to the next open day, telling those customers before they wait at home.

Start your free trial