Skip to main content

Logistics and transport

A moving dot is not proof of custody.

Logistics and transport software connects orders, shipments, capacity, routes, custody events, delivery and exceptions. The operating model Werkon would validate preserves the identity, timing and source of each movement record so teams can reconcile plans with physical evidence. Dispatchers, drivers and qualified operational owners retain commitment, safety, exception and claims decisions, with delivery and settlement recorded separately.

Operating realities

The same load can have five different identities.

An order, consignment, shipment, container, pallet, parcel, vehicle and route are related, not interchangeable. Events only become useful when the system preserves the level, actor, place, time and source they actually describe.

01

Identity has a physical level

A customer order may split across consignments, modes, vehicles, handling units and delivery attempts. One scan or vehicle position can be wrongly applied to every item associated with the movement.

Context evidence: Customer and commercial order, consignment and shipment, cargo line and quantity, package and handling unit, container and seal, vehicle and trailer where applicable, route leg and mode, parent and child link, shipper and consignee, identifier issuer, merge, split, substitution, correction, and final disposition.

02

An event is a claim with provenance

Scan, mobile, telematics, sensor, carrier, warehouse and manual events can arrive late, conflict, use different clocks, identify the wrong object, or report a device rather than the cargo itself.

Context evidence: Business event and step, object and granularity, event and record time, time zone, location and precision, actor and party, device and system, source message and digest, condition and sensor context, confidence, custody effect, late arrival, conflict, correction, supersession, and reviewer.

03

Optimization is not dispatch authority

A route or arrival model may omit current road, weather, vehicle, driver, cargo, facility, contract, permit, safety, service-window or local legal constraints. A lower score does not authorize a movement.

Context evidence: Planning objective, request time, inputs and freshness, service and capacity constraints, route and mode limits, vehicle and driver eligibility where applicable, break and duty context, cargo restrictions, weather and disruption sources, alternatives, estimate range, uncertainty, human review, dispatch decision, communication, and change receipt.

04

Delivery and close need more than a status

Delivered can mean left, handed over, signed, scanned at a location, or inferred by a carrier. Damage, shortage, refusal, failed access, extra work, detention, return, claim and charge disputes can remain open after the map turns green.

Context evidence: Delivery requirement and authorized recipient, arrival and attempt, location and time, custody handoff, quantity and condition, document and signature context, photo or sensor policy where permitted, refusal or exception, communication receipt, redelivery or return, charge basis, claim, settlement, correction, retention, and movement close approval.

Commitment-to-reconciliation path

Keep the promise, physical events, exceptions, and close connected.

