How to evaluate route planning software for your business.
Route planning software is easy to buy and hard to undo. This article walks through the evaluation questions that actually matter — starting with your own real data, not a vendor demo — so you can judge any vendor answers for yourself, Luminar Works included.
8 min read
Route planning software is easy to buy and hard to undo. A poor fit doesn't just fail to solve your problems — it often creates new ones: duplicate data entry, workarounds that grow into workflows, and a team that goes around the system instead of using it.
The most important evaluation questions aren't technical. They're operational. You don't need to understand how the software works — you need to understand whether it fits how you work.
Start with your real data, not a demo scenario
Every demo looks good. The scenarios are clean, the data is tidy, and the planner makes it look effortless. Your operation is none of those things.
The only meaningful test is running the software against your actual data: your jobs, your vehicles, your constraints, your edge cases. Ask the vendor to run a sample day using a dataset from your operation. Then ask:
- Did it produce routes your drivers could actually follow?
- How many jobs were dropped or unassigned — and can the system tell you why?
- How much manual adjustment was needed to produce a workable plan?
A system that handles your messy, real-world data reasonably well is worth more than one that handles demo data flawlessly.
Test how it handles constraints and exceptions
Real operations come with layered rules: drivers with specific certifications, time windows that differ by customer, vehicles that can only handle certain job types, dependencies between tasks. The question isn't whether the software supports these rules — it's how it behaves when they conflict.
Ask specifically: what happens when constraints can't all be satisfied? Does the system warn you with an explanation, or silently produce a plan that's already broken? Can it show you which jobs were dropped and why? Does it flag constraint violations before the plan is finalised?
A system that explains its decisions is worth significantly more than one that just produces outputs.
Evaluate usability for both planners and drivers
The people who will use this every day aren't in the demo. Your planners need to adjust routes quickly under pressure. Your drivers need to follow plans without confusion.
Test the system with actual users — not just decision-makers. Useful things to check:
- How long does it take a planner to adjust a route after it's built?
- Can changes be made mid-day without rebuilding from scratch?
- What does the driver-facing output look like — and can your drivers actually follow it?
If planners find it unintuitive, they'll work around it. If drivers can't follow it, the plan won't be executed as built. Either outcome erodes the value you're paying for.
Understand how it fits your wider process
Route planning doesn't happen in isolation. Jobs come from somewhere. Routes need to go somewhere. Before committing to any system, trace the full flow:
- How do jobs get in — manual entry, import, or direct integration with your booking platform?
- How do routes get out — what formats are supported, and do they match what billing or reporting expects?
- When reality diverges from the plan, can updates flow back without manual rework?
Every step that requires manual data entry is a step where errors accumulate. A system that creates new admin work isn't solving the right problem.
Don't overlook support and vendor health
The software you buy includes the company behind it. That matters when something goes wrong — which it will.
- Is the product being actively developed? Are updates meaningful, not just cosmetic?
- What does support look like in practice — not in the sales brochure?
- Is there documentation or a knowledge base for self-service troubleshooting?
A good product with poor support is a frustrating long-term relationship. Ask to speak with existing customers, not just references the vendor selected for you.
| Evaluation checklist: |
|---|
| Run a test using your own data — a real day, not a prepared scenario |
| Check how constraint conflicts are handled and communicated |
| Involve planners and drivers in testing, not just management |
| Trace the full data flow: job entry → route creation → execution → billing |
| Clarify support structure, response times, and product roadmap before committing |
The best route planning software isn't the one with the most features — it's the one that fits your operation closely enough that your team will actually use it, consistently, without building workarounds around it.
| Passage | Feature to feference indirectly | How to do it |
|---|---|---|
| "Run a test using your own data — a real day, not a demo scenario" | Smart Planning (CSV/API import, up to 80 stops per route) | "A meaningful test requires importing a real day's job file — not a vendor-supplied sample. Software that cannot accept a standard CSV of your own stops on day one is software that will cost you time in every integration step that follows." |
| "What happens when constraints can't all be satisfied — does the system warn you?" | Smart Planning (route quality scoring 0–100) | "The most useful signal a planning tool can provide is not just the plan itself, but a quality indicator that tells you how close to optimal that plan is — and, crucially, whether the limiting factor is a constraint conflict rather than a data problem." |
| "How long does it take a planner to adjust a route after it's built?" | Smart Planning (instant re-optimization) | "A planner under pressure does not have time to rebuild from scratch. The adjustment workflow — how quickly a single cancellation or driver absence can be absorbed and re-dispatched — is a more useful test of daily usability than the quality of the initial plan." |
| "How do routes get out — what formats are supported?" | Luminar Core (full REST API on every plan, including free tier) | "The API surface matters as much as the planning engine. An operation running billing, ERP, or CRM systems downstream needs routes to move automatically — not be re-keyed. A planning tool that provides a full API on its base tier gives you that flexibility without forcing an upgrade." |