Manual Status Updates

Overview

The driver mobile app triggers most status transitions automatically — a driver tapping "Start trip" in the app moves the mission to IN_PROGRESS without any operator action. However, there are situations where an operator must update a status manually from the back-office:

• The driver has no connectivity and cannot use the app
• A status was set incorrectly and must be corrected
• An on-site incident requires an immediate status override
• A late confirmation was received by phone rather than through the app

The Status Update dialog (screen D-04) is available from the Mission Detail panel or the Order Detail header. It applies to both mission-level and order-level statuses.

---

Opening the Status Update Dialog

1. Open the Order Detail view from the pipeline (click any row)
2. For a mission status update: click the kebab menu (⋮) on any mission row → Update status
3. For an order status update: click the Actions button in the order header → Update status

The dialog displays the current status and a dropdown of valid next statuses based on the current state machine.

---

Valid Transitions

The system enforces state machine guardrails. Not all status changes are permitted. The following tables show the allowed transitions:

Mission Status Transitions

Order Status Transitions

The dropdown in the dialog only shows statuses that are valid from the current state. Attempts to reach an invalid transition (for example moving a COMPLETED mission back to PENDING_ASSIGNMENT) are blocked by the UI and the API.

---

Adding a Reason

After selecting the new status, operators can — and are encouraged to — add a reason note in the free-text field. While the reason is optional for most transitions, it is highly recommended for:

• Any backward transition (e.g. reverting ACCEPTED_BY_DRIVER to ASSIGNED)
• Any override of an automatically-set status
• Any no-show or cancellation

The reason text appears alongside the status change in the mission event history and is visible to anyone with access to the order.

---

Audit Trail

Every manual status update is recorded in the event history with:

This audit trail is immutable — it cannot be deleted or edited after the fact. It is available from the Mission Detail panel under the Event history tab and from the Order Detail view.

---

Common Scenarios

Driver Lost Connectivity

The driver completed the trip but could not tap "Complete" in the app due to poor network coverage. The operator:

1. Opens the mission
2. Clicks Update status → selects COMPLETED
3. Adds reason: "Driver confirmed by phone — no connectivity at destination"

Incorrect Status Set by Mistake

An operator accidentally triggered IN_PROGRESS too early. To revert:

1. Open the Mission Detail
2. Click Update status → only valid previous steps are shown
3. Note: IN_PROGRESS cannot revert to ASSIGNED directly — the state machine does not allow backward moves past ACCEPTED_BY_DRIVER; contact support if a full revert is needed

Late Confirmation

A driver called to confirm acceptance but is not yet active in the app. The operator advances the mission from ASSIGNED to ACCEPTED_BY_DRIVER manually, with a reason note referencing the phone confirmation.