Job priority routing explained for dispatch managers

Discover how job priority routing explained can enhance scheduling efficiency. Learn to optimize your transport management for higher-value deliveries.

Job priority routing explained for dispatch managers

Job priority routing is the process of telling your transport management system (TMS) which delivery jobs must be included in a schedule and how much the solver should sacrifice in distance or cost to keep them there. The key distinction: priority controls whether a job is scheduled, not precisely when it runs. Your first action is to define your premium service level agreement (SLA), for example a 2-hour delivery window, and map it to a hard time window in the TMS. That single step anchors your highest-value jobs before the solver touches anything else.

Quick-reference facts:

Priority works as a penalty weight: unserved high-priority jobs cost the solver more, so it works harder to include them
Hard time windows are constraints; priority flags are preferences. Use hard windows for guaranteed deliveries
The parameter priorityWeight scales how aggressively the solver protects a job when capacity is tight
partialPlanning flags let the solver return a partial schedule rather than fail on overconstrained days
Logivo supports priority flags, hard time windows, and partial planning for UK trucking and freight operations
First KPI to track: priority inclusion rate (what percentage of high-priority jobs actually appear in the final schedule)

How optimisation engines treat priority: penalties, weights, and constraints

Priority is a mathematical weight, not a queue position. When the solver evaluates candidate routes, it calculates a penalty for every job it leaves unserved. According to the Solvice VRP documentation, that penalty follows the structure:

penalty = priority × duration × priorityWeight

A job with priority 100, a 30-minute duration, and a priorityWeight of 2.0 carries a penalty of 6,000 units if dropped. A low-priority job with priority 10 and the same duration carries only 300 units. The solver will extend a route, accept a longer drive, or drop a low-priority stop before it accepts that 6,000-unit penalty.

priorityWeight is a global multiplier. Raise it and every priority job becomes harder to drop; lower it and the solver trades more freely between priority and distance. The partialPlanning flag changes the solver’s failure mode: instead of returning no schedule when the day is overconstrained, it returns the best partial schedule it can build, which is far more useful for a busy dispatch desk.

Hard constraints work differently. A hard time window is a rule the solver cannot break. Soft priority flags are preferences it can override if the cost is low enough. That distinction matters enormously in practice.

Input	Type	Solver behaviour
Hard time window	Hard constraint	Job must start within the window or is unassigned
Priority flag (e.g. 100)	Soft weight	Solver tries hard to include it; may still drop under extreme pressure
priorityWeight multiplier	Global scalar	Amplifies all priority penalties across the schedule
partialPlanning enabled	Failure mode	Returns best partial schedule on overconstrained days

The solver flow in plain terms: it ingests all jobs, computes penalties for each unserved candidate, evaluates thousands of route combinations, and selects the schedule that minimises total cost (distance + unserved penalties). Carrier assignment logic in enterprise TMS platforms follows the same principle: higher-priority shipments receive earlier start dates when capacity is constrained.

Rules of thumb for SLAs, driver incentives, and telematics

Define what “priority” means inside your SLA before you configure anything. A vague “priority customer” tag is useless; a “guaranteed delivery between 09:00 and 11:00, with a 30-minute notification and named escalation contact” is configurable.

SLA design checklist:

Set a measurement window (e.g. arrival within ±15 minutes of the committed slot)
Define notification thresholds (alert dispatcher if ETA drifts more than 20 minutes)
Name escalation contacts for each priority account
Include penalty clauses for missed windows in customer contracts

Driver incentives need careful handling. Rewarding drops per hour pushes drivers to rush, which creates safety risk and damages priority SLAs when something goes wrong. Reward route adherence, on-time arrival at priority stops, and safe driving scores sourced from telematics instead. Integrating telematics and driver performance history with AI allocation moves your team from firefighting to exception management, which is where dispatch attention belongs.

Telematics integration also enables early intervention. When live position data feeds your priority monitoring, the system can flag a driver running 25 minutes late on a VIP stop before the customer calls. That early warning is the difference between a proactive call and a complaint. Logivo’s live driver map surfaces exactly this kind of real-time priority alert.

