Operator Workflows¶

MYConnect is designed around the working day of a transport company. The most important workflow is not a dashboard; it is the operational loop from order intake to delivery proof and customer visibility.

Order To POD¶

sequenceDiagram
    participant Ops as Operations
    participant Dispatch as Dispatcher
    participant Driver as Driver
    participant Fleet as Fleet/IoT
    participant Customer as Customer Portal
    participant Finance as Finance

    Ops->>Dispatch: Create or import transport job
    Dispatch->>Driver: Assign driver, vehicle, trailer, and stops
    Driver->>Fleet: Job moves with telemetry context
    Driver->>Ops: Submit status updates and POD evidence
    Fleet->>Ops: Enrich timeline with location and geofence events
    Ops->>Customer: Approve customer-visible shipment timeline and POD
    Customer->>Customer: Download accepted POD or enabled report
    Ops->>Finance: Generate billing-ready export

Daily Dispatch Flow¶

1. Create or import jobs with customer, pickup, dropoff, cargo, price, and instructions.
2. Assign driver, vehicle, trailer, and planned pickup/delivery times.
3. Watch active jobs, exceptions, missing POD, and billing-ready work.
4. Use vehicle telemetry and driver updates to build a credible timeline.
5. Review POD and make approved evidence available to the customer.
6. Export completed jobs for billing preparation.

Customer Visibility Flow¶

Customer visibility is controlled. A customer user should only see shipments, timeline events, POD descriptors, and reports that are approved for their account.

flowchart TD
    Login["Customer portal login"] --> Membership["Customer account membership check"]
    Membership --> Rule["Visibility rule check"]
    Rule --> Shipment["Shipment list and detail"]
    Shipment --> Timeline["Customer-safe timeline"]
    Timeline --> Evidence["Accepted POD or enabled report"]
    Evidence --> Audit["Download and access audit"]

Driver Workflow¶

The driver flow stays narrow because the driver should not need to operate a full office system.

• Log in with a driver mobile identity.
• See assigned jobs.
• Open job detail.
• Send job status updates.
• Submit POD evidence.
• Replay or diagnose rejected offline-style sync records.

Support And Admin Flow¶

MYConnect staff need platform-level tools, while haulier users need tenant-level tools. The current design keeps those surfaces separate.