Dispatching a runner

Create the errand with an address, assign it to whoever is nearest on the map, and watch the status change as they pick it up. Clicking the errand pans the map to them.

The Errands dispatch console in the project workspace

A worked example: a lens at the rental house

  1. Look at the map first

    Two runners are sharing location. One is twenty minutes from the rental house; one is across town. The map is answering the dispatch question before you’ve created anything.

  2. Create the errand

    New Errand: title “Collect 40mm from Panavision”, the address, a due time, and notes such as the order number and who to ask for. The address is what gives the runner navigation in the app.

  3. Assign the near one

    Pick the runner from your crew. It appears in their app immediately, with the address and directions.

  4. Watch it move

    Status flows back from their app: AssignedEn routeDone. You don’t ask, and they don’t have to tell you.

  5. Locate them when you need to

    Click the errand and the map pans to whoever it’s assigned to. That single interaction is why the map, the chat and the board share a tab. The dispatcher’s question is never “where is everyone”, it is “where is the person doing this”.

  6. Override when reality intervenes

    Reassign on the fly, or mark something done yourself when the runner’s phone is dead. The board is a tool, not an authority.

A crew member who hasn’t paired a device can be assigned, but the errand won’t appear in any app until they do, and the form tells you so. Location sharing is opt-in per device, so a runner who hasn’t enabled it is not on the map.