> For the complete documentation index, see [llms.txt](https://docs.shortcutco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shortcutco.com/readme/dispatch/assigning-and-ordering-routes.md). # Assign crews and set the route order Get every stop under a crew, put the stops in driving order, and make a good order stick for next week. This is the core of Dispatch: which crew goes where, and in what order. Everything here happens on the **Scheduled** tab, looking at a single day. ## What "Unassigned" means A stop sits in the **Unassigned** lane (at the bottom of the board, with the crew shown in red as **Unassigned**) when no crew is going to do it. That happens when: * the job doesn't have an owner crew (imported jobs and one-off jobs start this way), **and** * nobody has picked a crew for this particular visit. Unassigned stops don't appear on anyone's phone, so clearing this lane is the first thing to do each day. It also shows up as **No crew** on the [Needs attention](/readme/dispatch/needs-attention.md) tab, in case you miss it here. ## Four ways to assign a crew Pick whichever is closest to hand. They all do the same thing: move **this visit** to the crew you choose. 1. **Click the crew chip.** In the **Crew** column, the crew name is a button. Click it and pick a crew from the list. This is the fastest way for a single stop. 2. **Drag the row.** Grab the grip at the row's left edge and drop it into another crew's lane. Drop it between two stops and it lands right there in the order. You can't drag a stop *into* the Unassigned lane; use the crew chip if you need to take a crew off. 3. **Select several rows, then Crew.** Tick the checkboxes (shift-click selects a range), then click **Crew** on the black toolbar at the bottom and pick a crew. Good for handing a whole street to someone. 4. **Open the stop → Reassign Crew.** Click the customer name to open the stop's detail panel and click **Reassign Crew**. This is the only place with a second question (see next section). ### This visit only, or from now on? When you reassign from the stop's detail panel and the job is recurring, you'll see two options: * **This visit only** — *Future visits stay with the owner crew.* Next week's visit goes back to the crew that owns the job. * **This and future visits** — *Makes the selected crew the job's owner.* Every visit from here on goes to the new crew. Every other way of assigning (chip, drag, bulk toolbar, row menu) is **this visit only**. That's on purpose: a one-day shuffle shouldn't quietly rewrite who owns a customer. After you move stops with the toolbar's **Crew** button, or drag them into another crew's lane, a dark pill in the bottom-right corner says so, for example **"2 stops moved to Crew B — this visit only."** It has two buttons of equal weight: * **Keep future visits with Crew B** makes Crew B the owner of those recurring jobs, the same as choosing **This and future visits**. It only appears when a recurring job moved. * **Undo** puts the stops back with the crew they came from. After a drag, **Undo** is on the route pill that appears beside it (next section). A stop moved off its owner crew for one visit shows a small amber arrows icon beside the customer name. To make the move permanent later, open the stop and click **Keep with \[crew]**. See [Crew ownership](/readme/dispatch/crew-ownership.md#one-off-exceptions). ## Route order: the numbers on the left The number at the left edge of each row is that stop's place in the crew's run: 1 is first. Crews see their stops on their phone in exactly this order. Unassigned stops show a dash instead of a number because there's no route to be part of. **To reorder, drag.** Hover a row, grab the grip that appears at the far left, and drop the row where it should go. The numbers update immediately. Keyboard users can pick up the grip with the keyboard and move the row with the arrow keys. **Reordering is switched off** in three situations, and the grip greys out with a tooltip telling you which: * **A filter or sort is on.** You can only reorder a lane when you can see all of it, so clear the filter or sort first. * **You're looking at more than one day.** Route order is set per day, so switch from **This week** or a custom range back to a single day. * **The lane is Unassigned.** **New stops go to the end.** When a visit is scheduled, it's added as the last stop of its crew's day. If you've saved a regular order for that weekday (next section), it slots into place instead. ## Making an order stick: "Keep every Tuesday" After you drag, a dark pill appears in the bottom-right corner for about ten seconds. It names the crew, says what changed, and offers two buttons of equal weight: > **Crew A** Route reordered — today only. **Keep every Tuesday** **Undo** * **Keep every Tuesday** saves the current order for this crew as their regular Tuesday order. Existing Tuesday visits for the next eight weeks are put in that order, and any new Tuesday visits scheduled later drop into place automatically. Nothing else changes: Wednesday's order stays Wednesday's. The pill confirms with **"Saved the Tuesday order (3 changes)."** * **Undo** puts everything back the way it was. This is your only undo for a route change, so click it while the pill is up. Hovering the pill, or tabbing to its buttons, keeps it open. * Do nothing and the order you set stays for today only. Next Tuesday keeps whatever order it had. The **Keep every…** button only appears when at least one stop from a recurring job moved. If you only moved one-off stops, you'll just see **Undo**. The same pill appears in two other places: * **When you move stops to another crew** with the crew chip or a drag: **"3 stops placed — today only."** with **Keep every Tuesday** and **Undo**. * **When you reschedule stops to another day:** **"2 jobs moved to Sep 12, 2026 — this visit only."** with **Change service day going forward** and **Undo**. **Change service day going forward** moves the whole series to that weekday from the next visit on, and the pill confirms with **"Service day is now Friday for 2 jobs, from next visit on."** To reschedule, use **Reschedule** on the row, or tick several rows and click **Reschedule** on the black toolbar. A **Move 3 services** window opens; pick the new date. When it saves, the window closes, your selection clears, and the pill appears. ## What your crew sees * **Today, in your order.** The Worker app's **Today** screen lists the crew's stops in the route order on this board. * **A push notification when their day changes.** If you add a stop to a crew's day or take one away (assign, reassign, reschedule, cancel), everyone on that crew gets a push notification titled **"Your route changed"** that names the stop, such as *"Added: Jane Doe, 123 Elm St"* or *"3 stops added, including Jane Doe, 123 Elm St"*. Dispatch waits about a minute after your last change so a burst of edits becomes one notification, not ten. * **A push when their next stops change order.** A reorder (by hand, with Optimize, or with the Assistant) notifies the crew only when it changes the order of their **next three stops** that haven't started yet. The notification says where to go next: *"Next: Jane Doe, 123 Elm St"*. Swapping two stops later in the day doesn't send anything, and neither does a reorder you undo within the minute. * **Only today's route.** Changes to *future* days never send a push. * **You don't get notified about your own changes**, even if you're also on the crew. * **Today marks what changed.** On the crew's Today list, a new stop shows **Added** and a stop that changed place shows **Moved**. A stop taken away is listed at the top under **Removed from your route**. In the app, if Today is open when the push arrives, the list refreshes on its own. See [Worker app overview](/readme/worker-app/worker-app-overview.md#your-route-changed). Crew members can switch the notification off under **Settings → Notifications → Your route changed** (click your name at the bottom-left of the sidebar, then **Settings**). ## Related pages * [Dispatch overview](/readme/dispatch.md) * [Crew ownership (recurring jobs)](/readme/dispatch/crew-ownership.md) * [Optimize routes and the Assistant](/readme/dispatch/optimize-routes-and-the-assistant.md) * [Route map](/readme/dispatch/route-map.md)
Still stuck? Email **** with the date, the crew, and what you were trying to move.