Managing stops on a route from Maven Dispatch

overview

Use stop‑level controls in Maven Dispatch to keep routes realistic and aligned with field conditions.

table of contents

• review stops before making changes

• Resequence Stops 

• Skip or cancel stops that cannot be service 

• Force complete or roll back stops when drivers are blocked

• Add and update stop-level notes

• Monitor the impact of stop changes

Review stops before making changes

Open a route and:

• Scan the full stop list, including sequence and status.

• Check time windows and distance between stops.

• Review tags and notes for any special handling.

• Confirm the driver’s current position and progress.

Only adjust stops after reviewing the full context.

Resequence stops

When a route needs a new order:

• Drag and drop stops or use available move‑up/move‑down controls.

• Keep time windows and service commitments in view while resequencing.

• Avoid jumping long distances that create unreasonable travel times.

• Save and confirm the updated sequence.

Notify the driver of major changes if standard messaging procedures require it.

Skip or cancel stops that cannot be serviced

When a stop must be skipped or cancelled:

• Select the stop and apply the skip or cancel action.

• Add a clear note with the reason (closed, refused, unsafe, incorrect address, no freight).

• Confirm any follow‑up action, such as rescheduling or returning freight.

• Verify the mobile app reflects the updated status.

Do not leave unresolved stops in an in‑progress state once the outcome is clear.

Force complete or roll back stops when drivers are blocked

Use force controls when the normal workflow fails:

• Force complete a stop when work is finished but the driver cannot complete it in the app.

• Roll back a stop when the wrong status was applied in the field.

• Document each manual override with a brief explanation.

• Confirm that shipment status, POD, and KPIs reflect the desired outcome.

Use overrides sparingly to maintain clean audit trails.

Add and update stop‑level notes

Use notes to guide drivers and document decisions:

• Add instructions for access, contacts, or special requirements.

• Record reasons for resequencing, skipping, cancelling, or forcing completion.

• Use consistent, concise language so everyone can understand the history.

• Check that critical notes appear on the driver’s app where supported.

Review existing notes before applying new ones to avoid contradictions.

Monitor the impact of stop changes

After making stop‑level changes:

• Check updated ETAs and on‑time performance indicators.

• Confirm route duration and workload remain reasonable.

• Ensure no critical shipment dropped out of the route unintentionally.