Direct Assignment

Overview

Direct Assignment (screen G-06) is the manual dispatch mode where you explicitly select a specific driver for a mission. It is the most controlled workflow: you review eligible drivers, their compatibility scores, and any compliance warnings before confirming.

When to use it: use Direct Assignment when you know which driver is best suited for a trip, when a client has a driver preference, or when compliance constraints mean only a small number of drivers are eligible.

---

Opening the assignment wizard

The Direct Assignment wizard opens in two ways:

• From the Dispatch mode modal (G-07): choose Assign directly.
• From the List View: click the Assign action button on any unassigned mission row.
• From the Map View: click an unassigned mission pin, then Assign from here.
• From the Gantt View: right-click an empty slot on a driver row and choose a mission to assign.

---

Eligible driver list

The wizard displays a ranked list of drivers who meet all base eligibility criteria:

Eligibility criteria

1. Availability — no existing assignment overlapping [pickupAt, estimatedEndAt]
2. Vehicle category — driver's current vehicle matches the mission's required class
3. Active licence — VTC licence is valid on the mission date
4. RSE pre-check — no hard RSE violation that would block assignment in strict mode

Drivers who fail any of these criteria are excluded from the list entirely. Drivers with amber (borderline) RSE indicators appear with a warning badge but remain selectable.

Compatibility score

Each eligible driver is scored 0–100 based on:

The staffingSelectionPolicy configured in your organization settings can boost drivers who match preferred criteria (e.g., language, seniority, client history). Higher scores appear at the top of the list.

---

Selecting a driver

Each driver card in the list shows:

• Name, photo, and vehicle plate
• Distance from the pickup point (real-time, based on last GPS ping)
• Upcoming schedule context — next and previous assignments within ±3 hours of the mission window
• Compatibility score badge
• RSE compliance indicator (green / amber / red)

Click a driver card to select them. A confirmation summary panel appears on the right showing:

• Mission details
• Selected driver details
• Any RSE warnings requiring acknowledgement

---

FR394 — Optimistic assignment lock

FR394 — Optimistic Assignment Lock prevents two operators from accidentally assigning the same driver to two different missions at the same time.

How it works

1. When you open the assignment wizard for a mission, the system records a soft lock on that mission in your session.
2. As soon as you select a driver from the list (before confirming), the system places a provisional lock on that driver for the mission time window. This provisional lock is visible to other operators as a "Pending assignment" indicator.
3. When you click Confirm assignment, the system performs a re-verification in real time:
   • Has the driver been assigned to another mission in [pickupAt, estimatedEndAt] since you opened the wizard?
   • Has another operator confirmed an assignment for this same mission?
4. If the re-verification passes, the assignment is confirmed. Driver and mission are locked. Push notification sent.
5. If the re-verification fails (conflict detected), the confirmation is rejected and you see an error message explaining what changed.

What to do when a conflict occurs

If you see a conflict error at confirmation:

1. Click Back to driver list — the wizard refreshes the eligible driver list with up-to-date availability.
2. Select a different driver, or wait a moment and retry the same driver if the conflict was temporary (another operator cancelled).
3. Alternatively, switch to Broadcast mode from the mode modal (G-07) to let the system find the first available driver automatically.

The provisional lock expires automatically after 3 minutes of inactivity in the wizard to prevent "ghost locks" from operators who navigated away.

---

Confirming the assignment

After passing the re-verification:

1. The mission status changes to Confirmed (or Assigned, depending on your workflow).
2. The driver receives a push notification with full mission details.
3. The assignment is reflected in the Gantt, List, and Map views.
4. The mission dispatch history records the assigning operator, timestamp, and any RSE warnings acknowledged.

---

RSE warnings at confirmation

If a borderline (amber) RSE condition exists, the confirmation panel displays the specific warning (e.g., "Driver has 9 h 45 min rest since last mission — minimum recommended is 11 h"). You must explicitly check the acknowledgement checkbox before the Confirm button becomes active.

In strict mode, red RSE indicators block the confirmation entirely — the button remains disabled and you must choose a different driver or change the crew mode.

See RSE Compliance for details on all compliance rules and indicators.

---

Related pages

• Broadcast Pipeline — let the first available driver self-assign (FR395)
• Crew Modes — assign two drivers for double crew or relay missions
• RSE Compliance — compliance indicators and staffing alternative suggestions
• Gantt View — timeline view reflecting the confirmed assignment