Keelway
Sign in Book a demo Get Keelway free
Carrier
M01Carrier TMS M02Invoice & Collections Agent M03Track & Trace M04Email Agent M05Voice Agent
Broker
M01Broker TMS M02Fraud AI · CarrierVet M03Track & Trace M04Email Agent M05Voice Agent
Integrations PricingSign in
LTL dispatch software · Linehaul & P&D · For carriers

Standing linehauls, staffed automatically.

Keelway dispatch runs the two kinds of trips an LTL carrier actually moves: linehauls that repeat on a schedule and P&D runs that change every day. Define a standing linehaul once — lane, days, depart time, default truck, trailer, driver — and each day's manifest generates itself. Dispatch staffs freight onto it and moves on to the next decision.

ATL yard → Charlotte · Mon/Wed/Fri · 18:00 · generated daily · never duplicated

Right desk check

This page is for carriers — fleets that own the trucks, employ the drivers, and run the linehauls. Broker dispatching owner-operators? That's a different desk. Broker dispatch software →

1
manifest per standing schedule per day — generated, never duplicated
5
EDI transaction sets built in — 204, 990, 214, 210, 997
5
driver pay bases fed from dispatch — per-mile, tiered CPM, percent, hourly, per-stop
Schedule

Define the lane once

Lane, days of the week, depart time, default truck, trailer, and driver. “ATL yard → Charlotte, Mon/Wed/Fri, 18:00 depart” is one record, not a weekly chore.
Manifest

Daily manifests generate themselves

Every scheduled day produces exactly one dated manifest, pre-staffed with the schedule's defaults. Never duplicated — re-opening the board or re-saving the schedule cannot create a second copy of today's run.
Staff

Load freight, swap crew per day

Dispatch staffs shipments onto the manifest like any other run. Defaults for truck, trailer, and driver are swappable on that day's manifest without editing the standing schedule.
P&D

Pickups & deliveries, same board

P&D runs are trips alongside the linehauls — one dispatch surface for hub-to-hub freight and street work. No second system for the pickup sweep that feeds the 18:00 departure.
Drivers

One trip in the driver app

The Keelway driver app is a PWA on the phone the driver already has: trip workflow, ordered stops, POD capture, DVIR, HOS, GPS pings. A multi-shipment linehaul is one trip with ordered drops.
Shippers

Tracking links per load or truck

Public, expiring tracking pages per load or per truck — emailed to a shipper in one click. The “where's my freight” call answers itself.

Frequently asked questions

What is a standing linehaul schedule?+
A standing linehaul is a hub-to-hub run your fleet makes on a fixed rhythm — the same lane, the same days, the same depart time. In Keelway you define it once: lane, days of the week, depart time, and a default truck, trailer, and driver. From then on, Keelway generates that day's linehaul manifest automatically on every scheduled day. Dispatch staffs freight onto it instead of re-creating the run by hand.
Do daily linehaul manifests ever duplicate?+
No. Each standing schedule produces exactly one manifest per scheduled day. If today's manifest already exists, Keelway does not generate a second one — dispatch edits, weather delays, and re-opens all land on the same dated manifest. Never duplicated is the design rule, not a setting.
Can dispatch override the default truck, trailer, or driver?+
Yes. The defaults on a standing schedule pre-staff each day's manifest so the common case takes zero clicks. When a driver is out or a tractor is in the shop, dispatch swaps the truck, trailer, or driver on that day's manifest without touching the schedule itself. Tomorrow's manifest generates with the defaults again.
How do P&D runs and linehauls coexist?+
Both are trips on the same dispatch board. Linehauls generate from their standing schedules; pickup-and-delivery runs are created as trips alongside them. A dispatcher sequencing a morning P&D sweep and staffing the 18:00 linehaul is working one surface, not two systems — and every trip flows to the same driver app, tracking links, and settlement rails.
What EDI transactions does Keelway support?+
EDI 204 (load tender), 990 (tender response), 214 (shipment status), 210 (invoice), and 997 (acknowledgment) — the set retail trading partners require before they tender you freight. Every exchange has retry built in and an audit trail, so a dropped 214 gets re-sent instead of silently disappearing.
How do drivers get their trips?+
Through the Keelway driver app — a PWA that runs on the phone they already have, no extra hardware. A driver sees the trip with its ordered stops and works it stop by stop: trip workflow, POD capture at delivery, DVIR, HOS, and GPS pings back to dispatch. A multi-shipment linehaul shows up as one trip with ordered drops.
Does dispatch data flow into driver pay?+
Yes. Settlements compute from the trips dispatch actually ran. Keelway supports per-mile, tiered CPM, percent, hourly, and per-stop pay bases, with fuel, tolls, advances, and per-mile insurance deducted automatically. When an accessorial charge is payable to the driver, the driver-pay split carries through from billing. No re-keying trips into a payroll spreadsheet.
Is this for freight brokers dispatching owner-operators?+
No. This page covers carrier-side dispatch — fleets that own the trucks, employ the drivers, and run the linehauls. If you are a broker or hybrid dispatching owner-operators, Keelway has a separate product for that desk: the broker dispatch software page covers it.
Keelway LTL · Dispatch

Define the lane once. Staff freight, not calendars.

Related