A dependable path shows what was committed, how it was planned, who authorized movement, what happened at each handoff, who owned disruption, what the recipient accepted, and how the commercial record closed.

  1. 01

    Define the movement commitment

    Register the parties, cargo and handling identity, origin and destination, service and delivery terms, time windows, quantity and condition, documents, mode and route constraints, special handling, accessibility and communication needs, commercial basis, acceptance evidence, risks, exclusions and change authority.

    Owner
    Commercial, logistics, customer, warehouse, trade, safety, legal, finance, and data owners
    Evidence
    Order and line, consignment and shipment identifiers, party and authority, cargo and handling-unit hierarchy, quantity and unit, condition, origin and destination, service window and time zone, term and responsibility, document requirement, special handling, contact preference, price and charge basis, risk, approval, acceptance, version, and change.
  2. 02

    Plan capacity and handoffs

    Build eligible route, mode, facility, carrier, vehicle, driver, capacity, timing, custody, document and contingency options from current constraints; qualify providers and resources; expose assumptions and uncertainty; and reserve or tender without presenting a proposal as confirmed capacity.

    Owner
    Planning, procurement, dispatch, warehouse, fleet, safety, compliance, and provider owners
    Evidence
    Demand and availability snapshot, route and leg, mode and facility, provider status, capacity and unit, vehicle and driver eligibility where applicable, schedule and service window, route and cargo restriction, custody handoff, document and permit state, estimate range, cost basis, alternative, contingency, reservation or tender, acceptance, expiry, and planner review.
  3. 03

    Authorize dispatch and handoff

    Recheck the current commitment, cargo, quantity, packing, documents, resource, capacity, route, facility, driver and vehicle constraints where applicable, physical readiness and safety authority; issue the qualified dispatch; identify custody and communication owners; and keep holds or substitutions visible.

    Owner
    Qualified dispatch, warehouse, carrier, fleet, driver, safety, trade, and customer-communication owners
    Evidence
    Dispatch version and time, cargo and handling scope, pick and load record, seal and condition, resource assignment, qualification and duty checks where applicable, route and facility state, document pack, safety and cargo check, sender and receiver, custody transfer, departure evidence, hold, substitution, approval, notification, and receipt.
  4. 04

    Observe movement and own exceptions

    Capture attributable position, custody, condition, arrival, departure and communication events without overstating their certainty; compare actual state with the current plan; assign disruption to a person; preserve impact and alternatives; obtain authority before reroute or commitment change; and keep drivers and physical operators in safe control.

    Owner
    Operations control, dispatch, driver and carrier, warehouse, customer-service, safety, security, and exception owners
    Evidence
    Object and leg, event type and source, event and record time, location and precision, actor and device, custody and condition, planned and actual state, predicted range and basis, missing or conflicting event, disruption, impact, owner and deadline, driver communication, safe stopping or escalation where applicable, option, authority, reroute, revised commitment, recipient notice, receipt, and resolution.
  5. 05

    Deliver, reconcile, and close

    Verify the authorized recipient and delivery requirement, capture attempt, custody, quantity and condition evidence, record refusal or discrepancy, complete returns or claims, reconcile planned and actual movements, approved charges and service evidence, issue corrections without overwriting history, revoke access, retain the required record, and close only when open exceptions have an owner or disposition.

    Owner
    Delivery, recipient, customer-service, claims, commercial, finance, records, privacy, and security owners
    Evidence
    Arrival and attempt, destination and time, recipient identity and authority, custody handoff, quantity and condition, delivery document and context, exception or refusal, communication receipt, return or redelivery, route and service variance, approved accessorial and charge basis, invoice, claim and settlement, correction, retention, access revocation, outcome review, and close approval.

Movement authority

Automate event evidence, not physical or dispatch authority.

Deterministic systems should preserve identity, state, exact calculations, permissions, receipts and audit. Models can prepare bounded estimates and candidates. Accountable people retain dispatch, driving, physical handling, safety, custody, service, claim, commercial and regulatory authority.

01

Deterministic movement controls

Software owns tenant and role boundaries, identifiers and hierarchy, exact units and time zones, current plan and dispatch versions, resource states, event provenance, custody transitions, exception assignments, delivery receipts, charge calculations, retention and audit.

  • Order, consignment, shipment, cargo, package, handling unit, container, seal, route, leg, mode, facility, vehicle, driver, party, role, location, window, quantity, unit, condition, document, charge, and authority contracts
  • Source message and digest, event and record time, time zone, location and precision, actor, device and system, event type, business step, custody effect, condition, sequence, late arrival, duplicate, conflict, correction, supersession, and history
  • Current commitment, plan, capacity, tender, acceptance, assignment, qualification state, dispatch release, hold, departure, handoff, arrival, attempt, delivery, refusal, return, claim, settlement and close transitions
  • Exact distance, duration and charge arithmetic from approved inputs, permissions, communication and delivery receipts, exception timers, access revocation, retention, export, incident, change, rollback and audit
02

Bounded planning and prediction

Models can estimate demand, capacity, arrival, delay or risk; compare routes; detect event anomalies; classify documents; draft updates; and prioritize exceptions. Outputs remain source-linked, time-bounded, uncertainty-aware, advisory and outside dispatch or physical authority.

  • Cargo, document and event extraction candidates, entity matching, handling-unit association, duplicate and conflict detection, missing-event prompts, data-quality scores, and review queues
  • Demand, capacity, route, schedule, arrival, delay, condition, disruption, claim and cost candidates with exact inputs, freshness, constraints, range, uncertainty, evaluated conditions and abstention
  • Exception summaries, alternative plans, driver or facility messages, recipient updates and claim packets grounded in approved facts, audience, channel, language, policy, version, review and delivery state
  • Prioritization and anomaly candidates that cannot dispatch, reroute, assign unsafe work, alter duty status, establish custody, certify documents, accept delivery, approve claims, change charges, or close movement
