---
title: "How to Choose Dispatch Management Software: Assignment Logic, Live Tracking, and SLA Controls"
id: "26968"
type: "post"
slug: "how-to-choose-dispatch-management-software"
published_at: "2026-09-14T14:00:00+00:00"
modified_at: "2026-09-23T14:27:05+00:00"
url: "https://locus.sh/blogs/how-to-choose-dispatch-management-software/"
markdown_url: "https://locus.sh/blogs/how-to-choose-dispatch-management-software.md"
excerpt: "Evaluate dispatch management software across three pillars: assignment logic, live tracking, and SLA controls. Includes questions to ask every vendor."
taxonomy_category:
  - "General"
---

#### [General](https://locus.sh/blogs/category/general/)

# How to Choose Dispatch Management Software: Assignment Logic, Live Tracking, and SLA Controls

[Team Locus](/author/team-locus/)

Sep 14, 2026

18 mins read

## Key Takeaways

- Dispatch management software is the operational layer that converts incoming orders into assigned vehicles, planned routes, monitored deliveries, and maintained SLA commitments. Buyers who evaluate it only on routing quality miss the two-thirds of the capability that determines whether delivery performance holds at enterprise scale
- Assignment logic determines which vehicle, driver, or carrier handles each order. The gap between basic nearest-vehicle routing and multi-constraint optimization produces a measurable difference in SLA compliance and cost per delivery, and the gap widens as order volume increases
- Live tracking is not a GPS map. It is visibility into how delivery execution is performing against the plan, with exception signals generated early enough to act on. A platform that shows vehicle positions without plan-adherence context is useful for observation, not intervention
- SLA controls determine whether commitments are treated as hard constraints or reference targets. The distinction determines whether the platform produces a plan that honors commitments or a plan the dispatcher then has to manually review for SLA risk
- All three pillars depend on a shared data layer. Assignment logic that operates on different data from live tracking produces re-allocation decisions that conflict with the active route plan

