Skip to main content

Dispatch optimization agent

An optimized route is not an authorized dispatch.

A dispatch optimizer compares assignments and route sequences for current jobs, drivers and vehicles within explicit operating constraints. The pattern Werkon would validate shows feasible alternatives, uncovered work, uncertain travel times and service tradeoffs. Software enforces hard rules, dispatchers approve plans, and workers retain acknowledgment, correction and safety paths. A proposed route does not establish completed service.

Resources and routes need current evidence

Demand should identify the exact job, stop, service point, requested and committed windows, priority source and dependencies. Contractual service, ordinary urgency and emergency work need distinct treatment. Worker availability, licenses, endorsements, training, duty state and qualifications must come from approved records, while vehicle capacity includes weight, volume, compartments, temperature, range, charging, maintenance and access restrictions.

Preserve coordinate reference, entrance, geocode confidence and manual corrections. Route evidence needs map and provider versions, mode restrictions, traffic, closures, construction and weather with source times and uncertainty. Historical travel, current observations and forecasts are different inputs. Navigation data does not prove a route is passable, lawful or safe for a particular worker, vehicle and load.

Tradeoffs and worker safety

Hard rules cover qualifications, capacity, loading, temperature, access, work and rest, precedence and service windows. Expose unknowns, conflicts and uncovered work rather than silently relaxing rules. Compare committed service, stability, workload, undesirable duties, distance, energy, overtime, cost and dispatcher complexity, with emissions included only where valid evidence supports them.

Workers need exact approved job details, local times, access and safety notes, contact and correction paths. They must be able to report fatigue or hazards, stop unsafe work and reach human dispatch. Protected traits, location traces, response speed or past acceptance must not become unsupported fitness or employment judgments.

Revise dispatch without losing ownership

Before changing an approved plan, re-read jobs, duty and rest, vehicle state, network conditions and customer commitments. Show affected people, route legs and notifications; do not overwrite acknowledged work or require unsafe interaction while a worker is moving. Preserve proposal, approval, publication, acknowledgment, movement, attempt and completion separately, then reconcile custody, condition, customer evidence, charges, claims and settlement.

Dispatch boundary

Propose feasible mobile work without taking the dispatcher or driver out of the loop.

Dispatch joins contractual promises, worker time, vehicle limits and changing roads. Four boundaries keep optimization subordinate to operational truth.

01

Open work, commitment, and priority context

Resolve decision time, horizon, order and job identity, pickup or delivery dependencies, exact service locations, committed windows, durations, equipment needs and the accountable source of each priority.

Required evidence: Tenant and region, local zone and business date, decision and availability time, horizon, order, shipment or job, stop and location version, dependency, requested and committed window, duration source, service requirement, priority class and owner, current state and cancellation.

02

Worker, vehicle, capacity, and network truth

Read current worker relationship, availability, qualification and duty state plus vehicle, equipment, inspection and multidimensional capacity; version geocodes, road networks, restrictions and condition feeds with time and uncertainty.

Required evidence: Worker and relationship, license and qualification, approved availability, duty and rest, vehicle and equipment, inspection and maintenance, weight, volume, unit and compartment capacity, energy or fuel, current position, network and provider version, traffic, closure, weather and source times.

03

Feasible alternatives and explicit tradeoffs

Enforce hard constraints before optimization, compare several plans against visible objective weights and uncertainty, preserve binding constraints and sensitivity, and expose unassigned work or infeasibility.

Required evidence: Constraint set and owner, hard, soft, unknown or human-decided class, rule results, travel and service interval, candidate assignments and sequences, objective terms and weights, binding constraints, violations, alternatives, unassigned jobs, lateness risk, cost and sensitivity.

04

Authorized dispatch and observed execution

Require dispatcher approval, publish one version through safe channels, preserve worker acknowledgment and correction, govern revisions and reconcile only observed movement, stop, service, exception, claim and recovery events.

Required evidence: Plan version and hash, dispatcher decision and rationale, approved assignments and routes, publication, delivery and read state, worker acknowledgment and correction, revision diff, dispatch command and receipt, departure, arrival, attempt, pickup or delivery, exception, customer evidence, claim and recovery.

Work-to-service path