03

Accountable movement authority

Authorized people determine whether a movement is lawful and safe, resources and capacity are suitable, dispatch or reroute may proceed, custody transfers, a delivery qualifies, an exception or claim is resolved, charges are approved, and the record can close.

  • Service commitment, carrier and provider qualification, route and mode selection, capacity acceptance, cargo and document review, commercial terms, special handling, trade and jurisdiction assessment, and customer change approval
  • Dispatch and resource assignment, driver and vehicle eligibility where applicable, load and securement authority, dangerous-goods or specialist handling, safe operation, stop work, route change, emergency response, and incident management
  • Physical count and condition, custody handoff, recipient and delivery qualification, refusal, damage and shortage response, return, redelivery, claim evidence, liability and settlement, charge approval, correction and close
  • Safety, security, privacy, accessibility, labor and environmental review, model and provider approval, integration and access change, expansion, rollback, regulatory response, export, retention and retirement

Movement-system components

Build one ledger from commitment to settled movement.

Order, warehouse, transport, fleet, carrier, tracking, customer-service, document, claims and finance tools can each expose a partial state. Explicit contracts join them without letting a dashboard overrule physical reality.

01

Commitment and cargo authority

Preserve parties and authority, orders, consignments, shipments, cargo lines, quantities and units, package and handling hierarchy, origin and destination, service and delivery terms, windows and time zones, condition, special handling, documents, communication and commercial basis.

Operating contract: An order is not a consignment, a shipment is not a handling unit, a quoted service is not accepted capacity, and a customer instruction is not automatically a safe or lawful dispatch. Every change keeps its source and authority.

02

Plan, capacity, and custody ledger

Connect route legs, modes, facilities, providers, resources, capacity, schedules, eligibility, constraints, tenders, assignments, dispatch versions, handoffs, custody, documents, holds, substitutions and accountable approvals.

Operating contract: Available is not reserved, reserved is not accepted, assigned is not ready, ready is not dispatched, and dispatched is not proof of physical departure. Each state has an owner, effective time, evidence and exception path.

03

Event and exception workspace

Normalize attributable position, status, condition, custody, arrival, departure, scan and communication events while preserving original messages, granularity, clocks, precision and uncertainty; compare plan and actual state; assign exceptions, decisions, notices and recovery.

Operating contract: A device position is not cargo position, a predicted arrival is not a promise, no message is not proof of no event, and a reroute suggestion is not dispatch. Original evidence survives normalization, conflict and correction.

04

Delivery and settlement control

Connect arrival and attempt, recipient authority, quantity and condition, custody transfer, delivery documents, discrepancies, refusal, return, claims, planned and actual service, approved charges, invoices, settlements, corrections, retention and outcome review.

Operating contract: Attempted is not delivered, a signature is not complete context, delivered is not reconciled, invoiced is not approved, and closed is not erased. Open exceptions remain visible until an authorized disposition is recorded.

Delivery path

Prove one movement before widening lanes or authority.

A live map can make inconsistent events look coherent. Start with one bounded movement type and route where commitment, handoffs, delivery, exceptions, effort, cost and harm can be inspected together.

  1. 01

    Follow the movement

    Observe order, planning, tender, capacity, preparation, dispatch, pickup, custody, in-transit events, communications, facilities, exceptions, delivery, return, claims, settlement, staff and recipient effort, cost, security, safety and known harm.

  2. 02

    Name identity and authority

    Agree object hierarchy, parties, sources, clocks, locations, units, event semantics, plan and dispatch states, resource and safety boundaries, custody, communication, delivery, charge, claim, correction, retention and stop authority.

  3. 03

    Reconcile the baseline

    Join current records without hiding duplicate identifiers, missing or late events, manual re-entry, status disagreement, planning error, exception effort, failed communication, delivery disputes, charge corrections, security gaps, safety events and harm.

  4. 04

    Pilot a controlled ledger

    Implement exact identity and state contracts, deterministic calculations, bounded prediction only if justified, qualified dispatch, attributable events, custody and exception ownership, delivery receipts, recovery, correction, export and rollback for the selected movement.

  5. 05

    Compare operating evidence

    Measure event and handoff completeness, plan and arrival error, exception ownership, delivery and settlement evidence, staff and recipient effort, provider and model cost, cybersecurity, physical safety, disputes, corrections and harmful outcomes before expanding.

