Skip to content
Kavell
Pillar 01 · Ports Pillar

Auto-dispatch freight drivers and port labor against the rules you already use.

Configure the criteria once. Auto-dispatch applies them. Exceptions route to a supervisor with the reasoning attached. Every decision is grievance-defensible and HOS-defensible.

Dispatch supervisor reviewing assignments and rule criteria across a wall of operations dashboards.
Auto-dispatch applies your union, certification, HOS, and fatigue rules in one pass.
What this pillar does

The specific work this pillar automates.

Criteria-based auto-dispatch

Configure the rules once — seniority tier, certifications, shift rotation, proximity, fatigue limit — and the engine dispatches within them.

Eligibility enforcement

Drivers or workers without a current credential, required certification, or rest-hour clearance are never auto-dispatched. Rule violations become exceptions, not silent failures.

Supervisor exceptions

When auto-dispatch cannot place a driver or worker, the exception routes to a supervisor with the reasoning attached — always explainable, never a black box.

Union and HOS rule compliance

DOT hours-of-service for drivers. ILA and ILWU pay rules, rotation, and skill restrictions for port labor. Applied before the assignment publishes.

Real-time rebalancing

Delays, no-shows, and safety incidents trigger automatic re-dispatch without a supervisor having to rebuild the board.

Audit-ready history

Every dispatch decision — automatic or supervisor-reviewed — is logged with criteria, inputs, and timestamp for grievance and HOS defense.

Auto-dispatch criteria you configure

You set the rules. The engine dispatches. Exceptions route to a supervisor.

  • Seniority tier
  • Certifications held
  • Union rules (ILA / ILWU)
  • DOT hours-of-service clearance
  • Availability windows
  • Skill tags
  • Equipment / vehicle ratings
  • Physical proximity
  • Overtime thresholds
  • Fatigue limits & rest hours
  • Credential validity (TWIC, CDL, endorsements)
  • Medical clearance status
  • Preference or opt-out flags
How the workflow runs

From trigger to completion.

  1. Step 01

    Need arrives

    Vessel arrival, load tender, or work order publishes. Kavell ingests the requirement and compares it against the criteria set.

  2. Step 02

    Engine builds eligible pool

    The criteria engine filters drivers or workers by all configured rules in one pass, rank-ordered by your weighting.

  3. Step 03

    Auto-dispatch assigns

    Assignments publish automatically when confidence is high. Low-confidence cases route to supervisor review.

  4. Step 04

    Notifications and acknowledgements

    Driver or worker receives assignment via app, SMS, or voice. Acknowledgements feed back into the board in real time.

  5. Step 05

    Exception handling

    No-shows and refusals trigger automatic rebuild. The supervisor sees the re-dispatch reasoning, not the full recomputation.

  6. Step 06

    Grievance-ready log

    Every decision and input is logged for audit. If a grievance or HOS challenge arises, the full rule path is reviewable in one click.

Integrations

Systems we already speak.

TMS (McLeod, Turvo, MercuryGate)Terminal Operating SystemsPayroll gatewaysTWIC readersELD devicesCommunications (SMS, app, voice)
Modeled · terminal simulation
42% fewer

Modeled reduction in dispatch exceptions after auto-dispatch criteria go live on a simulated terminal.

FAQ

Questions buyers ask us first.

The honest answers. If your question is missing, book a fit call and we will answer it live.

Does this work for trucking fleets as well as port labor?
Yes. Auto-dispatch is designed for any workforce with rules: DOT hours-of-service for drivers, union rules for longshore labor, and skill / equipment matching for both. Configuration switches the ruleset, not the engine.
Can we run partial auto-dispatch and keep supervisor review for some positions?
Yes. Auto-dispatch is configurable per lane, position, crew, or shift type. Many sites start with low-risk positions on full auto and keep critical roles in supervisor-review mode for the first 60 days.
How are criteria weights configured?
Through a supervisor-facing rule editor. Weights, hard rules, and tie-breakers are all editable without developer involvement.
Does this integrate with our TMS or TOS?
Yes. We integrate with major TMS systems (McLeod, Turvo, MercuryGate) and Terminal Operating Systems for both load tenders and vessel arrivals — reading needs and writing assignment status.
Can we see the reasoning behind a dispatch decision?
Yes. Every assignment has an expandable reasoning panel showing which criteria matched, how tie-breakers resolved, and which drivers or workers were filtered and why.
Other pillars

Explore the rest of the workforce engine.