Free OpenClaw Skill for Trucking Companies: Dispatcher and Compliance Agent (Download)

What this skill does for your trucking businesses

• Scans DAT Load Board, Truckstop.com, and direct broker feeds for loads matching your equipment, lanes, and minimum rate-per-mile, then drafts the broker outreach.
• Triages driver check-calls and dispatcher SMS into status (rolling, delay, breakdown, HOS exhausted) with one-line escalation summaries for the after-hours dispatcher.
• Reads Motive or KeepTruckin ELD logs against FMCSA Hours of Service to flag drivers approaching the 11/14/70 limits before they bust.
• Runs the driver retention cadence (week 1, day 30, day 90, anniversary) keyed to miles run, home time, and pay per mile vs the fleet average.
• Compiles the weekly settlement summary from McLeod LoadMaster, TMW Suite, or Axon, with margin and detention flagged.

What's inside this OpenClaw skill

The full file you download, indexed below for search engines and for operators who want to read before they install.

---
name: trucking-dispatcher-and-compliance
description: Dispatcher and compliance agent for trucking companies. Handles load board sourcing, driver dispatch triage, FMCSA Hours of Service review, settlement digests, and driver retention outreach. Integrates with McLeod LoadMaster, TMW Suite, Axon, DAT Load Board, Truckstop.com, Motive, KeepTruckin.
version: 1.0.0
author: OpenClaw Consult (Adhiraj Hangal)
license: MIT
url: https://openclawconsult.com/skills/trucking-companies
---

# OpenClaw Skill: Trucking Dispatcher and Compliance Agent

## Overview

This skill turns the OpenClaw agent into a working dispatcher and compliance
layer for a small-to-midsize trucking carrier. It does not replace the
dispatcher, the safety manager, or the operations director. It owns the
high-volume triage so the human roles spend their time on margin, driver
relationships, and exception handling.

It is designed for CDL Class A fleets running 5 to 75 trucks, with a back
office on McLeod LoadMaster, TMW Suite, Axon, or Tailwind TMS, and an ELD
provider on Motive (formerly KeepTruckin) or a comparable platform. Single
terminal and small multi-terminal operations both work.

## What this skill does

1. Load board scanning across DAT and Truckstop.com against your rate floor
2. Broker outreach drafted and scored against historical pay performance
3. Driver check-call triage with HOS-aware escalation summaries
4. FMCSA Hours of Service projection against the 11/14/70 limits
5. Driver retention cadence (week 1, day 30, day 90, anniversary)
6. Weekly settlement digest with margin and detention flagged

## Triggers

```yaml
triggers:
  - type: heartbeat
    schedule: "0 5 * * *"           # Daily 5am
    action: morning_load_board_sweep

  - type: heartbeat
    schedule: "0/30 * * * *"        # Every 30 minutes
    action: poll_eld_for_hos_state

  - type: heartbeat
    schedule: "0 17 * * *"          # Daily 5pm
    action: evening_check_call_triage

  - type: heartbeat
    schedule: "0 6 * * 1"           # Monday 6am
    action: weekly_settlement_digest

  - type: on_event
    event: eld.hos_threshold_approaching
    action: flag_driver_to_dispatcher

  - type: on_event
    event: tms.load_dispatched
    action: enter_load_tracking_state

  - type: on_event
    event: tms.load_delivered
    action: close_load_and_score_broker
```

## Workflow: load board sweep

Every morning at 5am the agent:

1. Pulls available loads from DAT Load Board and Truckstop.com matching your
   equipment type, weight capacity, and registered lanes
2. Filters against your minimum rate-per-mile threshold (configured per lane
   if seasonal)
3. Cross-references the empty truck list from your TMS (current location,
   driver hours available, home-time window)
4. Scores each candidate load on margin, broker payment history, detention
   policy, and dead-head miles
5. Drafts the broker outreach for the top 10 loads
6. Routes to the dispatcher for approval; everything else is filed silently

A representative 15-truck operation sees 300 to 600 lane-matched loads per
morning. The skill surfaces the 5 to 15 that are worth bidding on this hour.

## Workflow: HOS compliance projection

Every 30 minutes the agent reads ELD duty status from Motive (or KeepTruckin)
and projects each driver forward against the FMCSA limits in 49 CFR 395:

- 11-hour driving limit within a 14-hour on-duty window
- 14-hour on-duty window from start of shift
- 70-hour 8-day rolling cap (or 60-hour 7-day rolling cap if you elected that)
- 30-minute break requirement after 8 hours driving
- 10-hour off-duty reset before a new shift

