Bringing order details to dispatch

The dispatch team re-entered order and jobsite details on a shared delivery board, even though those facts already lived in an order system and contract records. Rebuilding the board by hand added a daily copying task.

The shared board is what dispatch uses to coordinate deliveries, while order and jobsite facts are stored elsewhere. Re-keying them creates opportunities for stale addresses or incorrect job references to reach the people planning the day.

A desktop workflow pulls open orders, joins jobsite details from contract records, and previews proposed rows before writing to the shared delivery board. It fills known fields while leaving courier, truck type, and other judgment calls to dispatch.

1. 1

   Collect open orders

   Retrieve the relevant sales orders and allow an operator to select specific orders when needed.

2. 2

   Join and preview details

   Match contract jobsite information to each order and show the proposed board rows before any write.

3. 3

   Update with a fallback

   Write confirmed known fields while leaving courier and truck choices to dispatch, with an export path for API outages.

After an operator confirms the preview, known order and jobsite details are written to the board. Courier and truck-type fields remain under human control, and an export fallback supports the process during API outages.

The operator handoff includes a maintenance guide and a running edge-case log documenting setup, routine operation, and known exceptions. These references help the team operate the workflow and diagnose cases that need attention.