Dispatch, scheduling & load board

3 min read Updated 7/7/2026 3 views

Dispatch, scheduling & load board

Plan the week, publish it, and let drivers self-serve the rest — without the phone tree.

The short version
FAST turns dispatch into a shared plan. Build the week, publish it so every driver sees their runs instantly, post open runs to a load board drivers grab from their phones, and handle time-off in the same place — so coverage happens without a dozen calls.

Dispatch shouldn’t run on phone calls and memory

At most carriers, the schedule lives in one person’s head and gets communicated by text and phone call. When a run needs coverage, it’s a scramble; when the plan changes, half the drivers don’t get the update; and when that person is out, the operation slows to a crawl. Dispatch should be a shared plan everyone can see — not a bottleneck.

The week’s plan lives in one person’s head and a stack of texts.
Covering an open run means calling down a list until someone says yes.
A schedule change doesn’t reach every affected driver.
Time-off requests live somewhere separate from the schedule, so conflicts surprise you.
FAST dispatch scheduling and load board
Schedule Tools — plan runs, publish the week, and work the load board of open runs and grabs.

Plan it, publish it, let drivers grab it

Plan & publish runs
Build the week and publish it so every driver sees their assignments instantly.
Driver grabs
Post open runs; drivers claim them from the app, and you approve with a tap.
Auto-publish & load board
Keep coverage moving with an open-run board instead of a phone tree.
Time-off in one place
PTO and unpaid requests land where you schedule, so you see conflicts before they happen.

Coverage without the calls

Post the runs you need covered and let drivers claim them from the load board — you just approve. Instead of working down a call list at 5 a.m., you watch open runs get picked up. And because dispatch and the driver app are the same system, a change you publish is on the driver’s phone live, with no follow-up text.

One shared plan the whole team can see — not a bottleneck in one person’s head.
Open runs covered by drivers grabbing them, not by a phone tree.
Schedule changes that reach every affected driver instantly.
Time-off and conflicts visible before they wreck the week.
Turn dispatch into a shared plan
Publish the week and let drivers grab open runs from their phones.
Get started →
Super easy — getting set up was straightforward.
Robynn · Koda Express · Very Satisfied

Dispatch and the driver app are the same system. Publish a change and it’s on the driver’s phone live — no texts, no re-sends.

Frequently asked questions

Can drivers pick up extra runs themselves?

Yes. Open runs go to a load board; drivers grab what they want and dispatch approves. It fills coverage without the calls.

Does a schedule change reach the driver automatically?

Immediately. The driver’s schedule updates live, so reassignments don’t need a follow-up text.

Where do time-off requests go?

Into the same place you schedule, so PTO and unpaid requests show up as conflicts before you publish the week.

Do drivers need a separate app for their schedule?

No — it’s the same FAST driver app they use for pay and forms, so there’s nothing extra to install.

See plans & get started
Was this helpful? Contact support