Platform
The dashboard is not a health page. It answers four questions — what needs attention, what is due, what ran, what is coming — and everything on it is owner-scoped, evidence-backed and one click from the row that caused it.
Overview
Every KPI is counted over the same feeds that render the cards beneath it, so a number on the top row always has a list behind it.
Needs attention
2
Due today
7
Chassis in stock
12
Runs today
64
UP login failed — credential hold 1 h
openimport-tracing · portal
Timed TRAC booking retrying — Joliet has no 40' stock yet
openchassis-reservation · retry until booked
Surfaces
Every module ships the same drill-down: a filterable listing with a stat band, a report with the latest best state, the history of every run, and the CSV, raw portal payload and portal capture behind each row.
Paste any equipment number into the header and land on that container's, chassis's or booking's whole life across every module, newest first, with the requestor named on each row and related equipment linked.
A run shows its progress while it is still on the portals, row by row with a severity per row. The tracing report leads with what a dispatcher needs: next action, the dollars at stake on each unit, a calendar note — and a morning brief that replaces the first portal round of the day.
An operator who thinks a result is wrong flags the row with a category and what it should have been. Admins are emailed, triage it, resolve it with an outcome or forward it to engineering with the redacted evidence attached.
A bell with an unread count, the latest ten and a full page — so 'your blame was resolved' reaches the person in the app they are already in, not only in their mailbox.
Company profile, portal credentials, email config, service keys, users and API clients, the rail-storage, per-diem and overweight rule versions, a system monitor that samples every five minutes and mails a weekly report, logs and a nightly portal-login checker — every one gated on an admin row, not just a session.
Seventeen in-app manuals written in the dispatcher's order of work, with redacted screenshots and, for admins, the module's technical contract reproduced beside them.
Who sees what
An operator sees the requests they made; an admin sees everyone's. A request that is not yours is indistinguishable from one that does not exist — on the page, on every download, on every mutation. The one deliberate exception: a container, chassis or booking is the company's equipment, so its timeline shows every operator every event about it, and ownership decides only whether a row links to its report.
Get started
A thirty-minute walkthrough on your own Chicago lanes and carriers. We will show a live trace on one of your ramps, a scheduled watchlist and the dashboard your team would open every morning.