Keelway
Platform · Operations

Load management without the re-keying tax.

The legacy carrier-TMS load entry workflow has not changed since rate confirmations were faxes. Read the PDF, retype the data into the TMS, attach the original, set the status, repeat. A 50-truck carrier does that 200 times a week. Keelway extracts the load straight from the rate con, lets the dispatcher review and book in 30 seconds, and tracks the load through every status without anyone clicking through five screens.

Talk to salesAI email triage
7
Load statuses tracked
Open through Canceled, auto-advanced
<30s
Per-load review after auto-extract
Vs. minutes of re-keying
12h
Stuck-load alert threshold
Default — configurable per desk
Lifecycle

Seven statuses, auto-advanced

Open, Booked, In Transit, Delivered, Invoiced, Closed, Canceled. Status advances on real events — tracking pings, POD uploads, invoice generation — without anyone clicking through screens. The full state history is in the audit log.
Auto-extract

Rate confirmations parse into draft loads

Broker, MC, load number, rate, lanes, dates, equipment, and notes extracted by the AI. The original PDF attaches to the load record. Dispatcher reviews, books, moves on. No re-keying.
Stuck loads

Forgotten-load alerts surfaced in the queue

Twelve hours without a status update, a missed pickup window, a tracking gap — any of those flags surface in the stuck-load alert with the last activity timestamp and the suggested next action.
Search + filter

Status, direction, week, custom range, full-text

Filter by Open / Booked / In Transit / etc.; by inbound or outbound; by This Week / Next Week / Week 2–5 / custom range. Full-text search across broker, load number, driver, city, and notes. The active-load count carries revenue and avg rate alongside.

How auto-extraction changes the dispatcher workflow

The standard carrier-TMS load entry workflow on a 50-truck fleet takes roughly 4-6 minutes per load — read the rate con, tab to the TMS, type the broker, type the load number, type the rate, type the cities, type the dates, set the equipment, attach the PDF, save, dispatch. Multiply by 200 loads a week and the carrier is buying a third of a dispatcher seat just for data entry. Keelway's auto-extract compresses that to a 30-second review on a populated draft. The recovered capacity goes into customer relationships, problem loads, and everything else the dispatcher should actually be doing.

Frequently asked questions

What load statuses does Keelway track?+
The full lifecycle: Open, Booked, In Transit, Delivered, Invoiced, Closed, Canceled. Each status auto-advances based on real events (tracking ping moves Booked to In Transit, POD upload moves In Transit to Delivered, invoice generation moves Delivered to Invoiced). The status filter on the load list defaults to active loads but every historical state is queryable.
How does AI auto-extraction work?+
Forward a rate confirmation to the connected mailbox (or it arrives there natively). The AI parses broker name, MC number, load number, gross rate, fuel surcharge, pickup and delivery addresses, dates, equipment type, and notes. A draft load is created with the original rate-con PDF attached. Dispatcher opens, reviews, books — usually under 30 seconds per load.
What is a stuck load?+
A load that appears forgotten — no status update in 12+ hours when one should have happened, missed pickup window, no check-call inside the agreed cadence, or a tracking gap. Keelway surfaces stuck loads in a dedicated alert with the most recent activity timestamp and the suggested next action.
Can we search loads by broker, driver, city, or notes?+
Yes — full-text search across broker, load number, driver name, pickup city, delivery city, and notes field. Combined with status, direction (inbound/outbound), and weekly time filters (This Week, Next Week, Week 2–5, custom). Search and filter both work off the same load index.
Can we import existing loads from another TMS?+
Yes. CSV import is on every tier. LoadStop XLSX import is native — paste the LoadStop export and Keelway maps the fields. For other source TMSs (Aljex, McLeod, AscendTMS), the data-migration playbook is part of the enterprise implementation; the import format is documented and self-serve on the standard tier.
Re-keying every rate confirmation?

Auto-extract, review, book. Done.

Talk to sales

Related

AI email triage →

Where the rate cons get extracted from.

Live load tracking →

The in-transit board fed by booked loads from this module.

Lane templates →

Save repeating lanes for one-click instantiation.