How to Run a Daily Crew Dispatch So Nobody Shows Up at the Wrong Site

It's 5:50 in the morning and the group chat is already busy. A photo of the whiteboard went out at 9 last night, then two corrections at 10, then a text from the operations manager at 5:30 saying the Kerrisdale crew is now going to Burnaby because the inspector moved. Half the crew saw it. The other half are parked outside a locked gate in Kerrisdale, on the clock, while a foreman makes phone calls.

Most contractors run dispatch this way for years, and it mostly works, because one person holds the whole plan in their head and is very good at it. The trouble starts at about the third active site, or the first week that person is away. The whiteboard isn't the problem. The problem is that nobody decided when tomorrow's plan is final, who is allowed to change it, and how a change reaches the people it affects.

Here's how I'd set up a daily dispatch that survives a busy week.

Dispatch is a decision, not a document

The schedule tells you what should happen over the next few weeks. Dispatch decides who goes where tomorrow morning, with what. Those are different jobs, and mixing them is where most of the confusion comes from.

The three-week look-ahead is the input. It says the east footings form up Thursday, the rooftop units land Friday, the inspection is booked for Wednesday at 10. Dispatch takes that, checks it against who is actually available and what is actually on site, and produces one answer per crew: address, start time, crew lead, the work, and anything unusual.

If your look-ahead is thin or doesn't exist, dispatch will feel chaotic no matter what tool you use, because it's being asked to plan and assign at the same time, at night, from memory.

Pick a cutoff and hold it

Choose one time each day when tomorrow's board is final. Early afternoon works for most contractors, somewhere between 1 and 3, because that's late enough to know how today went and early enough that crew leads can load trucks and order anything missing before the supplier closes.

Before the cutoff, anyone can ask for changes. After it, the board is published and changes go through one person. That single rule removes most of the evening texting, because people stop assuming the plan is still open for discussion at 9 at night.

There will still be changes after the cutoff. Inspectors move, concrete trucks get cancelled, somebody's kid is sick. The cutoff doesn't stop that. It makes late changes visible as exceptions instead of the normal way of working.

One owner, and a backup who has done it

Somebody owns the board. In a small company that's often the operations manager or a senior super. What matters is that it's one named person, and that crew leads, PMs and the office all know that person is where requests go.

The owner also needs a backup who has actually run dispatch, not just watched it. Have the backup build the board one day a week, every week. The first week the owner goes on holiday is a bad time to discover the plan lived in their head.

Check the constraints before you assign

Most wrong-site mornings are really missing-constraint mornings. The crew went where the board said, but the board didn't know the gate code changed, or that the lift was still at the other job, or that nobody on that crew holds the ticket the task needs.

Before publishing, run through the same short list for every crew:

• Access. Site open, gate code current, parking or loading arranged, the GC expecting you.
• Predecessors. The work ahead of you is done. Nothing kills a morning like arriving to rough-in a floor where the framers are still framing.
• Materials. Delivered to site, or on the truck tonight. Check the procurement log, not memory.
• Equipment. Lift, compactor, core drill: where it is now and how it gets to tomorrow's site.
• People and tickets. Enough hands, and at least one person holding whatever the task requires, whether that's fall protection, confined space entry, a gas ticket or a specific equipment operator qualification. The rules come from your trade and WorkSafeBC, so check them for the actual task rather than trusting a general list.
• Inspections and deliveries. Booked times written on the board, with who needs to be there.

This takes ten minutes per site the first few weeks and three once it's a habit. It's the ten minutes that saves the hour of phone calls.

Send each crew its own message

A photo of the whole board is a lot of information for a crew lead who needs one line. Send each crew lead their assignment directly, in the same format every day: date, site address, start time, crew list, the work, the notes. If the notes are empty, say so.

The same format matters more than the channel. Text, email, WhatsApp or an app all work if the message looks identical every day, because the crew lead learns where to look. Ask for a reply of any kind. A thumbs up is fine. The owner then knows by 5 p.m. which crews haven't seen tomorrow's plan, instead of finding out at 7 a.m.

Late changes reach the people, not the chat

When something changes after the cutoff, the owner updates the board and then calls or messages each affected crew lead individually, and gets an acknowledgement. Not a post in the group chat. Group messages are where changes go to be half-read.

There's a cost reason to be strict about this in BC. Under the Employment Standards Act, an employee who reports for work is owed at least two hours' pay, and four if they were scheduled for more than eight hours, with a narrower rule when work stops for reasons entirely outside the employer's control, like weather. Collective agreements can set their own terms on top. Either way, a crew sent to the wrong site hasn't just lost the morning. You're paying for it, and the time lands on whatever job the foreman codes it to. Check the Act and your agreements for how it applies to your people.

Close the loop with the timesheet

The dispatch board says where each crew was supposed to be. The daily timesheet says where they were. Compare the two once a week.

When they match, the board is doing its job. When they don't, the gap is useful. A crew that keeps getting pulled off one job to cover another is a staffing signal. A job that never gets its planned crew is a scheduling signal. Hours coded to a site nobody was dispatched to are either a correction the board missed or a coding error in the timesheet, and either one is worth fixing that week.

This is also the cheapest way to see idle time. Fifteen minutes on a Friday, looking at where crews waited, doubled up or went short, turns next week's board into something slightly better than this week's.

Whiteboard, spreadsheet or software

A whiteboard works for one or two crews and an owner who is in the office every afternoon. Take a photo at the cutoff so there's a record, because a whiteboard has no history.

A shared spreadsheet, one row per crew per day, carries most contractors much further than they expect. It keeps history, it can be filtered per crew lead, and it sits next to the look-ahead and the procurement log. It starts to struggle when you need to see equipment and people together across several weeks, or when you have enough crews that double-bookings slip through.

Dispatch software earns its place once you're past that point, and there are plenty of good options. Before buying, check two things. Can crew leads receive and acknowledge their assignment without a paid seat each? And does the tool share its job and crew lists with your timesheet system, so the weekly comparison doesn't turn into retyping? If not, you're buying a nicer whiteboard.

Whichever you pick, the cutoff, the owner, the constraint check and the one-to-one late change do the actual work. The tool just holds the result.

If your mornings start with a round of phone calls, it's usually a process gap rather than a software one, and it tends to be a short conversation to find it. A discovery call is a reasonable place to start.