[Schedule a Demo With Locus Today](https://locus.sh/schedule-demo/)

Most dispatch management software evaluations center on route planning quality: how tight the routes are, how fast the algorithm runs, how many vehicle types it supports. Route planning matters. It is also only one of three capabilities that determine whether dispatch management software performs at enterprise scale.

The other two are live tracking, which shows how execution is unfolding against the plan in real time, and SLA controls, which determine whether delivery commitments are treated as binding constraints or planning targets.

A platform that excels at route planning but provides weak live tracking produces a morning plan with no monitoring layer. A platform with strong routing and tracking but no SLA enforcement produces visibility into execution without a mechanism for maintaining commitments.

This guide organizes the evaluation around these three pillars, identifies what to look for and what to avoid in each, and closes with the vendor questions that surface the gaps standard demos do not show.

## What Dispatch Management Software Needs to Do

Dispatch management software is the operational layer that sits between incoming orders and completed deliveries. Its job is to produce a feasible delivery plan, monitor its execution, and maintain the commitments made to customers and carriers throughout the delivery day.

At a minimum, it assigns orders to vehicles, builds route sequences, tracks delivery progress, and reports outcomes. At enterprise scale, it does these things simultaneously across hundreds or thousands of active deliveries, with enough intelligence to catch problems before they become failures.

| Capability area | What enterprise-grade looks like |
| --- | --- |
| Assignment logic | Multi-constraint order-to-vehicle matching that considers capacity, driver hours, time windows, carrier SLA history, cost, and priority simultaneously across the full order set |
| Route sequencing | Stop sequences that honor time window commitments and optimize for total route efficiency, built in minutes at enterprise volumes |
| Live tracking | Real-time delivery state with plan-adherence context, exception signals generated before SLA windows close, and driver-side activity visible to dispatchers |
| SLA controls | Committed windows treated as planning constraints; real-time monitoring with threshold-based alerts surfaced while there is still time to act |
| Exception response | Automated handling for routine exceptions; escalation to dispatchers for decisions that require human judgment |

## Pillar 1: Assignment Logic: Getting Order-to-Vehicle Matching Right

Assignment logic is the decision mechanism that determines which vehicle, driver, or carrier handles each order.

At its simplest, it is nearest-vehicle-first routing. At its most capable, it is multi-variable optimization that evaluates the full order set simultaneously and produces assignments that minimize cost while honoring all constraints.

The difference between these two is not visible until order volume is high or constraints are dense. At low volume, nearest-vehicle routing produces acceptable results because there is slack in the system to absorb suboptimal assignments. At enterprise volume, the suboptimal assignments accumulate into excess cost and SLA failures that the dispatcher cannot manually correct fast enough.

### What makes assignment logic sophisticated

- **Multi-constraint simultaneous optimization:** The best assignment for one order may make the next five orders worse. Sophisticated logic considers the full order set and the interaction effects of assignments
- **Fleet-type differentiation:** Captive fleet, contracted carriers, and on-demand capacity each have different cost structures, SLA commitments, and operational rules. Assignment logic that treats them identically applies the wrong rules to two of the three fleet types
- **Live re-allocation without plan rebuild:** When a vehicle breaks down or a carrier cancels a pickup, the affected orders need to be reassigned. Logic that requires a full plan rebuild makes mid-day re-allocation impractical at high volume
- **Priority weighting:** Configurable rules that can elevate time-sensitive orders, high-value shipments, or re-deliveries above standard queue position in the assignment process
- **Cost and SLA balance:** The ability to set objectives that weight cost efficiency against SLA compliance, so the assignment engine produces plans appropriate for the trade-offs your operation is willing to make

### Red flags in assignment logic

| Claim | What it actually means | Why it matters |
| --- | --- | --- |
| “Advanced AI routing” | Often a nearest-vehicle algorithm with a branding label. Ask how many constraints it processes simultaneously and whether it optimizes the full order set or assigns sequentially | Sequential assignment produces compounding inefficiency; the claims differ from the implementation more often than vendors admit |
| “Automatic re-routing” | May mean the platform sends a new route to the driver. May mean it rebuilds the full plan. May mean it only handles single-order changes. The mechanics vary widely | A full plan rebuild for a single-order change is not practical at enterprise volume; the answer reveals whether re-allocation is an actual capability or a demo feature |
| “Supports multiple carrier types” | Check whether different SLA and cost rules can be applied per carrier type, or whether all carriers are evaluated on the same logic | Treating contracted carriers and on-demand capacity with the same assignment rules produces incorrect cost calculations and SLA outcomes |
| “Priority-based routing” | Confirm whether priority is a manual dispatcher flag or a configurable rule applied at assignment time | Manual priority flagging does not scale; configurable rules that apply automatically by order type are the enterprise requirement |

[https://locus.sh/dispatch-management-software/](https://locus.sh/dispatch-management-software/)

DispatchIQ evaluates the full order set against 250+ simultaneous constraints, producing assignments that balance SLA compliance, cost, vehicle capacity, and driver hours without requiring a dispatcher to resolve conflicts manually

## Pillar 2: Live Tracking: Visibility That Drives Action

Live tracking is the real-time visibility layer that shows how delivery execution is progressing against the plan.

The word “live” carries specific meaning here: data that is 15 minutes delayed is not live enough for exception response. A vehicle that deviated from its route 12 minutes ago and has not been seen on GPS since is a problem that a dispatcher cannot act on if they learn about it from an hourly batch update.

The second important distinction: live tracking is not the same as a GPS map. A GPS map shows where vehicles are. Live tracking shows where vehicles are relative to where they should be, which deliveries are at risk, and what the dispatcher can do about it.

### What live tracking must cover

- **Vehicle position with meaningful update frequency:** 30-second or faster updates for high-density urban operations; longer intervals may be acceptable for long-haul but inadequate for last-mile. Confirm the actual update frequency, not the maximum capability
- **Plan adherence by stop:** Whether each stop was arrived at early, on time, or late, relative to the planned window. Position alone does not tell you whether stop 12 was completed before the committed window
- **ETA recalculation throughout the delivery day:** The remaining-stop ETAs should update as actual delivery times accumulate, not hold the 6 AM projection for the full day
- **Driver-side activity:** Whether the driver has started the route, is in transit to a stop, is at a stop, has marked a delivery complete, or has flagged an issue. Position does not surface these states
- **Exception signals before SLA breach:** An alert that a vehicle is 20 minutes behind plan and three stops have commitments due in 45 minutes has operational value. An alert that those commitments were missed has historical value only

### The difference between a GPS map and operational visibility

A GPS map answers one question: where are the vehicles? That answer is useful for a dispatcher trying to find a vehicle for a same-day urgent pickup, or for a customer service agent confirming a delivery is in the area.

Operational visibility answers a different question: what is happening relative to what should be happening, and where does the dispatcher need to act? The answer requires the platform to maintain the planned state (the route plan), compare it to the actual state (GPS position, stop completion events, carrier reports), and surface the deviations that represent operational risk.

The test for operational visibility is “when a vehicle falls 20 minutes behind plan, does the platform surface that deviation automatically, with context about which stops are at risk, before those stops are attempted?”

The [Driver Companion App](https://locus.sh/driver-companion-app/)
 component is a significant factor in live tracking quality. A driver reporting stop completion through an app that sends structured events to the platform is a fundamentally different data source from a driver verbally reporting to dispatch by phone.

The app-based data feeds plan adherence, dwell time, and exception detection automatically. The phone-based reporting creates a manual data entry task for a dispatcher who is already managing multiple active deliveries.

[https://locus.sh/driver-companion-app/](https://locus.sh/driver-companion-app/)

The Driver Companion App provides structured driver-side reporting that feeds directly into live tracking: stop completion events, dwell time, and exceptions appear in the dispatch view without requiring manual data entry or dispatcher-driver phone contact

## Pillar 3: SLA Controls: Making Commitments You Can Keep

SLA controls are the mechanisms that translate delivery commitments into operational constraints and monitor adherence in real time.

Without them, a delivery commitment is a note in the OMS that the dispatch system may or may not have access to when building the plan.

SLA controls have three components: commitment capture (the platform knows what was promised), planning-time enforcement (the route plan honors the commitment as a constraint), and real-time monitoring (the platform surfaces SLA risk before the window closes).

### How SLA controls work in dispatch software

Commitment capture connects the dispatch platform to the commitment made at order entry. This may be an OMS integration, a direct entry at dispatch time, or an inferred commitment based on order type and service level. Without this input, the planning engine cannot enforce what it does not know.

Planning-time enforcement means committed delivery windows are treated as hard constraints in the route optimization.

A route plan that delivers stop 25 at 4:15 PM when the commitment was 2 PM to 4 PM has a planning failure. The commitment was known; the plan did not honor it. This failure is invisible in a system where SLA data is stored in the OMS and the dispatch system builds routes independently.

Real-time SLA monitoring compares actual delivery progress against committed windows throughout the delivery day. The monitoring layer knows which stops have which windows and which stops are falling behind relative to those windows. It generates alerts when the projected arrival time for a committed delivery crosses a defined threshold, giving the dispatcher time to act.

### SLA monitoring vs. SLA enforcement

| SLA monitoring | SLA enforcement |
| --- | --- |
| Records whether commitments were met | Treats commitments as constraints before planning begins |
| Reports breaches after they occur | Alerts to SLA risk before the window closes |
| Shows delivery performance in retrospect | Surfaces intervention options while they are still available |
| Useful for carrier management reviews and NPS attribution | Useful for dispatchers managing active delivery operations |
| Answers: how many SLA breaches did we have? | Answers: which commitments are at risk right now, and what can we do about it? |

## How the Three Pillars Connect

Assignment logic, live tracking, and SLA controls form a system in which each pillar depends on the outputs of the others.

Assignment logic produces the plan. Live tracking monitors execution against the plan. SLA controls evaluate plan adherence against commitments. Weakness in any pillar creates a gap that the other two cannot compensate for.

### Why weak links break the system

- **Weak assignment logic:** A suboptimal plan produces more plan-adherence deviations for live tracking to surface and more SLA risks for the monitoring layer to alert on. Better assignment logic reduces the volume of exceptions that the other two pillars have to manage
- **Weak live tracking:** Strong assignment logic and SLA enforcement mean nothing if exception signals arrive after the SLA window closes. Live tracking is the early warning layer that preserves intervention opportunity
- **Weak SLA controls:** A platform with strong routing and real-time GPS tracking but no SLA enforcement gives dispatchers a live view of a plan that may already violate commitments. The visibility is present; the benchmark for what the visibility means is absent
- **Disconnected data layers:** The most common failure mode in assembled dispatch systems. The [route planner](https://locus.sh/blogs/software-for-route-planning/) uses one dataset, the tracking layer uses another, and SLA data lives in the OMS. Re-allocation decisions made from stale carrier capacity data or routing decisions made without current SLA status produce incorrect outputs regardless of how capable each pillar is individually

## Questions to Ask Every Vendor

These questions surface the gap between a feature claim and an implementation. Ask for specific answers during a technical evaluation, not a standard demo:

### For assignment logic

- How many simultaneous constraints does the optimization engine process, and what happens when constraints conflict?
- Does the engine optimize the full order set simultaneously or assign orders sequentially?
- When a vehicle breaks down mid-day, can the platform re-allocate the affected orders without rebuilding the full route plan?
- Can priority rules be configured per order type, channel, or customer tier, and do they apply automatically at assignment time?
- How does the engine differentiate between captive fleet, contracted carriers, and on-demand capacity in cost and SLA calculations?

### For live tracking

- What is the GPS position update frequency for vehicles reporting through your platform, and does it vary by vehicle or carrier type?
- Does the platform show planned arrival time versus actual arrival time by stop, or only vehicle position?
- At what point does the platform generate an SLA risk alert: before the window closes, at the window, or in end-of-day reporting?
- How do drivers report stop completion and exceptions: through a dedicated app, by phone, or through carrier API?

### For SLA controls

- Are delivery window commitments treated as hard constraints or soft preferences in the route optimization?
- At what threshold before an SLA breach does the platform surface an alert to the dispatcher?
- Can different SLA rules be configured per order type, customer tier, or fulfillment channel?
- What delivery event data does the platform retain to support SLA compliance reporting and dispute resolution?

## How Locus Addresses All Three Pillars

Locus is the world’s first Decision-Intelligent, Agentic TMS. Its approach to the three evaluation pillars is architecturally integrated: assignment logic, live tracking, and SLA controls share the same data layer, so decisions made in one function immediately update the state that the others draw from.

For assignment logic, the Dispatch Agent and Carrier Agent within Locus’s multi-agent architecture evaluate order-to-vehicle and order-to-carrier matching across 250+ simultaneous real-world constraints.

The [route optimization](https://locus.sh/route-optimization/)
 layer processes the full order set and produces assignments that balance SLA compliance, vehicle capacity, driver hours, and cost without requiring a dispatcher to resolve conflicts manually.

[ShipFlex](https://locus.sh/ship-flex/)
 extends assignment logic to contracted carriers, maintaining distinct cost and SLA rules per carrier type across 160+ active carriers from a broader network of 1,000+ pre-integrated partners.

For live tracking, a unified real-time visibility layer within Locus’s agentic TMS aggregates position updates, stop completion events, and carrier status signals into a single operational view that compares actual execution against the plan.

The [Driver Companion App](https://locus.sh/driver-companion-app/)
 provides structured driver-side reporting: stop completion, dwell time, and exception events feed into the platform automatically, making plan adherence visible without phone-based dispatcher-driver contact. Exception signals surface before SLA windows close, giving Mycroft AI Co-Pilot the context to present intervention options to dispatchers as soon as risk emerges.

For SLA controls, committed delivery windows are planning constraints in Locus, not reference data. The route optimizer treats them as hard boundaries. When plan-vs-actual comparison shows a delivery falling behind its committed window, the platform surfaces the alert with enough lead time for a corrective action: re-sequencing, carrier reassignment, or customer notification.

Locus has been recognized in Gartner research on last-mile delivery and supply chain execution technologies for seven consecutive years, including in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies and the 2025 Market Guide for Last-Mile Delivery Technology Solutions.

It serves 360+ enterprise customers across [e-commerce and retail](https://locus.sh/ecommerce-logistics/)
, [FMCG and CPG](https://locus.sh/fmcg-cpg-logistics/)
, and 3PL verticals in 30+ countries, with $320M+ in collective logistics cost savings and 99.5% on-time SLA adherence. In October 2025, Ingka Investments, the investment arm of Ingka Group, acquired Locus, providing long-term institutional backing to a platform that continues to operate independently.

[https://locus.sh/last-mile-delivery-software/](https://locus.sh/last-mile-delivery-software/)

Locus connects assignment logic, live tracking, and SLA controls through a shared data layer, ensuring that the re-allocation decision made by the assignment engine immediately updates the tracking view and the SLA monitoring layer

## Optimize Deliveries With Dispatch Management Software

Choosing dispatch management software on routing quality alone produces platforms that optimize the morning plan and leave the rest of the delivery day to dispatchers.

The three pillars of assignment logic, live tracking, and SLA controls determine whether the platform performs throughout the day.

Assignment logic sets the quality of the plan. Live tracking determines how quickly the operation learns when the plan is not being executed. SLA controls determine whether commitments are constraints or aspirations. And the shared data layer that connects all three determines whether they operate as a system or as separate tools that produce conflicting signals.

[Schedule a demo with Locus today](https://locus.sh/schedule-demo/)
 to see how assignment logic, live tracking, and SLA controls work as an integrated system.

---

## Frequently Asked Questions (FAQs)

What is the difference between dispatch management software and route planning software?

Route planning software builds delivery routes from a set of orders and constraints. It is primarily a plan-generation tool. Dispatch management software does that and adds the operational layer: assigning orders to specific vehicles and carriers, monitoring delivery execution against the plan in real time, managing driver communication, and tracking SLA adherence throughout the delivery day. Route planning is one function within dispatch management. A platform that only route plans stops contributing value when the routes leave the depot.

How does sophisticated assignment logic differ from nearest-vehicle routing?

Nearest-vehicle routing assigns each order to the closest available vehicle. It is fast and simple, and it produces acceptable results at low volume with few constraints. At enterprise volume, it produces assignments that are locally reasonable but globally suboptimal: the closest vehicle for order A may be the only vehicle in the right zone for orders B through G. Sophisticated assignment logic evaluates the full order set simultaneously and finds assignments that minimize cost and maximize SLA compliance across all orders. The quality difference compounds with order volume and network complexity.

What GPS update frequency is adequate for enterprise dispatch management?

For urban last-mile operations with dense stop sequences, a 30-second update interval is the practical minimum for exception detection to be useful. At 5-minute update intervals, a vehicle can miss a stop, dwell at an incorrect location, or diverge from the route plan by a significant distance before the dispatcher sees the deviation. For less time-sensitive operations, longer intervals may be acceptable. Confirm the actual update frequency the platform provides in your specific geography and carrier type. Some platforms advertise high-frequency updates but deliver them only when cellular connectivity is strong.

What does SLA enforcement mean in dispatch software?

SLA enforcement means committed delivery windows are treated as hard constraints in route planning, not as reference data the dispatcher reviews after the plan is built. A route optimizer that enforces SLAs will not produce a plan that delivers an order outside its committed window even if that plan is otherwise more efficient. Enforcement also applies in real time: when actual delivery progress shows an SLA risk emerging, the platform surfaces the alert before the window closes, with enough lead time for a corrective action. SLA enforcement is distinct from SLA monitoring, which records whether commitments were met after the fact.

How does Locus handle assignment logic, live tracking, and SLA controls in one platform?

Locus handles all three through a shared data layer where each function draws from and contributes to the same operational state. For assignment logic, the Dispatch Agent and Carrier Agent evaluate the full order set against 250+ constraints, with route optimization building sequences that treat SLA windows as hard constraints. ShipFlex extends assignment logic to contracted carrier networks with carrier-specific rules. For live tracking, a unified real-time visibility layer aggregates structured driver reporting from the Driver Companion App with carrier status updates, comparing actual execution against the plan by stop. Mycroft AI Co-Pilot surfaces SLA risk signals to dispatchers before windows close. For SLA controls, committed windows are planning constraints from the moment the route is built, and real-time monitoring flags deviations at a threshold that preserves intervention time.

MEET THE AUTHOR

Team Locus

Written by the Locus Solutions Team—logistics technology experts helping enterprise fleets scale with confidence and precision.

### Related Tags:

[https://locus.sh/blogs/what-is-a-dispatch-orchestration-platform/](https://locus.sh/blogs/what-is-a-dispatch-orchestration-platform/)
#### [General](https://locus.sh/blogs/category/general/)

## [What Is a Dispatch Orchestration Platform?](https://locus.sh/blogs/what-is-a-dispatch-orchestration-platform/)

[Team Locus](https://locus.sh/blogs/author/team-locus/)

Sep 14, 2026

Discover what a dispatch orchestration platform does beyond dispatch management, including real-time allocation, multi-carrier coordination, and decision intelligence.

[Read more](https://locus.sh/blogs/what-is-a-dispatch-orchestration-platform/)

[https://locus.sh/blogs/how-to-choose-field-service-dispatch-software/](https://locus.sh/blogs/how-to-choose-field-service-dispatch-software/)
#### [General](https://locus.sh/blogs/category/general/)

## [How to Choose Field Service Dispatch Software: Technician Scheduling, Routing, and On-Site Proof](https://locus.sh/blogs/how-to-choose-field-service-dispatch-software/)

[Team Locus](https://locus.sh/blogs/author/team-locus/)

Sep 14, 2026

Evaluate field service dispatch software across three pillars: technician scheduling, routing, and on-site proof. Questions to ask every vendor included.

[Read more](https://locus.sh/blogs/how-to-choose-field-service-dispatch-software/)

## How to Choose Dispatch Management Software: Assignment Logic, Live Tracking, and SLA Controls

- Share
- [Print](javascript:window.print())
- [Download](#)
- [Schedule a Demo](https://locus.sh/schedule-demo/)

### Is your team spending more time on fixing logistics plan than running the operation?

- Agentic transportation management from order intake to freight settlement
- Route optimization built on 250+ real-world constraints
- AI-driven dispatch with automatic execution handling

20%Cost Reduction

66%Faster Planning Cycles

[Schedule a demo](/schedule-demo/)

Insights Worth Your Time

#### [General](https://locus.sh/blogs/category/general/)

## [Locus 2026 UK Consumer Survey: Why Returns Visibility is Now the Conversion Engine for AI-Driven Shopping in UK Retail](https://locus.sh/blogs/returns-visibility-conversion-engine-ai-shopping-uk-retail-locus-q2-2026-consumer-survey/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

May 29, 2026

#### [General](https://locus.sh/blogs/category/general/)

## [Locus 2026 US Consumer Survey: Generative AI isn’t Just Changing How Consumers Shop, it’s Breaking the Demand Patterns US Retail Was Built On](https://locus.sh/blogs/generative-ai-shopping-effect-retail-fulfillment-operations-locus-q2-2026-consumer-survey/)

[Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/)

May 29, 2026

#### [General](https://locus.sh/blogs/category/general/)

## [Embedded vs Bolted-On AI: The Architecture Question European Logistics Buyers Are Asking](https://locus.sh/blogs/embedded-vs-bolted-on-ai-european-logistics-platform-architecture-business-benefits/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

May 21, 2026

#### [General](https://locus.sh/blogs/category/general/)

## [Hybrid Fleet Management: How Owned, 3PL, Gig, ICE, and EV Capacity Actually Operate at Most Enterprises](https://locus.sh/blogs/three-workforce-fleet-reality-owned-3pl-gig-drivers/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

May 7, 2026

#### [General](https://locus.sh/blogs/category/general/)

## [US Returns Hit $850 Billion in 2025: Why US Retailers Are Restructuring Reverse Logistics in 2026](https://locus.sh/blogs/850-billion-us-returns-ai-routing-reverse-logistics-2026/)

[Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/)

May 7, 2026