Driver Mobile App - Starting a Workflow (Route/Trip)

table of contents

Overview

Step 1: Open the assigned route or trip

Step 2: Review route details before starting

Step 3: Start the workflow

Step 4: Navigate to First Stop

Step 5: Complete workflow tasks at each stop

Step 6: Monitor progress and HOS during the workflow

Step 7: End the workflow

Overview

This article explains how drivers start their daily workflow (route or trip) in the Maven Driver App after signing in and connecting to a vehicle. The exact screens may vary by configuration (P&D, Linehaul, or other workflows), but the overall process is the same.

Step 1: Open the Assigned Route or Trip

After sign-in and vehicle connection:

1. From the main screen, navigate to the Routes, Trips, or Workflow section (term may vary by configuration).

2. Locate today’s assigned route or trip:

   • The route may be labeled with a route ID, trip number, lane name, or date.

   • If multiple routes appear, select the one that matches the dispatch instructions.

If no route is visible, contact dispatch or a fleet administrator to confirm the assignment.

Step 2: Review Route Details Before Starting

On the route/ trip details screen, review:

• Start and end locations (terminal, depot, or customer).

• The list of stops in planned order.

• Any special instructions or notes from dispatch (for example, gate codes, appointment times, or handling instructions).

• For workflows that display equipment fields:

  • Confirm the Truck and Trailer numbers are correct.

  • If the driver is not pulling a trailer and a checkbox is provided (for example, “I am not pulling a trailer”), mark it if applicable.

Confirming these details before starting reduces errors later in the route.

Step 3: Start the Workflow

To begin work on the route:

1. Tap Begin Route, Start Trip, or the configured Start button.

2. If prompted:

   • Confirm current equipment (vehicle and trailer).

   • Confirm starting duty status (for example, On Duty or Driving, as required by company policy).

3. The app will typically:

   • Open to the first stop in the route, or

   • Display the stop list with the first stop highlighted.

Once started, progress and status updates are shared with the Fleet Portal in real time (or when connectivity is available).

Step 4: Navigate to the First Stop

After starting the route:

1. From the stop list, tap the first stop.

2. Review stop-level details:

   • Customer name and address

   • Planned arrival time or appointment window

   • Any special instructions or notes

3. Tap the navigation button (for example, “Navigate” or a map icon) to open turn‑by‑turn directions using the configured navigation solution.

Arriving at the stop will either be detected automatically or require the driver to tap Arrive, depending on configuration.

Step 5: Complete Workflow Tasks at Each Stop

At each stop in the workflow:

1. Mark arrival (auto-detected or manual).

2. Complete the required actions for the workflow, which may include:

   • Scanning barcodes or PRO numbers

   • Capturing signatures or photos

   • Entering pieces, weight, or pallets

   • Applying exception codes if there are issues (for example, customer closed, refused freight, partial delivery).

3. Tap Complete, Depart, or the configured button to move to the next stop.

The app automatically updates the route status and sends stop completion data back to the Fleet Portal.

Step 6: Monitor Progress and HOS During the Workflow

While the workflow is in progress:

• Use the main screen to monitor:

  • Current duty status

  • HOS timers (including the 8‑hour break timer)

• Use the stop list or route view to:

  • See remaining stops

  • Track estimated arrival times and any timing changes

Drivers should follow company policy for breaks and duty status changes to maintain HOS compliance.

Step 7: End the Workflow

After completing the final stop:

1. Return to the route or workflow overview screen.

2. Tap End Route, Complete Trip, or the configured Finish button.

3. If prompted, review:

   • Any incomplete stops or exceptions

   • Final equipment status (for example, returning trailers on the Equipment page)

4. Confirm the end of the workflow.

Once ended, the route is marked as complete in both the driver app and the Fleet Portal.