Keep route proposal, dispatch commitment, and physical execution separate.

A plan is valuable only if its source state is time-correct, its constraints hold and accountable people can safely act on it.

  1. 01

    Freeze the decision-time problem

    Record the planning horizon and availability cutoff, normalize open jobs, locations, windows, dependencies and priority sources, and preserve late, missing, duplicate, canceled and conflicting demand rather than rewriting history.

    Owner
    Order, customer-service, operations and dispatch owners
    Evidence
    Decision time, horizon, input cutoff, job and source versions, customer commitment, stop and geocode, service duration, dependency, priority owner, current state, duplicate, cancellation, missingness and conflict.
  2. 02

    Resolve feasible resources and routes

    Re-read approved worker and vehicle state, apply current qualifications, capacity and safety rules and obtain time-scoped route and condition evidence without treating any feed as complete physical truth.

    Owner
    Fleet, workforce, safety, compliance and network-data owners
    Evidence
    Worker, duty, availability and qualification versions, vehicle and equipment state, capacities, inspection, current location, network and provider version, restriction, route candidates, traffic and weather observations and forecasts, uncertainty and blocked resource.
  3. 03

    Generate and compare plan candidates

    Apply hard constraints outside the model, estimate time with intervals and compare multiple assignments and sequences against disclosed service, safety, stability, fairness, distance, energy, cost and workload objectives.

    Owner
    Dispatch, safety, workforce, service and finance owners
    Evidence
    Rule evaluation, travel matrix and vintage, duration interval, objective terms and weights, candidate plans, assigned and unassigned work, binding constraints, late risk, workload, distance, energy, overtime, cost, sensitivity and abstention.
  4. 04

    Review, approve, and publish safely

    Show dispatchers every consequential tradeoff and exception, preserve their decision, publish the approved version through accessible channels and collect worker acknowledgment, correction, decline where allowed and hazard reports.

    Owner
    Accountable dispatcher, duty manager and workers
    Evidence
    Review packet, alternatives, plan diff, override and reason, approved plan and hash, affected people and jobs, publication channel, sent, delivered and read state, acknowledgment, correction, availability change, decline, hazard and escalation.
  5. 05

    Revise from current state and reconcile service

    Re-read operations before any change, preserve the prior plan, warn affected people safely and join route and stop observations to accountable service, exception, return, claim and recovery evidence without turning tracking into performance authority.

    Owner
    Dispatch, drivers, field operations, customer service and claims owners
    Evidence
    Revision trigger and decision time, fresh sources and constraints, changed jobs, people, vehicles and legs, approval and acknowledgment, departure and arrival, attempt, load and unload, delivery evidence, exception, refusal, return, damage, complaint, charge, claim and recovery.

Authority map

Separate route analytics, deterministic constraints, and human dispatch authority.

A model can compare candidates. It cannot certify a road, judge worker fitness, relax legal rules or command a moving person without accountable control.

01

Deterministic dispatch controls

Software owns tenant and region boundaries, identity and authorization, source versioning, civil time, location validation, eligibility, qualification, duty, capacity, compatibility, precedence, access, hard-rule enforcement, idempotent commands, state transitions, retention and receipts.

  • Job, stop, customer, worker, vehicle, equipment, location, region and business-date identifiers
  • License, qualification, hours, rest, capacity, maintenance, access, sequence and time-window checks
  • Plan hash, approval gate, publication, dispatch command, idempotency and uncertain-effect reconciliation
  • Source, proposal, decision, acknowledgment, revision, execution, exception and service receipts
02

Bounded optimization and AI assistance

Analytics can estimate time with uncertainty; optimization and models can prepare feasible assignments, sequences, explanations, alternatives and exception summaries while exact rules, sensitive-trait exclusions, source authority and commands remain outside the model.

  • Travel and service duration estimates with intervals and source time
  • Feasible assignment and stop-sequence candidates
  • Objective tradeoff, binding-constraint, late-risk and sensitivity explanations
  • Missing data, infeasibility, unassigned work and revision-summary drafts
03

Dispatcher, worker, and domain authority

