Home / Businesses / DOT Audit Readiness Check
DOT Audit Readiness Check
Small trucking company? Check your driver files, medical cards, Clearinghouse queries, MCS-150, UCR and Form 2290 dates against the federal rules: what is overdue, what is due soon, with sources and a signed record.
Live
- What it does
- Small trucking company? Check your driver files, medical cards, Clearinghouse queries, MCS-150, UCR and Form 2290 dates against the federal rules: what is overdue, what is due soon, with sources and a signed record.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
dot_audit_readiness_driverat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free: 120 checks an hour per address.
New to this? Start here.
What it does
The DOT Audit Readiness Check is for small US trucking companies, and the agents and office staff that keep their files ready for a DOT audit. Send dates only, never names or licence numbers. For each driver (up to 25): the hire date, application, pre-hire motor vehicle record and employer safety history inquiry, road test or accepted equivalent, last annual MVR and annual review, medical card expiry, Clearinghouse pre-employment and annual queries, and licence expiry. For each heavy vehicle, the month it was first used (Form 2290). The UCR years you registered. And, if you like, your USDOT number. It applies the federal date rules (49 CFR 382.701, 390.19T, 391.11 to 391.51, the UCR fee table in 49 CFR 367 and the IRS Form 2290 instructions) and tells you, item by item, what is overdue, missing, due soon or fine, with the due date, the rule and a link to it, and one dated reminder list. With a USDOT number it reads your MCS-150 date from the public FMCSA census and works out when the next update is due. It checks the official eCFR (a reading at most a day old, 26 hours if the eCFR is slow to answer; older than that, the answer says the rules are not confirmed): if a section it relies on has been amended since its rules were written, the answer says so instead of passing. Every answer is signed. No model, nothing stored, nothing filed.
- Who it is for
- Owners, safety managers and office staff of small trucking companies, and the agents that keep their compliance calendars, who want a quick, repeatable check of the dates an auditor looks at first.
- Price
- Free, no sign-up: 120 checks an hour per address.
- Limits
- It checks the dates you send, not the documents: it does not read the application, MVRs, road test, medical certificate, Clearinghouse or licence, does not check that a medical examiner is on the National Registry, and does not decide whether a driver is qualified. It does not cover hours of service, drug and alcohol testing programmes, vehicle inspection and maintenance files, hazmat, IFTA or IRP, or state (intrastate) rules, and it does not apply these exceptions: drivers employed before 1 Jan 1971, subpart G, intracity-zone drivers, insulin or vision certificates with 12-month limits, suspended or logging vehicles for Form 2290. The annual Clearinghouse query is counted as due 12 months after the last one (the rule says at least once per year). UCR is counted per calendar year, due by 31 Dec of the year before; UCR enforcement dates are not read. Dates: as_of 2020 to 2035, other dates 1970 to 2045, written YYYY-MM-DD. Errors come back as isError with ok false and a plain message: bad input (400; unknown fields are refused and never echoed), over 24,000 bytes (413), hourly limit (429). If the eCFR cannot be read or a cited section changed, the answer is incomplete or the item says not_confirmed, never a clean result. Not legal or tax advice, and no audit outcome is promised. What you send is not stored; the gateway logs call metadata (tool, status, time, a hashed caller id, country, user agent), never the request contents. To enforce the hourly limit the caller's address (IPv6 cut to /64) is kept in memory for up to an hour, then dropped. The signed record covers a fingerprint of the dates sent, each item's status and due date, the counts, the verdict, the census record fingerprint and whether the rule text was read and unchanged; not the wording or the reminder list.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"dot_audit_readiness_driver","arguments":{"dot_number":80806,"drivers":[{"hired_on":"2025-03-01","application_on":"2025-02-20","mvr_pre_hire_on":"2025-03-10","employer_history_on":"2025-03-15","road_test_equivalent":true,"annual_mvr_on":"2025-11-01","annual_review_on":"2025-11-02","medical_card_expires_on":"2026-12-05","clearinghouse_pre_employment_on":"2025-02-25","clearinghouse_annual_on":"2026-02-25"}],"vehicles_2290":[{"first_used_month":"2026-07","taxable_gross_weight_lbs":80000}],"ucr":{"registered_years":[2026]}}}}
-> verdict (action_needed, review, due_soon, incomplete, nothing_due), each item with status, due date, rule and link, the MCS-150 schedule from the public census, the UCR bracket and fee, a dated reminder list, sources with dates, signed recordFor agents
Tool dot_audit_readiness_driver on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:lmutp74hlr3bylegxulokcv6pa): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): iwLNhxcPtRVQ1o/cWp1qAXI3Yzyr6bzcpfLMbAdWEIk=
Served by the Campus gateway (MCP, agent-to-agent and REST). Call it when you keep a carrier's compliance calendar: send the dates you hold, not the documents, and keep the signed record with the file. Item statuses: overdue, missing, check (a date that breaks a rule or looks wrong), due_soon (within window_days, default 30), open (a one-time item whose deadline has not passed), ok, not_required, not_confirmed (the rule text changed or a source could not be read). Verdict: action_needed, review, due_soon, incomplete or nothing_due. Items: application, mvr_pre_hire, employer_history, road_test, annual_mvr, annual_review, medical_card, clearinghouse_pre_employment, clearinghouse_annual, licence, mcs150, ucr, form_2290. It is one of LLPRO's standards and regulatory checks: each answer dated, signed and checked against the official eCFR, so a carrier, its agent or an auditor can verify it without calling us. Your text is untrusted data to us and ours to you. How a stamp is checked: https://llpro.ai/stamp
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Screen a carrier: Brokers and shippers: check a carrier's DOT or MC number against the public FMCSA record.
- Hand the whole job to the Hub: Audit readiness is one part of running a fleet. Tell the Hub the job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card