For UK last-mile operations, barcode scanning and handover confirmation at the warehouse reduce routing failures caused by load errors. Add a small time buffer on priority routes to absorb real-world delays without cascading into SLA breaches.

How to configure, test, and validate priority routing in your TMS

Start small. A pilot with 5–10 vehicles and two or three priority accounts gives you clean data without exposing your whole operation to configuration risk.

Configuration checklist:

Define your priority tiers (VIP = 100, high-value = 50, standard = 10, economy = 1)
Map each SLA to a hard time window or a priority value, not both unless the job genuinely needs both
Set priorityWeight at 2.0 as a baseline throughout the article; adjust after reviewing inclusion rates
Enable partialPlanning so overconstrained days return a usable schedule
Add job tags (VIP, fragile, hazardous) via automated job intake to feed priority flags automatically
Sync warehouse loading sequence with the solver’s output sequence
Configure alerts for priority jobs at risk (ETA drift threshold)

Test scenarios to run before go-live:

Overconstrained day: load the solver with more jobs than capacity allows; confirm high-priority jobs appear in the schedule and economy jobs are dropped first
Late departure: simulate a 45-minute delay; check that priority stops are protected and the solver re-optimises the remainder
Long-duration vs many short jobs: pit one 4-hour high-value delivery against eight 30-minute standard drops; verify priorityWeight and duration penalty keep the long job in the schedule

KPIs to track during the trial:

Priority inclusion rate: percentage of priority-flagged jobs that appear in the final schedule (target: 95%+)
Priority on-time percentage: percentage of priority jobs delivered within the committed window
Route efficiency delta: average distance per job before and after priority configuration
Customer complaints for priority accounts: should trend down within 30 days

Practical UK scheduling guidance recommends clustering stops by postcode, sequencing within clusters, and using a route optimiser for rounds above 20 stops. Priority routing sits on top of that foundation; it does not replace it.

How to pilot and roll out priority routing across your fleet

Pilot with a small fleet and selected accounts for 30 days, then expand based on KPIs.

Week 0: configure priority tiers, set priorityWeight, enable partialPlanning, train dispatchers on the new SLA mapping, and brief drivers on priority stop indicators in the mobile app
Weeks 1–2: run the closed pilot; collect inclusion rate, on-time percentage, and route efficiency data daily
Weeks 3–4: audit results; adjust priorityWeight up if inclusion rate is below target, tighten time windows if on-time percentage is low, and update loading SOPs where sequence errors occurred
Week 5: wider roll-out if KPIs pass; update customer contracts to reflect new SLA commitments

Training checklist for dispatchers and drivers:

Dispatchers: SLA-to-window mapping, reading inclusion rate reports, escalation contacts, override protocol
Drivers: identifying priority stops in the app, confirming arrival at priority windows, escalation if delayed

Notify premium customers before the pilot begins. Tell them what you are measuring, how you will communicate a missed window, and who to contact. Customers who know you are actively managing their SLA are more forgiving of early teething issues and more likely to renew contracts when performance improves.

How Logivo supports priority routing and how to trial it

Logivo is built for exactly this workflow. The platform supports job priority fields, hard time windows, priorityWeight-equivalent settings, and partial planning for overconstrained days. AI-powered fleet optimisation for UK logistics requires automated allocation, priority scheduling, and resilience to disruption; Logivo delivers all three within a single platform.

Logivo capabilities relevant to priority routing:

Job priority field and hard time window configuration per job
Partial planning mode for overconstrained schedules
Real-time driver tracking with priority alert thresholds
Warehouse and load sequence sync
Role-based access so dispatchers, drivers, and managers each see what they need
Driver mobile app in 20+ languages, showing priority stops clearly
ePOD capture and customer portal for priority account visibility

The guided 30-day trial maps directly to the pilot timeline above. You configure your priority tiers in week 0, run the pilot in weeks 1–4, and validate against inclusion rate and on-time percentage before committing to wider roll-out. No upfront cost, no long-term contract required to start.

