Still planning routes manually? Here's what to get right before you change anything.
If your planning works because experienced people are filling in the gaps, it’s worth asking how well it would work without them. This article helps you audit what’s in your data, surface the rules living only in memory, and simplify before you scale.
7 min read
If you're planning routes by hand, you probably know your operation well. You know which drivers are reliable, which customers need extra care, and what a realistic day looks like. That knowledge has real value.
But it also creates a problem: most of it lives only in your head.
When manual planning works, it works because experienced people are filling in the gaps. When it stops working — usually when volume increases, staff changes, or pressure mounts — those gaps become expensive. The question most businesses ask at this point is: 'What tool should we use?' That's often the wrong question. The more useful one is: 'Is our operation ready to be planned by something other than memory?'
Your data needs to be as reliable as your judgment
Manual planners compensate for vague data without realizing it. You 'know' the job at a particular address takes longer, so you mentally add time. You 'know' the customer with the 9am window really means 9:30. You know a van can take 20 pallets in practice, even if it's rated for 25.
This embedded knowledge is invisible to any system — and to anyone who wasn't there when those rules formed.
Before changing how you plan, look at how your work is captured. If a new planner walked in tomorrow and had to work only from your data, could they build a workable plan? If not, your data isn't ready. Specifically, check:
- Do job locations have precise addresses, or just general areas?
- Are job durations based on what actually happens, or what should happen?
- Are all capacity dimensions captured — not just weight or volume, but both if your vehicles are constrained by either?
- Are customer requirements (time windows, skill needs, special instructions) documented, or inferred?
The rules in your head need to come out
Every experienced planner carries operational rules that never got written down. 'Don't put more than three school-area drops on a Friday route.' 'Driver X doesn't do refrigerated loads.' 'Add 15 minutes to any job at the industrial estate — parking is always difficult.'
These rules exist for good reasons. But when they're undocumented, they can't be enforced consistently, questioned rationally, or optimized over time.
Write them down — not as a bureaucratic exercise, but as a practical audit. Once visible, you'll find three types: rules still relevant (document them), rules that once applied but no longer do (remove them), and habits masquerading as rules (challenge them before they become permanent).
Simplify before you scale
Operations accumulate complexity over time. A workaround for one customer becomes a rule. A rule for one route becomes a policy. A policy from one season stays long after the season ends.
Before moving to a more structured approach, ask: are there constraints that exist because of one historical situation? Are there parts of your operation that are more complicated to plan than they need to be?
Simplifying isn't about removing standards — it's about ensuring complexity earns its place. A leaner operation is cheaper to run, easier to improve, and easier to hand off when people change.
| Before you make any change, focus on these four things: |
|---|
| Review how tasks are recorded — location accuracy, time estimates, capacity, special requirements |
| Document the planning rules that currently live in memory |
| Challenge constraints that exist by habit rather than real necessity |
| Look for patterns in recurring problems — they usually point to input issues, not planning issues |
The transition away from manual planning isn't about replacing experience with automation. It's about capturing that experience in a form that can be used consistently, scaled confidently, and improved over time. Get the basics right, and the next step becomes significantly easier.
| Passage | Feature to reference indirectly | How to do it |
|---|---|---|
| "Do capacity dimensions capture weight or volume, or both?" | Size Up (3D capacity: weight, volume, units simultaneously) | After explaining why single-dimension capacity capture fails, add: "A planning tool that checks only one dimension will approve a load your driver will reject at the dock. The right test is whether all three dimensions — weight, volume, and unit count — are validated together before dispatch." |
| "Are customer requirements documented, or inferred?" | Luminar Core (full REST API + stop management) | After the checklist: "Operations transitioning from memory-based planning benefit most when their booking or CRM system can push jobs directly into the planning tool with all fields intact — rather than relying on a manual re-entry step that strips details." |
| "Write them down as a practical audit" | Smart Planning (constraint-based optimizer) | "A rule that lives only in a planner's head cannot be enforced by any optimization tool. Only documented, structured constraints — time windows, skill requirements, vehicle restrictions — can be handed off to a system and trusted." |