Dispatchers own priorities, exceptions, tradeoffs and final plans; workers own corrections, acknowledgment, lawful decline and safety reports; qualified fleet, safety, compliance and service owners own resource fitness, legal rules, incidents, customer commitments and recovery.

  • Priority interpretation, unassigned work, overtime, third-party capacity and customer tradeoffs
  • Worker availability correction, route concern, fatigue or hazard report and safe stop
  • Vehicle fitness, qualification, road, dangerous-goods, access and emergency decisions
  • Dispatch approval, service exception, compensation, claim, complaint and recovery decisions

Dispatch components

Build a decision-time dispatch ledger, not a live map with a score.

Optimization can only be audited when demand, resources, routes and commitments keep their own identities and clocks.

01

Job, commitment, and location ledger

Version orders, shipments and field jobs; pickup, delivery and visit stops; dependencies; requested and committed windows; service durations; priorities; equipment needs; customer and site instructions; geocodes; entrances; access hours; current state and cancellation.

Operating contract: Free-text urgency is not contractual priority, requested window is not accepted commitment, address is not service entrance, geocode is not verified access, planned duration is not observed service time, canceled job is not open work and a private location is not general-purpose tracking data.

02

Worker, vehicle, and capacity ledger

Bind worker relationship, approved availability, duty, rest, license, qualification, access and accommodation plus vehicle, equipment, inspection, maintenance, capacity dimensions, compartments, temperature, range, fuel or charge, restriction and current observation.

Operating contract: Calendar free time is not willingness, location is not fitness, prior acceptance is not consent, license record is not current physical readiness, vehicle position is not availability, nominal capacity is not usable capacity, maintenance status is not a roadworthiness certification and tracking is not employment-performance evidence.

03

Network, condition, and estimate ledger

Version map and route provider, road or transport network, allowed mode, turns and restrictions, matrix query, historical travel, observed traffic, incident, closure, construction, weather, forecast, travel and service intervals, coverage, confidence and expiry.

Operating contract: Shortest path is not safest, routable is not lawful for every vehicle, historical speed is not live traffic, forecast is not observation, telemetry is not complete road truth, absence of closure is not passability, estimated arrival is not a promise and map-provider confidence is not operational validation.

04

Plan, dispatch, and execution ledger

Link problem snapshot, constraints, objective weights, candidates, infeasibility, dispatcher decision, approved plan, publication, worker acknowledgment, revision, idempotent command, movement, stop, service, exception, claim and recovery evidence.

Operating contract: Best score is not authorized plan, approved plan is not delivered message, read is not acknowledgment, acknowledgment is not departure, predicted arrival is not observed arrival, stop attempt is not completion, signature or scan is not condition or custody truth and completed job is not settled claim or satisfied customer.

Delivery path

Prove one region, fleet slice, and dispatch horizon before expanding.

Begin where job commitments, resource truth, route conditions, dispatch authority and physical service can be followed without unsafe autonomous action.

  1. 01

    Choose one bounded dispatch problem

    Select one region, depot or field team, short planning horizon, job family, vehicle class and service commitment with named dispatchers, current resource records, approved route data, safe worker channels and observable execution evidence.

  2. 02

    Map facts, constraints, and clocks

    Inventory order and stop states, locations, windows, durations, priorities, workers, qualifications, duty rules, vehicles, capacities, network and condition sources, civil time, source latency, dispatcher authority, acknowledgment and exceptions.

  3. 03

    Build time-safe candidate planning

    Freeze decision-time inputs, enforce hard rules deterministically, estimate travel and service intervals without future leakage, compare explicit objectives, expose infeasibility and prepare several inspectable candidates with no command authority.

  4. 04

    Test shocks, harm, and stale state

    Exercise wrong geocode, private location, daylight change, road closure, weather event, traffic outage, new worker, expiring license, hours limit, vehicle failure, capacity mismatch, dangerous-goods restriction, site delay, duplicate or canceled job, dispatcher absence and unsafe reroute.

  5. 05

    Release narrowly and reconcile execution

    Start in advisory mode, compare candidate plans with dispatcher decisions and the prior process, preserve worker feedback and follow revisions, movement, stops, service, exceptions, incidents, claims, complaints and hidden human work before permitting bounded publication.

Release controls

Six controls before a route proposal can become a dispatch.