When a driver is within 90 minutes of the 14-hour clock or within 4 hours of
the 70-hour rolling cap, the dispatcher gets flagged with the recommended
action: mandatory break, relay, repower with team, or schedule the 34-hour
restart.

The skill does not edit ELD logs. Log edits stay with the safety manager.

## Workflow: driver check-call triage

Inbound driver SMS, dispatcher voicemails, and ELD events are bucketed into:

- Rolling on schedule (auto-acknowledge, log to TMS)
- Delay under 60 minutes (auto-acknowledge with revised ETA)
- Delay over 60 minutes (route to dispatcher with summary)
- Breakdown (route to dispatcher immediately; suggest tow vendor from your
  preferred-vendor list by region)
- HOS exhausted or approaching (route to dispatcher with relay options)
- Personal emergency (route to dispatcher; suggest backup driver)

The skill drafts the response in your dispatcher's voice. Defaults route any
breakdown, any HOS exception, and any personal emergency to a human.

## Workflow: driver retention cadence

Driver turnover is the single most expensive line item for most carriers.
The skill keeps the retention cadence consistent:

- Week 1: orientation check-in (equipment, paperwork, first-load feedback)
- Day 30: pay statement walkthrough and home-time review
- Day 90: route preference conversation and equipment swap if needed
- Anniversary: pay-rate review against fleet average and seniority pay raise

For drivers running miles below the fleet average or with frequent home-time
complaints, the cadence accelerates and the operations director gets a Slack
ping for a 1-on-1 call.

## Workflow: weekly settlement digest

Every Monday 6am the agent compiles the prior week:

- Total loads, total miles, total revenue
- Revenue per truck and revenue per driver, ranked
- Top 5 brokers by margin and by detention paid
- Bottom 5 brokers by slow-pay days
- Detention claims pending and approved
- Fuel cost vs IFTA-equivalent budget
- Maintenance reserve draw and projected payoff for lease-purchase units

The digest goes to the operations director with the dispatcher CC'd. Anomalies
(broker payment slowing, lane margin compressing, fuel slippage) are called
out at the top.

## Memory keys

```yaml
memory:
  - key: trucking.driver_state[{driver_id}]
    description: Driver duty status, hours available, home-time window
    schema: { duty_status: string, hours_drive_remaining: number, hours_duty_remaining: number, hours_cycle_remaining: number, home_time_due: date }

  - key: trucking.load_state[{load_id}]
    description: Current load tracking state
    values: [bidding, dispatched, rolling, delayed, breakdown, delivered, settled]

  - key: trucking.broker_scorecard[{broker_mc_number}]
    description: Broker performance history
    schema: { loads_hauled: number, avg_rate_per_mile: number, avg_pay_days: number, detention_pay_rate: number, last_load: date }

  - key: trucking.retention_state[{driver_id}]
    description: Driver retention cadence stage
    values: [week_1, day_30, day_90, anniversary, dormant, exit_risk]
```

## Message templates

```yaml
templates:
  broker_outreach_load_bid:
    body: |
      {broker_first_name},

      {your_name} from {carrier_name} (MC {your_mc}). We have a 53' dry van
      in {origin_city} available for a {pickup_window} pickup. Saw load
      {load_id} on DAT, {origin_city} to {dest_city}.

      We can be on it for ${proposed_rate}, all-in, with no detention claim
      for the first 2 hours. Asset is empty, driver has full HOS, on-time
      record on this lane is 98%.

      Confirm and I send the BOL setup now.

  driver_check_in_week_1:
    channel: sms
    body: |
      Hey {driver_first_name}, {dispatcher_first_name} here. You wrapped your
      first full week with us. Quick check: equipment running clean? Any
      paperwork still pending? Home time on track for next weekend?

      Reply any time, or call dispatch direct.

  hos_warning_to_dispatcher:
    channel: slack
    body: |
      HOS WATCH
      Driver: {driver_first_name} {driver_last_name}
      Truck: {truck_number}
      Load: {load_id} ({origin} -> {dest})
      Time to 14-hr clock: {minutes_remaining} min
      Recommendation: {recommended_action}
      Relay options: {relay_options_summary}

  detention_claim_draft:
    body: |
      {broker_first_name},

      Detention claim on load {load_id}. Per the rate confirmation, free time
      was 2 hours after the {pickup_or_delivery} appointment of
      {scheduled_time}. Driver arrived at {arrival_time} and was released
      at {release_time}, for {hours_detained} hours of detention.

      Per ${detention_rate} per hour after the 2-hour grace, that's
      ${detention_total}. Attaching the in/out gate stamps and ELD trace.

      {your_name}, {carrier_name}
```

