00Platform
Four surfaces. One question: which load do I touch next?
Dwell is not a dashboard. It is a queue, a set of distributions, a scorecard and a ledger — each built for a decision somebody makes on a specific day of the week.
- Deploys
- Read-only, alongside your TMS
- Time to live
- 3 weeks, typical
- Latency
- 18 sec P95, ping to screen
- Seats
- Unlimited on every plan
01Exception queue
One list, ordered by money, empty when nothing is wrong.
Every load carries its own contractual free time, pulled from the rate confirmation rather than a global default. Rules are written in plain conditions your ops lead can read and change without a ticket. When a load is 30 minutes from crossing, it surfaces — with the facility contact and carrier dispatch line already attached.
Rule · Pre-detention warning
CRIT- WHENload.status = AT_FACILITY
- ANDclock.elapsed > free_time − 00:30
- ANDfacility.median_dwell > 02:00
- THENraise CRITICAL · notify desk + carrier dispatch
Matched 214 loads in the last 30 days · 9 escalated to detention
02Facility intelligence
Some doors are slow every single week. Now you can prove it.
Dwell keeps a distribution, not an average, for every facility you touch. Averages hide the tail; the tail is where detention lives. Walk into a rate negotiation with 214 loads showing that 46% of them cross free time at one door, and the conversation stops being anecdotal.
Joliet DC-4 · dwell distribution
n = 21446% of loads cross the 2h free-time line at this door. Contract says 2h.
03Carrier scorecards
Separate the carriers who are late from the ones your facilities delayed.
A carrier's on-time number is meaningless if half their misses were caused by a consignee holding them at the dock. Dwell attributes each delay to the party that caused it, so quarterly reviews stop being a blame exchange and start being a lane-by-lane decision.
MRDN
Meridian Freight Systems
1,240 power units · 41 lanes with you · reviewed quarterly
- On-time pickup
- 71%−9
- On-time delivery
- 88%+2
- Median dwell caused
- 2:48+0:22
- Tender acceptance
- 94%+1
- Disputed detention
- 3 of 11—
04Detention ledger
Timestamps, not recollections.
Every accessorial charge carries the evidence that produced it: geofence entry, gate confirmation, the exact minute free time expired, departure. Approve, dispute or bill back from the same row. The export is the document AP asks for anyway.
INV-2261 · evidence
$1,875.00- 06:12:04ELDGeofence entry · Joliet DC-4
- 06:18:31YARD APIGate-in confirmed
- 08:12:04DWELLFree time expired (2:00 per rate con)
- 11:52:47ELDDeparture · geofence exit
Exported as a PDF the carrier's AP department accepts without a call.
05Data in
We read. We don't rearrange.
Dwell sits beside the systems you already pay for. If a source isn't listed, a nightly SFTP drop of load and stop records is enough to run the whole product.
TMS
- McLeod
- MercuryGate
- Blue Yonder
- Oracle OTM
- Turvo
- Custom / SQL
Telematics
- Samsara
- Motive
- Geotab
- Platform Science
- Omnitracs
Facility
- Opendock
- C3 Reservations
- Terminal49
- Yard API
- Manual CSV
Standards
- EDI 214
- EDI 990
- REST webhook
- SFTP drop
- MacroPoint
The boring answers, up front.
Procurement is going to ask. Here it is before the call, so the call can be about freight.
- Access
- Read-only credentials. Dwell never writes to your TMS.
- Residency
- US or EU region, chosen at provisioning. Data does not cross.
- Retention
- Load telemetry 24 months, then aggregate-only. Deletion on request.
- Audit
- SOC 2 Type II, annual. Penetration test report on request under NDA.
- Isolation
- Per-tenant encryption keys. No shared query path between customers.
- Availability
- 99.9% contractual. Status and incident history published.
07Next step
Bring one bad week of loads. We'll show you what it cost.
A 30-minute walkthrough against your own data. No slides, no sandbox with invented shipments — your lanes, your facilities, your free-time terms.
- Format
- 30 min, screen share
- Prep needed
- One CSV of loads
- Sales pressure
- None