Movement safeguards

A faster dispatch still needs a safer record.

Controls need to cover the whole movement and its physical consequences, not only whether the interface returned a route or status.

Identity and granularity
Keep order, consignment, shipment, cargo line, package, handling unit, container, vehicle, route leg and delivery attempt distinct; validate issuer, parent and child links, quantity, unit, split, merge, substitution and correction.
Time, place, and event provenance
Preserve event and record time, time zone, location and precision, actor, device, system, source message, object scope, business step, custody effect, condition, confidence, late arrival, conflict, correction and original history.
Route, resource, and safety authority
Apply current capacity, vehicle, driver, cargo, facility, route, mode, weather, duty, permit, service and jurisdiction constraints where relevant; expose uncertainty; and require qualified dispatch, safe operation, stop-work and emergency paths.
Custody, documents, and access
Limit data and actions by tenant, party, role, purpose, movement and time; bind handoffs to people, objects, condition and documents; protect credentials and sensitive locations; monitor suppliers; revoke access; and preserve lawful export and retention.
Exception, communication, and recovery
Assign missing or conflicting events, delay, route disruption, capacity loss, failed handoff, damage, shortage, refusal and outage to named owners; preserve options and authority; provide accessible human contact; record receipts; and test offline, retry, reconciliation and rollback paths.
Delivery, charges, and outcome review
Verify recipient and delivery context, quantity, condition and custody; retain refusal, return and claim evidence; calculate only from approved terms and actual events; preserve disputes and corrections; review cybersecurity, safety, cost, effort and harm; and stop expansion when evidence is weak.

Outcome proof

Measure reconciled movement, not dots on a map.

More frequent status updates can coexist with wrong cargo identity, unsafe dispatch, unresolved exceptions or disputed delivery. Proof must follow the commitment and physical evidence through settlement.

Baseline

  • Movements by service, party, origin and destination, mode, route, cargo and handling scope, provider, plan and dispatch state, custody, current event, exception, delivery, claim, settlement, close and known outcome
  • Events by object granularity, source, actor and device, event and record time, time zone, location and precision, business step, condition, custody effect, sequence, conflict, correction, plan variance and downstream use
  • Manual planning, tendering, re-entry, dispatch, status checking, driver and facility contact, recipient updates, exception work, document repair, delivery review, charge validation, claim handling, support, staff and recipient effort, provider fees, model cost and operating cost
  • Wrong object or destination, invalid resource, unsafe dispatch, lost custody, false location, missed handoff, stale prediction, unauthorized reroute, driver distraction, inaccessible communication, failed delivery, unsupported charge, security incident, claim, correction and harm

Outcome evidence

  • More movements preserve exact identity, current commitment, qualified dispatch, attributable events, custody, exception ownership, recipient communication, delivery context, approved charges, corrections and close
  • Dispatchers and operators receive current options and evidence they can inspect, reject or amend without a route score, arrival estimate, sensor signal, automated message or completed field becoming physical authority
  • Shippers, carriers, facilities, recipients and service teams share clearer movement state, visible uncertainty, accountable exceptions, accessible human contact, delivery evidence and correction paths without implying that every party uses one system
  • Comparable movements expose planning error, event and handoff gaps, exception and communication burden, delivery disputes, claims, cybersecurity, physical-safety events, staff and recipient effort, cost and harm instead of treating update frequency as service quality

Guardrails

  • Wrong order, consignment, shipment, package, handling unit, party, destination, time zone, quantity, unit, document, vehicle, driver, route, provider or charge; hierarchy breaks; source event is detached; duplicate or late event changes the wrong state; or access crosses movement or tenant boundaries
  • Prediction uses stale or shifted data, uncertainty is hidden, route constraints are incomplete, optimization objective conflicts with safety or service, device position is treated as cargo location, missing event is inferred, or generated communication invents fact
  • Dispatch, reroute, custody, delivery, claim, charge, safety or regulatory authority is delegated to a model; driver interaction creates distraction; physical staff cannot stop work; recipient lacks a human path; or a signature, scan or photo is treated as complete proof without context
  • Outage loses events, retries duplicate movements, correction overwrites history, supplier access persists, sensitive route or personal data leaks, unresolved exceptions disappear at close, outcome evidence is selectively reported, or expansion precedes reconciliation

