Skip to main content
The dispatch board is where the day’s work gets allocated: open jobs in columns by where they have got to, technicians, crews and suppliers in a rail down the right, and a drag from one to the other. Open it from Work → Dispatch. You need View the dispatch board; assigning from it needs Assign or reassign work orders.
If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules, or it may not be included in your plan.
The dispatch board, with jobs in columns and technicians in the rail The dispatch board, with jobs in columns and technicians in the rail

The summary line

The board covers the sites chosen in the site switcher at the top of the screen. The switcher is a tree with checkboxes, so ticking a region or business unit covers every site under it at once — a supervisor running several plants can dispatch across all of them from one board. See Navigating.

Board and Map

Board and Map are two views of the same jobs. The rail stays on the right in both, because it is what the board is for.

Board

The columns come from your organisation’s lifecycle, not a fixed list: The working and waiting columns take their names from your statuses, so renaming a status renames its column. Each column shows a count. Each job card shows the work order number (a link to the job), its priority or emergency, the title, the asset, who holds it, the time to its promised time (“in 3h 27m”) or how late it is (“2h 3m late”), how long somebody has been checked in (green while somebody is on it now), and N short when its readiness check finds something missing.

Map

Pins are jobs — grey unassigned, amber emergency, red past their promised time. Names are technicians; a dashed line joins a technician to the job they are on, drawn straight because nothing here has routed a van. A number is several jobs close together or at one site, ringed in the colour of the most pressing — click it to separate them. Technicians based at one set of coordinates are fanned around it so each name can be dropped on. Click a name for their day, or drop a job onto one. The map needs a connection to the map tile service; where your network blocks it, the pins appear on a plain background.

The rail

Technicians lists your technicians, each with: Crews & suppliers lists crews (how many of their people are free, and how many open jobs the crew holds) and suppliers (their committed response time, or “no committed response”, and their open jobs). Click a technician with no job picked up to see their day: Availability, On shift (until when, or “not rostered now”), Based at, Current job, Next job, Open work, Distance and Skills.

Assigning a job

Drag a job card onto somebody in the rail or on the map. On a touchscreen, tap a job to pick it up (“number picked up — choose somebody on the right.”), then tap who should take it. The rail then reads Who can take number?

Dropping a job does not assign it

The assignment preview, listing each check for a job dropped on a technician The assignment preview, listing each check for a job dropped on a technician When you drop a job, the board asks what would happen and shows you, before anything changes. The preview names the job and the person, and lists each check with a tick, a warning or a stop: The footer says how many things are worth knowing. Then you decide:
  • With nothing stopping it, Assign hands the job over.
  • When something stops it, the preview says “N things stop this assignment. It can still be made, with a reason.” Type why you are going ahead anyway — it is recorded against the job — and press Assign anyway.
  • Cancel leaves everything as it was.
A board that assigned on drop would be a board people are frightened to touch, and every check it silently passed would be one nobody was shown. The checks are advice, not locks — sometimes the part arrives at ten and the job starts at eleven — but the board makes sure you were told, and a stop needs a reason on the record.

Unassigning

To take a job off somebody, open the job and press Open in its header — the Unassign move in the default lifecycle. It returns to the Unassigned column.

What this screen is not

Dispatch is about today. For whether the week can absorb the work that is due — technician hours against planned load — use the capacity plan. The plan says whether the days ahead can take the load; the board says who is on what right now.