Dispatch choices affect worker time, public safety, customer commitments and physical assets. These controls keep optimization reviewable and reversible.

The problem snapshot is time-correct
Bind region, zone, business date, decision time, horizon and input cutoff; version every job, cancellation, location, resource and condition source; preserve late and conflicting data; and prevent future execution evidence from entering historical evaluation.
Resource and route truth stay qualified
Re-read worker relationship, availability, duty, qualification and current vehicle, equipment and capacity state; version geocodes, network, traffic, closure and weather evidence; and treat calendar, navigation and telemetry as bounded inputs rather than operational proof.
Hard constraints never disappear for a score
Encode current safety, legal, license, qualification, hours, rest, capacity, maintenance, access, precedence and committed-window rules under qualified owners; classify unknowns; block or escalate conflicts; and never silently relax a hard rule.
Objectives and uncertainty are inspectable
Show service, priority, safety, stability, fairness, distance, time, energy, overtime, cost and dispatcher-work weights plus travel intervals, alternatives, binding constraints, sensitivity, unassigned work and infeasibility before review.
People keep dispatch and safety authority
Require dispatcher approval and rationale, publish one version through an accessible safe channel, preserve worker acknowledgment and correction, protect hazard and safe-stop paths and forbid employment decisions from optimizer or tracking activity alone.
Revisions and service states are reconciled
Re-read current state before change, show affected jobs, people, vehicles and legs, avoid unsafe interaction while moving, preserve prior versions and distinguish dispatch, acknowledgment, movement, attempt, service, condition, claim and recovery evidence.

Outcome evidence

Measure feasible service and safe execution, not route-score improvement.

A shorter plan can still be infeasible, unsafe or operationally expensive. Evidence must join the decision-time snapshot to accountable execution and service outcomes.

Baseline

  • Regions, depots, job families, commitments, priorities, stop and address quality, workers, qualifications, duty rules, vehicle classes, capacities, route providers, condition feeds, dispatchers, channels and exception owners
  • Current dispatcher, worker and customer time from order readiness through planning, review, publication, acknowledgment, revision, travel, stop, service, exception, claim and recovery
  • Current infeasible and unassigned work, late-risk plans, geocode defects, stale states, route errors, capacity blocks, qualification blocks, hours and rest conflicts, route churn, failed messages, worker corrections, unsafe suggestions and manual replanning
  • Current planned and actual travel and service, attempts, completions, late and early events, returns, damages, incidents, charges, claims, complaints and recovery with source coverage and outcome maturity

Outcome evidence

  • Correct decision time, job, location, window, duration, priority, worker, qualification, vehicle, capacity, network, condition, constraint, objective, approval and dispatch-state handling against authoritative evidence
  • Feasible-plan rate, useful abstention, unassigned work, plan stability, worker correction, dispatcher acceptance, ETA and service-duration error, successful acknowledgment and observed service by region, job, worker context, vehicle class and condition
  • Unsafe or unlawful route, unqualified assignment, capacity breach, hours and rest breach, hidden infeasibility, sensitive-trait proxy, unstable reroute, duplicate command, unsafe interaction, privacy exposure and false completion prevention
  • Dispatcher and worker effort, overtime, empty travel, energy, late service, attempts, completions, exceptions, incidents, claims, complaints and recovery against the prior process with demand, geography, traffic, weather and fleet mix visible

Guardrails

  • Wrong tenant, region, customer, job, worker or vehicle; exposed home or worker location; excessive tracking; unauthorized monitoring reuse; inferred fitness or sensitive traits; and inaccessible or punitive correction, decline, hazard or safe-stop path
  • Stale job or cancellation, wrong geocode, cross-zone time error, future leakage, invalid qualification, unavailable resource, maintenance block, capacity breach, closed or restricted road, weather risk, missing access and unowned hard-rule conflict
  • Distance or cost minimized over safety, infeasibility hidden, hard rule relaxed, unfair undesirable work concentrated, route provider treated as legal authority, ETA promised, approved plan changed without review, moving worker distracted and uncertain command retried blindly
  • Read message called acknowledgment, tracking point called departure or arrival without rule, stop geofence called service, signature called condition proof, completed job called customer satisfaction, incident minimized, claim closed without authority and weak observational result presented as causal saving

