Loads, dispatch, carriers, documents, team messaging and billing — one workspace, one record of truth, from the moment a load is booked to the moment it is paid.
| Load | Customer | Status | Rate |
|---|---|---|---|
LC100341 Fargo, ND → Omaha, NE | Northline Mfg | Dispatched | $2,400 |
LC100342 Des Moines, IA → Chicago, IL | Prairie Foods | In transit | $1,850 |
LC100339 Denver, CO → Salt Lake City, UT | Alto Metals | POD received | $3,120 |
LC100337 Omaha, NE → Kansas City, MO | Northline Mfg | Invoiced | $1,675 |
LC100344 Minneapolis, MN → Milwaukee, WI | Harbor Goods | Booked | $2,050 |
Assigned to Ridgeline Carriers · rate confirmation sent.
Casey: POD is in — moving it to billing now.
POD-LC100339.pdf opened, checked, attached to the load.
INV-LC100339 generated from the POD — $3,120.
Every load moves through the same five stages. Each system acts at the stage where it belongs, on the same record — so nothing is re-keyed and nothing is lost between them.
Customer, lane, rate and carrier on one record every later stage reads from.
Carrier assigned against live compliance, rate confirmation generated and sent.
The thread about a load references the load — not a screenshot in another app.
The POD opens in the PDF Workspace and files itself against the load it belongs to.
POD-gated invoicing off the same record, and your customer sees it in their portal.
Four groups, all shipped and in use today. Nothing on this site is a preview.
Most brokerages run dispatch in one app and the record of it in another, so the reason behind a decision lives somewhere nobody can find it later. Connect is inside the workspace, and a thread can reference the freight it is about.
One product, three jobs — and the roles are real: what each person sees is enforced on the server, not hidden in the interface.
Every claim below is implemented in the shipped product. No certifications, compliance standards or uptime figures are claimed, because none have been audited.
Every record is scoped to your workspace, and the isolation is regression-tested — cross-tenant access is a failing build.
Duplicate invoices, duplicate payments and replayed bulk operations are refused by database constraints, not just by screens.
TOTP with recovery codes, a first-class step of sign-in.
Single active session, lockout after failed attempts, rate-limited authentication.
Sign-ins, failures, lockouts and settings changes are all recorded.
Integration secrets encrypted with versioned keys, never plaintext.