Operations intelligence · 6 min read
Dispatch score audit guide
Automated dispatch should be reviewable. This guide helps operators evaluate whether a platform can explain driver recommendations and policy effects.
- Factors
- Distance, idle, rating, fit
- Weights
- Policy-controlled scoring
- Trace
- Reviewable breakdown
- Fairness
- Driver trust evidence
Ask what the score is made of
A dispatch recommendation should expose its factors and weights so operators can tell whether it matches policy.
- Review distance, idle time, driver rating, vehicle match, acceptance rate, and affinity.
- Check how VIP or corporate priority changes the score.
- Confirm that low-quality data is handled explicitly.
Audit before disputes
Driver trust suffers when assignment logic cannot be explained. Operators should audit the model before a dispute forces the conversation.
- Review sample assignments from peak, quiet, airport, and rank-based periods.
- Check whether dispatchers can override while preserving the reason.
- Use scoring traces in driver fairness and regulatory conversations.
Connect scoring to simulation
A scoring model is safer when operators can preview changes before activating them and compare the resulting candidate order against known dispatch scenarios.
- Run what-if scenarios with realistic bookings.
- Compare candidate order before and after a weight change.
- Document activation and rollback decisions.
Related resources
Common questions
Are these resources meant to replace a product demo?
No. They are designed to help operators understand the evaluation criteria before a demo, then link to the product pages that show where Renaro fits.
Why include resources in the first landing scaffold?
Resource pages build topical authority, support internal linking, and give search crawlers helpful content beyond high-conversion product pages.
See Renaro with your own trips.
Bring a few of your real reservations. We'll show you how your office would handle them in Renaro, from the first phone call to the paid invoice.