How the app is organized

The sidebar is organized into groups — here’s the map:

Roles: Brokers create and manage verifications and loads. Dispatchers work the dispatch side. Workspace owners and admins additionally manage the team and settings. Give each person the least role that covers their job — you can change roles later from Settings → Team.

Click New Verification in the sidebar. The wizard has three steps:

Step 1 — Carrier lookup. Enter either the MC number or the DOT number (not both) and click “Search FMCSA + carrier intelligence”. The system pulls the carrier’s federal registration and industry profile, then shows a Confirm carrier profile panel so you can make sure the right carrier came back before continuing. Two data cards appear:

• FMCSA — legal name, phone, registered email, physical address, “Allowed to operate”, “Out of service”.
• Carrier intelligence — packet status, risk indicators, phone count, registered contacts and emails, and the carrier’s known phone numbers.

Step 2 — Contact & load details. Enter the owner’s contact info (we always call the owner and send the code to the FMCSA-registered number, never to the phone you type — that’s deliberate, it anchors the verification to the registered identity), the dispatcher who contacted you, and the load: commodity type, declared value (required), weight, origin and destination, pickup/delivery dates, and flags for hazmat, temperature control, and high value.

Step 3 — Review & submit. A line-by-line review of everything you entered. Submit to start the verification, or Save draft to finish later. If you navigate away mid-wizard, the app autosaves and offers Resume / Discard next time.

After submission the verification detail page shows a workflow tracker (“{n} of 7 complete”). The steps, in order:

Carriers never need a Happy Tactic account: the owner, dispatcher, and driver each get a secure link (valid 24 hours, locked once submitted). From the People & links tab you can Send fresh link or Re-issue a link (up to 2 re-issues), and see SMS delivery status.

Every verification produces a 0–100 Trust score — higher is safer — always shown with its band: 70 or higher is Low risk, 31–69 Medium risk, and 30 or below is High risk (a 30 is red). While the carrier is still answering, the score is provisional and the verification reads In progress. Once every step is in, it gets exactly one verdict — the same words on the list, the detail page, the decision email and the evidence PDF:

When a blocking rule fires, the decision panel lists exactly which rules triggered — no black-box rejections. For a Needs your review verification, the Approve — OK to book / Reject — Do not book buttons let you make the final call once the workflow steps are complete, and the “What to fix before approving” panel lists remediation items.

Open any verification to see six tabs:

The All Verifications list has filter pills (All / In progress / Needs your review / OK to book / Do not book / Cancelled / Draft), search by carrier, MC or DOT, a minimum-Trust-score filter, CSV export, and bulk Approve All / Reject All for selected rows. Each row shows one verdict and its Trust score (“78 · Low risk”), the owner check (confirmed ✓), the insurance-expiring warning and when it was last updated.

Every verification compiles its evidence — data snapshots, confirmations, documents, risk breakdown, audit trail — into a branded PDF. From the detail page header: Download PDF (Download report once decided) saves it, Email report sends it. Keep it with the load file; it’s your proof of due diligence.

Once a verification is decided (approved or rejected), Download evidence PDF adds every photo and document collected — driver license, selfies with the face-match result, owner ID, truck and insurance documents — each labelled and timestamped. When the verification is decided we also email it to the broker who started it (attached, or as a download link when it is over 7 MB) — an admin can turn that off under Admin Settings. The photos in a verification can be deleted from 90 days after the decision, so this PDF is your permanent copy of them; the verification record itself (decision, score, findings, match results) stays in your account for as long as it is open. Every download is recorded in your company’s audit log.

Loads → + New load. The wizard starts with Select a customer — there’s no form until you pick who you’re hauling for. Once selected, a credit-exposure header stays pinned: open A/R, credit limit, and what’s available. If booking would put the customer over their limit, the system warns or blocks depending on your workspace’s credit-gate setting.

Then two steps:

• Load details & rate — mode, equipment type, spot vs. contract pricing, cargo value, hazmat; the customer rate as a flat rate or Unit × Qty × Rate (per CWT, mile, pallet, ton, …); accessorial charges (detention, lumper, layover, fuel surcharge); and reference numbers (PO #, BOL #, Pickup #, Delivery #, Customer ref).
• Stops & items — pickups, deliveries, waypoints, and drop-trailer stops, plus the items on board.

Create load books it in Draft status.

Loads is the operational spreadsheet: 20+ columns (Load #, Status, Customer, Carrier, PU/DO cities and dates, Equipment, Weight, Cust Rate, Carrier Rate, Margin, PO #, BOL #, Broker/Dispatcher, …), every one sortable. Quick-search by Anything / Load # / BOL # / PO-Ref #; a status rail with live counts; deep filters for lane, equipment, carrier MC/DOT, and pickup windows; and a My Loads toggle.

• Saved views — save any combination of filters, columns, and sorting as a named view (“Make this view my default”), e.g. an accounting view or a my-team view.
• Bulk status changes — select rows, pick “Change status to…” and Apply. Each load is validated individually; the result banner shows changed / skipped / failed counts.

Open any load for everything on one page, with a sticky jump-nav: Details · Documents · Customer · Carrier · Accounting · Check Calls · Tasks & Notes · Messages · Activity. You never hunt through five screens to answer “what’s going on with this load?” Status changes from here (and everywhere else) run through the same validated lifecycle — an illegal jump is simply not offered.

Dispatch Board shows loads as drag-and-drop cards in six columns: Pending → Available → Covered → Dispatched → Pickup / In Transit → Delivery / Delivered. Drag a card to move it through the lifecycle; updates appear live for everyone, no refreshing. A map view toggle shows the same loads geographically.

Offers start from the load: open the load’s Carrier section. While no carrier is attached, the Find carriers panel ranks candidate carriers by lane history, capacity, and rating — verified carriers first — each with a button to send them the offer.

The carrier gets the offer by email with a link — no sign-in — and accepts, declines or counters it. Once booked they receive the Rate Confirmation: the actual PDF, already signed for your company, which they sign on the page (with e-sign consent); both sides get the signed copy. Every send and signature is stamped into the load’s activity log automatically. Offer states: Awaiting response, Accepted, Declined, Expired, Counter-offered, Withdrawn — manage them per load or across the workspace on Offers to carriers (accept counters, withdraw, re-send). The Carrier section also mints a customer tracking link (package-tracking-style page, no account needed) and can text the driver a check-in link for location, status, and a POD photo at delivery.

Delivered loads don’t go straight to invoicing — they queue in Invoice audit, which checks each load against that customer’s paperwork rules: POD present, BOL, required reference numbers, carrier invoice in and matching the rate con. Clean loads are approved in bulk; problem loads show exactly what’s missing. Approved loads are batched per customer — one email, one invoice PDF, the right paperwork attached. Carrier payments (pay terms, quick-pay, advances, factoring) are tracked per load under Accounting, and every load shows its live profit. Exceptions — Missed pickup, TONU, Ops hold, Accounting hold, Claim filed — are real statuses with their own colors, so a troubled load never hides in a normal list.