Home
Features
Crew Scheduling, Whiteboard & Dispatch

Scheduling, Whiteboard & Dispatch · Three coordinated surfaces

Plan the season, balance the week, run the day.

Plan the season, balance the week, and run the day from one set of jobs. Dispatch a smarter route today and next week's schedule already has it.

Book a Demo See Pricing

Plan Balance Dispatch

A real week: drag a job to balance it

Most scheduling tools throw today’s optimization away at sundown. We write it back into next Tuesday, and save you 15–25% of windshield time over a season.

Whiteboard demo

Crew Aover

Crew B

Crew Cidle

Crew D

Crew E

Unassigned

MON 5/12

TUE 5/13

WED 5/14

Tap a card to pick it up, then tap a cell to drop, or just drag it. Arrow keys work too.

A landscape crew installing stonework — hardscape crew laying patio pavers on a job site.

What this replaces

Scheduling chaos has a shape, and we built around it.

Most operators run the schedule across four tools that don't talk: a season calendar, a wall whiteboard, day-of group texts, and a billing spreadsheet. Every handoff loses information.

The plan and the day-of don't share a system

The recurrence calendar lives in one app, the whiteboard in another, and the dispatcher's head in a third. When weather hits or a tech calls out, it takes 40 minutes of texting just to know what's still happening.

Today's optimization gets thrown away

Foreman re-orders 14 stops to cut 22 miles of windshield time. Next Tuesday those exact properties hit the schedule again, and the system serves them up in the original arbitrary order. The optimization never compounds.

"Borrow Joe for Friday" turns into a permanent reassignment

You pull a tech from one crew to cover another for one day. Three weeks later he's still assigned to the wrong crew because the system didn't model "borrowed for a date" as different from "permanently swapped." The home crew quietly degrades.

Same jobs, three time horizons

Which surface for which moment

Each surface acts on the same underlying jobs. There's no "schedule a job here, dispatch it over there" double-entry. The split is operational: who's looking at it and how far ahead.

Planning layer

SchedulingAll tiers

Weeks → seasons

The plan: who does what, when, and how often.

Recurrence rules: weekly, biweekly, monthly, quarterly, annual, or anytime
15 service types, each on an explicit job lifecycle
Route-template sequences for repeat stops
Visits auto-created overnight and deduped, so no double-bookings

Used by: office admins, foremen

Balancing layer

WhiteboardProfessional+

Today → next few weeks

The balance: drag-and-drop work across crews and days.

Spot over- and under-staffed crews from a KPI strip
Borrow a tech for one day without losing the home crew
Multi-select a stack and bulk-reassign in one step
"Edit Day" to bulk-move a whole day's visits for weather
AI suggests rebalancing moves you can apply or ignore

Used by: foremen, dispatchers

Execution layer

DispatchCrew+

Today (and day-of-event)

The execution: today's events as a filterable list, with bulk actions and dispatch-note threads.

Routing engine optimizes the day; the foreman locks the order
"Apply to future weeks" saves that sequence, so next week starts optimized
Crew-location breadcrumbs land on a live map
Quick Dispatch fires 100+ visits in one click for storms

Used by: dispatchers, foremen

Whiteboard deep-dive

The dispatcher's one-screen view of the next few days

A drag-and-drop grid: crew columns, date rows. Each cell shows that slot's jobs and the day's effective roster, borrowed members included. Every move sends exactly one notification.

Drag-and-drop grid with capacity bars

Crew columns, date rows, plus an Unassigned column. Capacity bars compare scheduled work to available hours; a KPI strip flags crews over, under, or idle.

Bulk-move up to 200 jobs at once; batches apply cleanly or not at all
Status buckets: overstaffed (over 100%), understaffed (under 70%), balanced, idle
Org-wide totals for scheduled, capacity, and unassigned hours; KPI strip always matches the grid
Completed and cancelled jobs are locked, so finished work can't be quietly restored

Borrow vs. permanent swap

Two distinct flows for two distinct realities. Same-day borrows are honoured by job creation, so a job created mid-day on the borrowing crew picks up the borrowed tech automatically.

Borrow: lend a tech to another crew for a single day; their home crew stays exactly as it was
Permanent swap: rewrites the home crew effective from a date you pick, with a clean audit-log entry
Conflicting borrow + swap on the same person on the same day is blocked: the system asks you to resolve it instead of silently overwriting
The audit log of every borrow and swap is searchable for any date window

Edit Day: bulk weather moves

