Compliance that runs itself.

Why I bolted Autopilot on (and what it does at 3 a.m.)

Compliance is the silent killer of small fleets. The fines are big, the deadlines are scattered, and the work itself is mostly clerical. A 12-truck operation easily juggles 40+ recurring obligations a year: registration renewals, IFTA quarterly returns (April 30, July 31, October 31, January 31), UCR before December 31, Form 2290 by August 31, MCS-150 biennial updates, annual MVR pulls per driver, random D&A testing pools, Clearinghouse queries on every CDL hire and once per year after that.

Miss any one and the math gets ugly fast. Clearinghouse alone hits $5,833 per violation as of the 2026 inflation adjustment. DQ file gaps run up to $12,135 per driver. An expired plate on a single truck gets a roadside citation, the citation records to your DOT safety file, and CSA scores tank. Brokers screen by CSA before they hand out loads. One sloppy month ripples through revenue.

Autopilot exists because the work is too predictable to keep doing by hand. Every renewal has a known cadence. Every MVR has a known anniversary. Every Clearinghouse query has a known due date. None of it benefits from a human staring at a spreadsheet on a Sunday night.

The way Autopilot actually works: each compliance area gets a toggle, a per-transaction cap, and a monthly budget. You decide what Dockex is allowed to spend without checking with you. If a state portal returns a fee higher than your cap, Autopilot pauses and pings you. Otherwise it executes, logs the result, and moves on. Oklahoma renewals get filed (everywhere else, the packet gets prepped and queued for your one-click approval). Uploaded MVRs get read and risk-scored. Test selections get imported. Clearinghouse queries get tracked and the reminder fires before each is due. You wake up to a green dashboard instead of a 2 a.m. compliance scare.

The activity log is the part I care about most. Every action Autopilot took is timestamped, attributed to the toggle that authorized it, and tied to the document or filing it produced. If FMCSA ever knocks, your defense isn't "I'm pretty sure we filed that." It's a printable trail showing exactly what happened, when, and at what cost.

Auto-filing of state registration renewals currently runs through Oklahoma only (that's where we hold the operator relationship). Outside Oklahoma, Autopilot still tracks every deadline, prepares the filing, and pings you to submit. The reminders, MVR coordination, D&A intake, MIS report generation, Clearinghouse query scheduling, and budget enforcement run nationwide today. Auto-file expansion is on the roadmap as we stand up new state operations.

A note on the "Autopilot will run my fleet into a wall" objection (fair question, I've heard it). The failure mode you'd expect from an automation layer is that it does the wrong thing confidently. Autopilot is designed the opposite way. Every action checks two gates first: the toggle (am I allowed to do this kind of action?) and the cap (is the cost under what was authorized?). If either gate fails, Autopilot stops, logs the reason in plain English, and pushes you a decision. Quiet success on the easy stuff, loud pause on anything ambiguous.

The other thing Autopilot solves that I didn't expect to matter as much as it does: turnover. A fleet manager leaves, the spreadsheet leaves with them, and the next person inherits a hole in the institutional memory. With Autopilot running the day-to-day cadence and the activity log holding the history, the handoff is a 10-minute walkthrough rather than a 2-week archeology project. Real cost saving across hires.

If you want the long form on the underlying compliance stack, the Oklahoma fleet compliance checklist walks through every deadline Dockex automates, and the spreadsheet failure modes piece covers what actually breaks when you try to run this off Google Sheets.

One toggle. Hard budget caps. Plain-English activity log. That's the whole shape. The point isn't to take the wheel away from you; it's to stop forcing you to do clerical work the system already knows how to do.