Pilot: Driver Dashboard
Provides consolidated driver situational awareness for active work context, trip status, and immediate operational actions.
Capability
How it works
- 1 Active assignment summary with current and next work context.
- 2 HOS clock visibility and warning cues.
- 3 Quick actions for duty-state change, DVIR start, and document access.
- 4 Truck health context embedded from maintenance telemetry.
Operational outcomes
- Active assignment summary with current and next work context.
- HOS clock visibility and warning cues.
- Quick actions for duty-state change, DVIR start, and document access.
Integration boundaries
- TMS
- CMMS
- Crew
Proof model
Feature-level proof
Driver Dashboard scope is defined in product module catalog.
verified
docs/products/pilot/product.md · Module Catalog > Driver Dashboard
Pilot trip workflows and stop progression are implemented in mobile load and stop views.
verified
docs/products/pilot/product.md · Module Catalog > Trip and Stop Management
Code: frontend/apps/mobile/src/pages/Loads.tsx
Contract: proto/tms/loads/v1
Pilot trip and stop workflows are implemented in mobile and load components.
verified
docs/products/pilot/product.md · Module Catalog > Trip and Stop Management
Code: frontend/apps/mobile/src/components/load
Contract: proto/tms/loads/v1
Solution routes that reuse this feature
Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (1).
Field execution continuity
Outcome: Trip and compliance actions remain durable through offline capture and replay.
Field execution remains durable through connectivity gaps when mobile workflows replay deterministically.
Continuity routes for this capability
Route-level continuity checks where this feature appears in product-pair workflows.
Driver-First Execution
Formula: Pilot + TMS
Open continuity routeOperational validation path
Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.