Re-date every visit on a day to a new date (or just the ones that aren't done yet) optionally moving them to a different crew at the same time. All at once, one notification per affected job.

Same time of day on the new date: each visit's start and end time shift together
Cancel just the unfinished visits: in-progress jobs are skipped so a midday weather call doesn't blow up active work
The Unassigned column is targetable too: clear a column of leftovers in one click
Every action sends a single notification per affected job, not one per surface

AI scheduling assistant

Suggestions you approve. Nothing changes without you.

AI can help propose; the dispatcher disposes.

The assistant asks AI for ranked moves that would balance the day. The model never moves anything on its own. It returns a side panel of suggestions, and the dispatcher picks which to apply. Suggestions cite the specific over- and under-staffed crews so the reasoning is legible.

Every suggested move is checked against your real grid; the AI can't invent jobs
If AI times out, a simpler built-in rule takes over; the page never blocks
Suggestions stay read-only until you apply them; nothing moves in the background
The same panel appears on the Whiteboard, so you apply moves without switching screens

A landscape crew laying fresh sod on a job site — installation work being executed in the field.

Dispatch deep-dive

The day-of operational surface

Where the Whiteboard balances the next few weeks, Dispatch shows what's happening today and lets you act on it in real time. A single page with a simple Events / Plans toggle, set to Events by default, the workflow most operators live in.

Events list with bulk actions

Every visit, meeting, and to-do in the range, filterable by crew, employee, or state. One load, so the list opens fast on weak signal.

Bulk: complete · reopen · move (same time of day) · duplicate · assign crew or employee
Per-row errors: one failure doesn't abort the batch; retry just the rejects
Delete is blocked for in-progress, completed, or storm-active jobs; finish or cancel first
Snow events: Quick Dispatch templates fire 100+ visits in one click. See Snow Ops →

Sequence lock + "Apply to future weeks"

The optimized stop order isn't a one-time win. Locking it writes a per-crew route template with a recurrence: every week or every other week, anchored to that day's Monday. Next time the same properties hit a route plan for that crew, the stored sequence overrides the routing engine's default.

One template per crew + property + sequence; if you re-lock the same set, the most recent sequence wins
Biweekly templates remember the anchor week so they only fire on the right Tuesdays, not every one
Today's optimization becomes every Tuesday's optimization: windshield time compounds the right way
Foreman role and up to apply: the field crew can't accidentally lock a sequence from a half-finished route

The efficient-scheduling flywheel

The work you do today saves you setup tomorrow

Most tools end at step 3. The day's optimization dies at sundown and next Tuesday starts over from scratch. Closing the loop is where the windshield time hides.

The scheduling flywheel: four steps arranged in a loop — 01 Recurrence rule, 02 Whiteboard balance, 03 Dispatch optimize and lock, 04 Apply to future weeks — with the closing arrow from step 4 back to step 1 labelled “loop closed: the step competitors skip”. The center reads 15 to 25 percent windshield time saved over a season.

The flywheel. Most tools end at step 3.

Most scheduling tools throw today’s optimization away at sundown. The route plan dies with the day. Next Tuesday, the same 14 properties hit the schedule in the original arbitrary order. The foreman re-optimizes them by hand, and the cycle starts over.

RootControl writes today’s locked sequence back into the recurrence. Step 4 closes the loop. Next Tuesday’s plan starts already optimized. The only work left is filling in the new date.

What's on which plan

Core scheduling everywhere; Dispatch on Crew; Whiteboard on Pro+

Recurrences, the calendar, and weather integration are on every plan, Solo included. Route optimization, the Dispatch board, and route templates start on Crew. The drag-and-drop Whiteboard, weather auto-holds, Quick Dispatch storm templates, and the AI scheduling assistant unlock at Professional. Multi-location branch scoping is Enterprise.

Capability	Solo	Crew	Professional	Enterprise
Recurrence engine + 15 service types	●	●	●	●
National Weather Service (NWS) weather integration & forecasts	●	●	●	●
Weather auto-holds & auto-reschedule	—	—	●	●
Drag-and-drop Whiteboard + KPI strip	—	—	●	●
AI scheduling assistant	—	—	●	●
Dispatch board + bulk actions + dispatch notes	—	●	●	●
Route optimization	—	●	●	●
Route templates ("Apply to future weeks")	—	●	●	●
Quick Dispatch templates (storm rapid deploy)	—	—	●	●
Multi-location branch scoping for every view	—	—	—	●

Questions we hear

Scheduling, Whiteboard & Dispatch FAQ

What plan do I need for the Whiteboard and Dispatch?

Core Scheduling (recurrences, calendar, weather integration) is on every plan, including Solo. Route optimization, the Dispatch board, and route templates start on Crew. The Whiteboard, weather auto-holds, Quick Dispatch storm templates, and the AI scheduling assistant unlock at Professional. Enterprise adds multi-location branch scoping to every Whiteboard and Dispatch view.

How does "Apply to future weeks" work?

When a foreman locks the optimized sequence in Dispatch, they can save it as a per-crew route template with a weekly or biweekly recurrence anchored to that day's Monday. The next time those properties land on a route plan for that crew, the stored sequence overrides the routing engine's default. Today's optimization becomes every Tuesday's optimization.

Can the AI scheduling assistant move jobs on its own?

No. It returns ranked rebalancing moves as a side panel of suggestions; the dispatcher picks which to apply. Every job and crew the model references is validated against your real grid first, so the AI can't reference a job that doesn't exist. If the AI times out or returns something unusable, the side panel falls back to a simpler built-in rule so the page never blocks on AI.

What's Quick Dispatch and when do I use it?

Quick Dispatch templates are the “schedule 100 visits in one click” surface used during storm and snow events. You pre-build a template (crew + service + a list of customer properties), and during the storm one click creates a Job per property for a target date. Templates live forever; deploying doesn't consume them. The deployed jobs land on the Whiteboard and immediately appear in Dispatch's Events view.

Can I borrow a crew member without permanently reassigning them?

Yes. The borrow flow lends a tech to another crew for a single date; their home crew stays exactly as it was. Same-day borrows are honored at job creation, so a job created mid-day on the borrowing crew picks up the borrowed tech automatically. A separate permanent-swap flow rewrites the home crew from a date you pick, with a clean audit-log entry.

Related capabilities

Explore more of RootControl

Get started

See the three surfaces run on a real week

30-minute walkthrough. Bring your current schedule and we'll set up a live week with your real crews, real properties, and a storm-day Quick Dispatch run.