Delivery Exceptions & Replanning

Keep the Operation Moving When Plans Change

Detect issues, understand their impact and reassign work without losing sight of drivers, routes or customers.

  • Detect delivery exceptions
  • Compare replanning options
  • Reassign and reschedule work
  • Update drivers and customers
  • Keep routes moving
Route360 exception control centre: five headline counters over the exception table with priority, type, route, stop, driver, issue, detection time, impact and status. 16:10, dark UI, 2560x1600.

THE REPLANNING WORKSPACE

Move the Work. Keep the Plan.

Move selected work, compare the impact and check the new plan before applying changes, whether you're managing city deliveries across Dubai, Abu Dhabi and Sharjah or coordinating routes between emirates and operating locations.

Exception table: six exceptions with priority, type, route, stop, driver, issue, detected time, impact and status. 16:9, dark UI.

What Happens When Changes Are Applied

Driver update sent, awaiting acceptance. 4:3, dark UI.

Driver notified. The change is sent to the driver in the app for acceptance.

Driver and customer communication feed: seven events with their times and delivery states. 16:9, dark UI.

Updates sent. Driver updates, customer ETA changes and message delivery are recorded in sequence, with each event timestamped.

Driver declined flow with the alternative options. 4:3, dark UI.

Change declined. The dispatcher is alerted, alternative options are shown and another change can be applied.

Move entire shift options, three cards. 4:3, dark UI.

Shift reassigned. Reassign the remaining stops, the full shift or move the work to another day.

Exception detail panel with its attachment. 4:3, dark UI.

Exception details. See the exception type, route, driver, vehicle, stop, original window, cause, impact, owner and notes.

Exception reporting: the type breakdown donut beside resolution time, replanning frequency, repeat locations and failure reasons. 16:9, dark UI.

Exception reporting. Track exception types, average resolution time, replanning frequency, repeat locations and failed delivery reasons.

Exception history timeline. 4:3, dark UI.

Full history. Keep the complete exception timeline from detection through to resolution.

Additional features

  • Auto Refresh

    The board updates automatically without needing a reload.

  • Prioritisation

    Set high, medium or low priority based on operational impact.

  • Route Rescheduling

    Move a stop within the same driver's day.

  • Recovery Routes

    Build a new route for affected stops.

  • Return to Depot

    Send an item back and create the return job.

  • Resolution Owner

    Assign someone to take ownership of each exception.

  • Attachments

    Keep driver photos attached to the exception.

  • Repeat Locations

    Identify locations where the same problems keep occurring.

  • Replanning Scope

    Move a stop, route segment, full route or shift.

  • Impact Comparison

    Compare ETA, distance, drive time and affected customers.

  • Change validation

    Check proposed changes against configured driver, vehicle, route and operational requirements before publishing.

  • Republish Routes

    Publish updated routes and ETAs in one action.

Frequently Asked Questions

  • What can be moved when a plan breaks?

    Move a single stop, a section of a route, a full route or an entire shift. Choose the scope first, and the available replanning options adjust to match.

  • How do I know which option is best?

    Compare each option by ETA change, additional distance, drive time, affected jobs, time window impact and customers affected. The lowest impact option is highlighted with the reason it was recommended.

  • What stops a replan creating a new problem?

    Route360 checks proposed changes against configured requirements such as driver availability, recorded licence and skill information, vehicle capacity and readiness, delivery windows, route conflicts and planned work and rest periods. Potential issues are highlighted for the dispatcher to review before publishing.

  • What if the driver declines the change?

    The dispatcher is alerted and alternative drivers and routes are suggested. If the driver does not respond, alternative options are surfaced rather than leaving the change unacknowledged.

  • Are customers told automatically?

    Customer updates can be sent automatically through configured notification channels when a route or ETA changes. Where enabled, the customer tracking page reflects the revised delivery information, with communication history and available message statuses recorded against the job.

Handle Delivery Issues From One Place

Detect, compare, reassign and communicate in one workflow.

  • Secure, role based access
  • Complete audit trail of every change
  • Communication via app, SMS and email
  • Available across web and mobile