Log In. Here's What Today Needs.
Open most trucking software at 7 AM and it shows you everything. Every load, every truck, every driver, every expiring document — the whole operation, flat, in no particular order. Somewhere in there are the six things that actually need you before lunch. Finding them is your job.
That's backwards. The system already knows which load is going to be late, which truck is past its PM, which applicant nobody has called in nine days. It just never volunteered any of it.
You shouldn't have to interrogate your own software to find out what today needs.
So we shipped Workflows. Log in and your department's briefing is already open — what's going wrong, what's due, and what's waiting on you, sorted worst-first. There are four so far, one per job, and they don't look alike, because a dispatcher's bad morning and a mechanic's bad morning are not the same morning.
Dispatch: The Day, Then the Problems
The dispatcher's briefing opens with today's schedule — every pickup and delivery on their board, in time order, with the driver and the city. Then it gets to the parts that need a decision:
Drivers needing loads. Who's rolling with nothing booked for today, and separately who's on home time and when they're due back. A driver whose return date is today lands in the needs-freight list automatically, which is exactly the one everybody forgets.
ETA watch. Every active load bucketed — on time, tight, at risk, already late — with the at-risk ones listed worst-first. That's the call you want to make at 8 AM, not the one the broker makes to you at 4 PM.
Stuck past free time. Trucks sitting at a dock right now, past the free time for that broker, ranked by how long they've been there.
Brokers waiting on a reply, delivered loads with paperwork still missing (oldest first — that's your A/R aging before it becomes A/R), and loads waiting on a revised rate con, with the detention minutes and lumper already attached so you know what the revision is even for.
Maintenance: What the Shop Owes Today
The shop's briefing is eleven sections and it opens with active engine fault codes coming off the trucks. Then PM services — overdue first, then anything inside five thousand miles, then units with no PM baseline at all, because a truck nobody ever set a baseline for will otherwise never appear on a due list. That last one is the quiet killer.
After that: annual DOT inspections coming due, the weekly pre-trip cadence (never inspected, overdue, escalated, or requested by the office and still not done), open repair cases, maintenance requests drivers filed from their phones, purchase orders, vendor invoices waiting to be triaged, claims whose unit status doesn't match, and unit paperwork heading for expiry.
The last section is the one we're quietly proud of: odometer freshness. If a truck's mileage feed has gone stale, its PM math can't be trusted — so instead of silently showing a wrong due date, the briefing tells you the number itself is old.
Safety: The Regulatory Clock
Safety's briefing is built around things that have deadlines attached by law.
Post-accident testing leads it, because that clock is measured in hours, not days — alcohol at eight, drugs at thirty-two, per §382.303. Every open accident claim sits in one of a few states: nobody has decided yet whether testing was required, testing is required and hasn't happened, or the driver refused. The briefing chases all three, and once the drug window is blown it says so plainly, because at that point the rule wants a documented explanation instead.
Then: new roadside inspections with no DataQ decision yet, new crashes not yet linked to a claim, unacknowledged license-monitoring alerts, the random testing and SAP queue, employment verifications, MVR risk flags, and CDLIS prior-license hits.
For driver and unit paperwork it deliberately doesn't list every missing document — it counts the drivers and units needing attention and links straight into the compliance page's own filters. A briefing should tell you where to go, not try to become the page.
Recruiting: Nobody Falls Through
Recruiting's briefing exists because leads die of neglect more than rejection. It surfaces forgotten leads in two flavors — applicants who were never contacted at all, and ones who were contacted and then went quiet past your stale threshold.
One detail worth calling out: the "last contact" clock counts actual outreach — a call, a text, a logged conversation. It does not reset when a document gets uploaded. A lead who sent in their MVR last Tuesday but hasn't heard a human voice in two weeks is still a forgotten lead, and the briefing says so.
Alongside that: promised callbacks, missing documents, third-party results still pending, applicants ready to onboard, follow-ups you parked, orientations this week, and leads that look misfiled. Recruiters see their own pipeline; managers see everybody's.
The Details That Decide Whether Anyone Reads It
A daily popup is an easy thing to build and a very easy thing to build badly. What made the difference here was smaller than the feature list.
It's your day, not the server's. The briefing is built against the local date in your browser. A dispatcher in Pacific time opening the app at 6 PM is not looking at tomorrow's schedule.
It opens once, and then it's yours. First login of the day it's already open, greeting you by name. Dismiss it and it stays dismissed — but the header icon reopens it any time, with live data, and reopening it by hand never counts as dismissing it. Check it four times a day if you want.
It's a to-do list, not a report. Every section is capped. Nobody triages a hundred rows before coffee, so each list shows the worst ones and tells you the true total.
Every line is a button. Open the load, put the driver on home time, jump to the claim. The briefing isn't a screen you read and then navigate away from — most of it you can act on without leaving.
Departments are the default, not the rule. Dispatchers get dispatch, mechanics get maintenance, and so on — but any briefing can be assigned to any individual from Admin Panel → Workflows. Your safety director who also runs the shop gets both. On multi-branch fleets, restricted users only ever see their own branches' units.
What We Won't Say
This isn't a robot deciding what matters. It's your data, run through rules we wrote down and you can tune — thresholds, who gets what, which department is on the hook. It can only surface what you already track: a truck with no PM baseline shows up as exactly that, not as a guess.
And dismissing a briefing doesn't fix anything. It's a list, not a fairy. Somebody still has to call the broker.
What it does end is the part where you open the software and it just sits there, full of everything, telling you nothing. Four briefings are live now, and the catalog is built to grow. If you want to watch one open, there's a short walkthrough.