Cancellation & Reroute Reasons
Log every cancellation and reroute with a reason so there is never a doubt about why, by whom, and when
With Cancellation & Reroute Reasons,
The Dispatcher can
track cancellation and reroute reasons
so they can
identify problematic patterns
— resulting in reduced deadhead fuel costs.
The Problem
The Core Problem
Cancellations and reroutes happen with no structured documentation, leaving providers exposed to broker audits and unable to identify waste patterns.
The Scenario
A provider handles 300 daily trips and averages 25 to 35 cancellations or reroutes per day. When a trip is canceled, the dispatcher deletes it or marks it complete with no record of why. When a broker asks why a trip was not completed, there is no documentation.
Why It's Urgent
Brokers audit cancellation patterns quarterly. Providers without documented reasons face penalties or contract termination. Internally, repeated no-shows by specific passengers waste driver time but nobody tracks the frequency.
Without MediRoutes
Ask dispatchers to write notes in a comment field. Notes are inconsistent, hard to aggregate, and often skipped during busy periods.
With MediRoutes
Structured cancellation and reroute reason codes required at the time of action. Every cancellation logs who initiated it, the reason category, a timestamp, and whether the trip was rerouted or fully canceled. Dashboards show patterns by passenger, driver, route, and reason.
Who This Helps
The Fleet Owner
Needs audit-ready documentation for every canceled trip and visibility into patterns that waste fleet capacity.
The Dispatcher
Handles 25 to 35 cancellations per day and needs to log the reason quickly without disrupting workflow.
How It Works
Each step shows what happens when things go right — and what MediRoutes does when they don't.
Start / End
Process Step
Decision Point
Common Questions
Yes. Providers can add custom reason categories beyond the defaults. Common additions include weather delays, facility construction, and insurance authorization issues.
Every cancellation has a timestamped record with the reason, who initiated it, and whether a reroute was attempted. Providers can generate broker-specific cancellation reports filtered by date range and reason category.
Yes. The system identifies passengers with elevated no-show patterns and can flag them for dispatcher attention or trigger automated confirmation calls before future trips.
Driver-initiated cancellations are logged from the mobile app with GPS coordinates and timestamp proving the driver was at the pickup location. This provides evidence for no-show documentation.