## Required integrations

| Integration                | Purpose                                       | Read | Write |
|----------------------------|-----------------------------------------------|------|-------|
| McLeod LoadMaster          | Load, settlement, customer master             | yes  | optional |
| TMW Suite                  | Load, settlement, dispatch                    | yes  | optional |
| Axon Software              | Load, fuel, IFTA, settlement                  | yes  | optional |
| DAT Load Board             | Load sourcing                                 | yes  | optional |
| Truckstop.com              | Load sourcing, broker credit check            | yes  | optional |
| Motive / KeepTruckin ELD   | Driver HOS, location, status                  | yes  | no    |
| FMCSA SAFER                | CSA BASIC scores, broker MC verification      | yes  | no    |
| Twilio (or similar)        | Driver SMS                                    | no   | yes   |
| Slack                      | Dispatcher and operations alerts              | no   | yes   |
| OpenClaw Memory            | Cross-run state                               | yes  | yes   |
| OpenClaw Heartbeat         | Scheduled triggers                            | yes  | yes   |

Write-back to the TMS is optional and starts disabled. Most carriers flip
TMS writes on once the agent proves out on read-only for two to four weeks.

## Compliance notes

The skill respects FMCSA 49 CFR 395 HOS rules and does not draft any
recommendation that would knowingly put a driver out of compliance. It does
not edit ELD logs. It does not auto-confirm loads beyond the dispatcher's
approval queue.

For California-domiciled drivers, the skill carries an AB 5 independent-
contractor flag and routes any owner-operator load with California pickup or
delivery for human review of the contracting structure. Carriers running B2B
truckload should still validate their AB 5 posture with counsel; the skill
does not substitute for legal review.

## Configuration

```yaml
config:
  carrier_name: "Your Carrier Name"
  carrier_mc: "MC-XXXXXX"
  equipment_types: ["53_dry_van", "reefer", "flatbed"]
  rate_floor_per_mile:
    default: 2.10
    dry_van: 2.10
    reefer: 2.45
    flatbed: 2.65
  hours_of_service_rule: "70_hour_8_day"      # or "60_hour_7_day"
  approval_mode: dispatcher_approves_all      # or "autonomous_after_2_weeks"
  fleet_structure: company_drivers            # or "owner_operator", "lease_purchase", "mixed"
  preferred_tow_vendors_by_region: {}
  retention_cadences:
    week_1: true
    day_30: true
    day_90: true
    anniversary: true
  detention_grace_hours: 2
  load_sourcing:
    dat: enabled
    truckstop: enabled
    direct_broker_feed: optional
```

## Quick install

```bash
mkdir -p ~/.claude/skills
mv trucking-companies.md ~/.claude/skills/trucking-dispatcher-and-compliance.md
# Edit the config block to match your carrier
```

Launch OpenClaw and the skill is live. Run `morning load board sweep` or
`check HOS status` to invoke it on demand, or wait for Heartbeat to fire on
the configured schedule.

## Want it wired to your stack?

This SKILL.md is the starting point. If you want it plugged into your
specific TMS, ELD, factoring partner, and broker shortlist on a fixed-price
two-week clock, with the founder writing every line of the build, the door
is at https://www.adhirajhangal.com/work

Install in 60 seconds

1. 1

   Drop the file into your OpenClaw skills directory

   Save the downloaded trucking-companies.md as ~/.claude/skills/trucking-dispatcher-and-compliance.md (or scope it per terminal in your project-level .claude/skills/). OpenClaw picks up new skill files on next agent launch, no restart required.

2. 2

   Connect your TMS, ELD, and load board accounts

   Edit the integrations block to point at your McLeod LoadMaster, TMW Suite, or Axon API, your Motive or KeepTruckin ELD feed, and your DAT and Truckstop.com credentials. Read access on the TMS and ELD is enough to start; load board access needs read for sourcing and write only when you authorize bid submission.

3. 3

   Launch in approval mode, then move autonomous on safe templates

   Start with the dispatcher approving every outbound broker quote and driver text for two weeks. The skill defaults route any load over $4/mile, any HOS exception, any breakdown call, and any driver-retention conversation to a human. After two weeks, flip the low-risk templates (load-board screening summaries, settlement digests) to autonomous.

Example conversation

Common questions

Related free skills