Fit test

Use this pattern when dispatch facts and physical service are observable.

Good reason to begin

  • One region has durable job and stop identifiers, verified service locations, explicit commitments and priority owners, current worker and vehicle records, versioned route and condition sources and named dispatch authority.
  • Safety, legal, qualification, duty, rest, capacity, maintenance, access, precedence and service rules can be encoded deterministically with effective versions and qualified owners.
  • Workers have accessible acknowledgment, correction, hazard, safe-stop and human-dispatch paths, and tracking purpose, visibility, retention and employment-use boundaries are explicit.
  • Plan versions, dispatch commands, movement observations, stop events, service evidence, exceptions, incidents, claims and recovery can be reconciled without treating one feed as complete truth.

Resolve before beginning

  • Job, location, priority, worker, vehicle, qualification, duty, capacity, road, safety, dispatch, tracking, acknowledgment, exception or service ownership is missing or stale.
  • The process cannot distinguish requested from committed window, calendar from availability, routable from lawful or safe, plan from dispatch, message from acknowledgment, geofence from service or signature from custody and condition.
  • Success is defined by distance, utilization, ETA or route-score improvement without feasibility, safety, worker harm, privacy, correction, plan churn, dispatcher burden, service, incident, claim and outcome maturity.
  • The optimizer is expected to invent capacity, infer worker fitness, ignore hard rules, choose employment consequences, hide unassigned work, issue autonomous dispatch, track beyond purpose, distract moving workers, retry unknown commands or guarantee arrival and saving.

Source basis

Sources behind the control model.

  • 01

    International Organization for Standardization

    ISO 19133:2005: Tracking and navigation services

    ISO says this international standard was last reviewed and confirmed in 2022 and remains current. Its public abstract describes data types and operations for tracking and navigation services, including web-service use. It does not establish geocode correctness, live road state, legal or safe routing, travel-time accuracy, worker or vehicle eligibility, dispatch authority, physical service, compliance or outcome.

  • 02

    International Organization for Standardization

    ISO 39001:2012: Road traffic safety management systems

    ISO lists this published standard as current after 2023 confirmation, with a 2024 amendment, while also marking it to be revised and showing a replacement under development. Its public abstract covers road-traffic-safety policy, objectives, action plans and factors an organization can control or influence. It does not define a safe route, dispatch constraint, driver fitness, legal duty rule, control implementation, certification status or reduced-injury outcome.

  • 03

    RFC Editor

    RFC 5545: Internet Calendaring and Scheduling Core Object Specification

    This standards-track specification defines an exchange format for events, tasks and free or busy information and has later updates. Calendar data does not prove worker identity, employment, qualification, availability, willingness, duty state, vehicle capacity, route feasibility, dispatch acknowledgment, time worked, physical service or compliance.

  • 04

    National Institute of Standards and Technology

    NIST AI RMF 1.0

    NIST describes AI RMF 1.0 as voluntary, rights-preserving, non-sector-specific and use-case agnostic, and NIST states that the framework is being revised. It does not define dispatch entities, route sources, safety or legal constraints, optimization objectives, evaluation groups or thresholds, operational authority, compliance or demonstrated service and safety outcomes.

[ WORKFLOW / SYSTEMS AUDIT ]
THE FIRST ENGAGEMENT

Start with one real workflow

A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.

Show Us the WorkflowStart with the free automation readiness checklist

OBSERVEQUANTIFYDECIDEBUILD

Continue with the work

Choose the next useful path.

Stay with the operating question. The technology can wait until the work is clear.

01

Explore governed AI agents

Compare other bounded agent patterns and the evidence, authority and recovery contracts they require.

Open path02

Design logistics and transport operations

Frame movement identity, planning, dispatch, custody, exceptions, delivery, claims and settlement around accountable operational evidence.

Open path03

Prepare accountable workforce schedules

Separate time-safe demand, worker constraints, rule ownership, manager approval, acknowledgment and actual-work evidence before mobile assignment.

Open path04

Design operations workflow automation

Keep triggers, state transitions, policy, typed actions, exceptions and reconciliation explicit across operational workflows.

Open path