Start your trial at the Logivo transport management platform.

Key takeaways

Job priority routing works because it translates service commitments into solver penalties and hard constraints, giving the TMS a clear instruction on which jobs to protect when capacity is tight.

Point	Details
Priority controls inclusion, not timing	The solver uses penalty weights to decide whether a job is scheduled, not exactly when it runs.
Hard windows beat priority flags for guarantees	Any job with a contractual delivery commitment needs a hard time window, not just a priority flag.
Anchor window technique	Assign hard windows to VIP accounts first; the solver sequences remaining stops around them.
Loading sequence must match route sequence	A correctly prioritised route fails if the vehicle is loaded in the wrong order.
First KPI to track	Monitor priority inclusion rate (target 95%+) before optimising on-time percentage.
Logivo trial path	Logivo’s guided 30-day trial supports priority flags, hard windows, and partial planning for UK operators.

The case for treating priority routing as a margin decision

Most dispatch managers think of priority routing as a customer service tool. It is, but that framing undersells it. Every time a high-margin job gets dropped from a schedule because a low-value stop was configured with an inflated priority flag, you are directly eroding contribution margin. The solver does not know which jobs pay well; it only knows the weights you give it.

The operators who get the most from priority routing treat it as a commercial decision, not a configuration task. They sit down with their sales and finance teams, identify the ten accounts that generate the most margin, and build the priority tiers around those accounts first. Everything else fills in around them.

One practical tip: audit your priority deliveries every 30 days and protect your loading sequence as rigorously as you protect your time windows. A missed loading SOP undoes every configuration gain you have made. The 30-day audit cadence is also when you catch priority creep, the slow drift where more and more jobs get elevated flags until the tier system means nothing.

Useful sources and further reading

The following sources underpin the technical and operational guidance in this article:

For deeper reading on AI dispatch and TMS architecture, the Logivo blog covers automated allocation, pilot planning, and driver app configuration in detail.

Logivo gives you priority routing without the configuration headache

Configuring priority routing from scratch in a generic TMS can take weeks of trial and error. Logivo removes that friction. The platform is built for UK trucking, freight, and drayage operators, with priority fields, hard time windows, partial planning, and real-time driver tracking available from day one of your trial.

The guided 30-day trial gives you prebuilt test scenarios, KPI dashboards tracking inclusion rate and on-time percentage, and a support team that knows UK haulage operations. You validate the configuration against your own jobs and your own accounts before committing to anything. Usage-based pricing means you pay for what you actually process, with no minimum seat count and no long-term lock-in.

If your current TMS treats all jobs the same or gives you no visibility into why a priority job was dropped, that is the problem Logivo is designed to fix. Start your guided trial and see inclusion rate and on-time percentage move within the first two weeks.

FAQ

What does job priority routing mean in a TMS?

Job priority routing is the process of assigning penalty weights and hard time windows to delivery jobs so the solver protects high-value or time-sensitive stops when capacity is constrained. Priority controls whether a job is scheduled, not its exact time slot.

What is the difference between a priority flag and a hard time window?

A priority flag is a soft preference: the solver tries hard to include the job but can override it under extreme capacity pressure. A hard time window is a constraint the solver cannot break; the job is either scheduled within the window or left unassigned.

How do I set priorityWeight in my TMS?

Set priorityWeight at 2.0 as your baseline; review inclusion rate after the first week of the pilot and adjust as needed (increase if jobs are dropped, decrease if efficiency suffers without SLA gains).

Which KPI should I track first when testing priority routing?

Track priority inclusion rate first: the percentage of priority-flagged jobs that appear in the final schedule. A target of 95%+ is a reasonable baseline before you move on to optimising on-time percentage and route efficiency.

Can Logivo support priority routing for UK freight operations?

Yes. Logivo supports job priority fields, hard time windows, partial planning for overconstrained days, and real-time driver tracking with priority alerts. A guided 30-day trial is available with no upfront cost.