Multi-crew scheduling: how to run three teams without cloning yourself

By the SKEDS Team · 9 October 2026 · 6 min read

There's a wall every growing trade business hits, usually somewhere between the fifth and eighth person on the tools. One crew, the boss can run from memory. Two crews, from a whiteboard and a lot of phone calls. But at three crews across three sites, the boss becomes a full-time human router — planning everyone's day, answering everyone's questions, driving between sites to see what's actually happening — and the business's growth is now capped by one person's bandwidth and one person's phone battery.

Multi-crew scheduling is the discipline of breaking that cap. It's part structure, part software, and the businesses that get it right grow past the wall; the ones that don't stall at it, exhausted.

Crews as units, not just people

The first shift is conceptual: stop scheduling seven individuals and start scheduling stable crews. A consistent pairing — a lead plus a second, or a lead plus an apprentice — builds its own rhythm, quality standard and accountability. The crew lead owns the site day-to-day; the office schedules the crew as a unit and only breaks pairs deliberately (to cover leave, or to seed a new crew with an experienced hand).

On the SKEDS board, each crew is a swim lane. The week reads at a glance: Crew A on the renovation through Thursday, Crew B on service work clustered by area, Crew C free Friday afternoon — which is where the new booking goes. The clash you'd have created by memory is visible before you promise it, which is the whole anti-double-booking discipline at crew scale.

The job pack replaces the morning briefing

The hidden cost of multiple crews is question traffic: every crew that doesn't know something rings the person who does. The cure is making the job itself carry the answers. Every job dispatched in SKEDS holds the address, scope, site contact, access notes, drawings, photos and safety forms — so the crew lead opens their phone at 7am and has everything the boss would have told them, without the boss saying it. Businesses that make this switch report the same thing: the phone goes quiet, and the quiet is growth headroom.

Live status beats the drive-by

The multi-site supervision instinct is to drive the loop — but a boss doing site visits all day is your most expensive employee producing nothing billable. Live job statuses invert the model: crews update en route / on site / complete as they work (two taps, even offline), progress photos flow back from each site, and the office sees the whole operation on one screen. Now presence is spent where it's needed — the site that's gone quiet, the job running long — instead of spread evenly over sites that were fine. The same live picture is what makes same-day dispatch decisions possible when the emergency call lands: you can see who's genuinely nearest and freest, not who answers first.

Load balancing: protect the people the work prefers

Left alone, work flows to the most reliable crew until you burn them out — the strongest lead gets the hardest jobs, the most hours and, eventually, a resignation. A visible board makes load imbalance obvious weekly instead of anecdotal quarterly: jobs per crew, hours per crew and callback rates sit in the reports, and rebalancing becomes a deliberate scheduling act. The same numbers reveal the opposite problem — the crew whose days are mysteriously short — without a confrontation, because the data does the noticing.

Mixed workforces on one board

Real multi-crew businesses are rarely all-employee: there's the subbie crew for overflow, the specialist brought in per project, the apprentice rotating between leads. They all belong on the same board, with the same job packs, because a plan that lives in two systems is two plans. Per-user pricing that doesn't punish casual users matters here — check SKEDS pricing against what enterprise tools charge for the same seat.

The weekly rhythm that holds it together

Software carries the information; a light rhythm carries the decisions. The pattern that works: a Friday planning pass where next week's board gets shaped (contract days blocked, rounds routed, gaps identified), a two-minute Monday message to crew leads confirming the week, and a mid-week glance at the numbers. Total cost: under an hour. What it replaces: the constant, reactive re-planning that used to be the job.

Frequently asked questions

At what size does a business need multi-crew scheduling? The moment two crews can be in the wrong place at once — typically the second van. The wall just gets more expensive the later you address it.

How do crews take to status updates and time tracking? Fast, when it's framed honestly: fewer interruptions, no Friday timesheet homework, and no more being blamed for scheduling mistakes they didn't make.

Can one person still run the schedule for five crews? Comfortably — that's the point. The board does the remembering; the scheduler does the deciding.