Donna’s question · Can you prove it?
Start with the compliance
job in front of you.
Route first.
The Compliance Desk is the hub. It does not decide which regulations apply to your operation — that work happens inside the Compliance Toolkit, where applicability and the evidence check run together.
The Toolkit determines what applies to your operation, then checks the proof that belongs to those requirements. Audit notices, roadside questions, IFTA math, and insurance terms do not all belong in one giant checklist.
If the requirement applies, the record has to prove it.
Doing the work and being able to demonstrate the work are not the same thing. Establish applicability first. Then identify the supporting record, verify whether that proof is current, and preserve Unknown when the evidence is not available. A requirement that does not apply is not a deficiency, and an old document does not become current simply because it exists.
Put the question in the right place.
These routes organize where to go next. They do not determine whether a regulation applies to your operation. Compliance owns the proof trail; fuel math, insurance terms, and other department-owned decisions stay with their own engines.
I need to understand an audit or organize the records behind it.
Start with the audit-readiness material when the immediate job is understanding what FMCSA reviews and how the supporting records fit together.
I received an audit notice, filing request, invoice, or official-looking message.
Do not treat the appearance of a notice as proof of what you owe or what applies. Verify the sender, claimed requirement, deadline, and responsible official source before paying or submitting sensitive information.
My question is roadside, inspection, ELD, HOS, or driver proof.
Use the inspection route when the immediate question is what needs to be current, available, and defensible before a roadside inspection or records check.
The paperwork question is really fuel math or an insurance term.
Compliance may care whether a record exists. It does not take ownership of another Desk’s calculation or written-term interpretation.
Diagnosis and the evidence check belong in the same working record.
The Toolkit begins with Your Operation so requirements can be tested for applicability before they enter the requirement ledger. Only then does the evidence check ask what proof exists, whether it is current, and what remains Unknown.
Does this requirement belong in your record?
Your Operation establishes scope before anything is called missing.
What proves the requirement was addressed?
Keep an actual record or official source separate from an estimate, memory, or assumption.
Is the supporting proof still current?
Freshness belongs to the specific requirement. There is no invented universal expiration date.
What actually needs attention?
Current, stale, conflicting, untouched, Not Applicable, and Unknown remain different states.
Read the evidence for the question you already have.
Guides explain individual requirements, proof questions, and preparation issues. They do not determine the complete set of requirements that applies to a specific operation and they do not replace the working compliance review.
New Entrant Safety Audit: What FMCSA Actually Checks
Use this when the immediate question is what an audit examines and how the records supporting the carrier’s safety systems fit together.
DOT Inspection Readiness: What Every Owner-Operator Should Know Before the Officer Walks Up
Use this when the question is inspection preparation, driver documents, logs, ELD readiness, vehicle inspection, or what happens at the scale.
FMCSA Notice or Private Solicitation? How to Verify It Before You Pay
Use this when a letter, email, or notice claims to be from FMCSA or a federal register and the immediate question is whether it’s real before any payment or response.
Four pages. One clean sequence.
The Desk routes. The Toolkit determines applicability and checks the proof. The Decision Center compares DIY against outside help only when the record supports a reason to compare. Providers come last.
Compliance Desk
You are here
Orient the operator, explain the Compliance system, and route the question without deciding applicability here.
Compliance Toolkit
Your Operation establishes applicability. The same tool then checks the requirement ledger for evidence, freshness, contradictions, Untouched items, and Unknowns.
Compliance Decision Center
Compare DIY against paid or assisted options only after the Toolkit establishes the requirement, the evidence condition, and the operator’s actual unresolved need.
Compliance Providers
Review provider options without treating vendor availability as evidence that the operator needs to buy anything.
What this Desk will not do.
Proof should reduce exposure, not create another one. HaulSmarterHQ does not need your SSN or driver’s-license number to organize your Compliance working record — the system runs on proof status, evidence, dates, applicability, and verification, not unnecessary sensitive identifiers.
Requirements can depend on the operation, vehicle, driver, authority, jurisdiction, date, and controlling source. Verify current requirements with the responsible authority. Legal disputes, insurance coverage questions, and private written-term interpretation belong with the appropriate qualified professional.