Industry fit

Use this approach when one movement can be followed end to end.

Good reason to begin

  • The organization can bound one service, movement type, route pattern and party set and name cargo identity, source systems, event semantics, plan, dispatch, physical-safety, custody, exception, delivery, charge, claim, retention, effort, cost, harm and stop authority.
  • Commercial, planning, dispatch, driver and carrier, warehouse, customer-service, safety, compliance, trade, security, privacy, finance, claims, records, data and technology owners can inspect the same movement and agree every system and human authority boundary.
  • Representative historic movements and a bounded shadow, advisory, staged or live cohort can be compared before models, automated communication, additional providers, modes, lanes, cargo, customers or authority expand.
  • The operation can preserve safe manual and offline work, stop dispatch, reject plans, correct events visibly, reconcile delayed messages, provide accessible human service, export a complete record, revoke access, investigate incidents, roll back change and retire the system safely.

Resolve before beginning

  • Movement identity, party authority, cargo and service scope, event semantics, source clocks, location precision, capacity, dispatch, vehicle or driver eligibility, physical safety, custody, delivery, charge, claim, retention, correction or close is unclear or disputed.
  • The organization cannot separate plan from actual state, preserve original events, qualify providers and resources, maintain safe operating authority, identify custody, own exceptions, verify delivery context, reconcile charges, support outages or produce a reproducible movement record.
  • The desired first step begins with autonomous dispatch, route changes, driver instructions, custody decisions, delivery acceptance, claim settlement or pricing and omits identity, constraints, human authority, physical evidence, exception recovery, receipts, correction and outcome proof.
  • The business case depends on unverified arrival accuracy, capacity gain, fuel or emissions reduction, on-time performance, fewer incidents, lower effort, lower cost, claim reduction, compliance, implementation schedule, shipment volume or customer result.

Source basis

Sources behind the control model.

  • 01

    GS1

    EPCIS and Core Business Vocabulary

    Defines interoperable visibility-event structures and vocabulary for describing what, when, where, why and how across supply chains. The current listed EPCIS release is 2.0.1. It is a data-sharing standard, not proof that a reported physical event occurred, that every party adopted it, or that a movement is safe, lawful or complete.

  • 02

    United Nations Economic Commission for Europe

    UN/CEFACT Supply Chain Management standards

    Publishes trade and transport semantic resources including UN/LOCODE, UN/EDIFACT and Buy-Ship-Pay Reference Data Model material that generalizes multimodal transport and supply-chain models. These support structured exchange; mode, corridor, document, implementation and legal requirements still need exact qualification.

  • 03

    National Institute of Standards and Technology

    SP 800-161 Rev. 1 Update 1: Cybersecurity Supply Chain Risk Management Practices

    The May 2022 publication includes updates through 1 November 2024 and addresses cybersecurity risks in technology supply chains. NIST states that nongovernment use is voluntary. It does not establish physical cargo custody, transport safety, carrier compliance, route feasibility or delivery proof.

  • 04

    Federal Motor Carrier Safety Administration

    Hours of Service

    Provides current US federal motor-carrier hours-of-service resources and 2026 pilot-program notices. Its applicability depends on vehicle, operation and jurisdiction. It is included as a limited example of driver-safety constraints, not a universal transport rule or a substitute for qualified legal and safety review.

[ 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

Project guide / Logistics

Compare logistics AI projects by available operational evidence and exception-handling needs.

Open path02

Explore industry operating contexts

Compare movement and transport with field, professional, knowledge, commerce, property, service, product and production environments before choosing a system pattern.

Open path03

Connect the supply network

Separate physical events, recorded state, forecasts, qualified commitments, execution receipts, exceptions and realized service across the wider network.

Open path04

Control operational communication

Connect event truth, audience and contact authority, deterministic decisions, bounded drafting, approved release, delivery receipts, replies, correction and suppression.

Open path