Carrier integrity · operations console

VetGate Console Walkthrough

Every screen an operator uses to decide whether a motor carrier may be handed a load — and every point at which the system refuses to let that happen on anything but a checked record.

20screens

3:14runtime

9 Sep 2026captured live

VetGate console, Overview: VetGate screens the carriers a broker is about to hand freight to — and refuses dispatch when the record does

VetGate console, Overview: Every carrier sits in one of four integrity tiers: cleared for commercial dispatch, cleared for federal work,

VetGate console, Carrier vetting: Vetting starts from an MC or DOT number. The engine resolves the identity first — the same docket number can m

VetGate console, Dispatch gates: The protection gates are two-person controls. Turning one off needs a second operator to approve it, and every

VetGate console, Email intake: Carrier packets arrive by email and are read automatically. Nothing an inbox produces is treated as proof on i

VetGate console, Carrier monitoring: Approval is not the end of it. Monitoring runs continuously, and a carrier that goes dispatchable here but unw

VetGate console, Review holds: Any operator can stop a carrier; only an admin can release one — and releasing is per-hold, never all of them

VetGate console, Assessment disposition: Findings raised about a carrier have to be answered before a load moves. Each is satisfied or waived by a seco

VetGate console, Carrier review: This is where a human signs off. The engine can fail a carrier on its own; it can never approve one — that is

VetGate console, Carrier review: A PASS needs at least a sentence of evidence. Three of the seven steps are derived by the engine and cannot be

VetGate console, Readiness roster: For disaster work the bar is higher: federal registration, the state tier that contract demands, and a complet

VetGate console, Document approvals: A document a driver uploads satisfies nothing until a person approves it. Only an approved document counts tow

VetGate console, Document approvals: A decision already taken is not a button. An approved document offers only the reverse — and the database refu

VetGate console, Reports: Operating reports read the same record the decisions were made against — not a separate analytics copy that ca

VetGate console, Agent health: Every automated agent reports its own liveness. A stale data source raises an alert — a quiet feed is evidence

VetGate console, Integrations: Vetting results push into the systems a broker already runs — Teams, load boards, or any endpoint by webhook.

VetGate console, Customers & access: Customers are invited, never self-registered. The API key is shown once and never again — the key is the crede

VetGate console, Settings: Administrative controls, including the disaster-portal recovery path — which runs through the company's own id

01 / 20 Overview

0:00 / 3:14

Redacted

Recorded against the live production console. Every carrier name, MC and DOT number, email address, phone number, filename and API key on screen is a stand-in — substituted at render time by a redaction layer, with the capture refusing to take any frame that still carried a real identifier. Tier counts, timestamps, agent runs and queue depths are real.

What is on screen

20 beats · jump to any

What is on screen

Overview

Carrier vetting

Dispatch gates

Email intake

Carrier monitoring

Review holds

Assessment disposition

Carrier review

Readiness roster

Document approvals

Reports

Agent health

Integrations

Customers & access

Settings

Carrier profile