Dataq state agency review process

Skill x3fleetsafety/skills/skills/dataq-state-agency-review-process

Use this skill to set proper expectations on how a DataQ challenge is actually reviewed. Covers state vs federal authority, typical timelines, and common review outcomes.From its SKILL.md

Install

npx -y skills add x3fleetsafety/skills --skill dataq-state-agency-review-process

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, 683 tokens by cl100k_base, as published. Nobody here has run it

DataQ State Agency Review Process Explained

DataQ challenges are reviewed by the state agency that issued the inspection — not FMCSA. Understanding this changes how to prepare your filing.

State vs federal authority

State agency (typically DOT or State Police) issues the inspection
State agency reviews the DataQ challenge first
FMCSA can override only in narrow cases (interstate conflicts, federal error)

Typical timeline

Filing submitted: Day 0
State agency review begins: 5-15 days
Decision issued: 30-60 days (often longer for complex cases)
FMCSA database updated: 7-14 days after state decision

Review outcomes

Granted (in full) — violation removed from record
Granted (in part) — some violations removed, some retained
Denied — violation stands
Insufficient evidence — open question; you may re-file with additional evidence

What state agencies look for

Factual error in the inspection
Officer documentation error
Mismatched data (driver, vehicle, location, time)
Inappropriate citation of CFR section
Procedural error (driver not given opportunity to respond)
New evidence not available at time of inspection

What state agencies do NOT consider

"The officer was rude" (style complaints)
"The fine is too high" (penalties separate from inspection record)
"The law is unfair" (carrier disagrees with the regulation)

Preparing for state review

Lead with the specific § citation that's wrong
Reference the FMCSA inspection report fields (Sections A-F)
Include all evidence that supports your position
Don't argue policy — argue facts and procedure

What if you disagree with state decision

Re-file with additional evidence
Request FMCSA review (limited; usually for procedural error by state)
For severe cases, administrative appeal (rare, time-consuming)

Compass support

Pre-builds challenges by inspection ID
Tracks state review timing
Auto-generates audit-quality evidence packages

CFR citations

49 CFR Part 385 Subpart D
FMCSA DataQ User Guide
State Motor Carrier Safety Assistance Program agreements

How Compass surfaces this

Searchable in Compass Ask. Runs against the carrier's actual fleet data when invoked from the relevant tracker. Read-only; no actions without explicit user approval.

Built by X3 Compass

The AI-powered DOT compliance platform for fleets 1–100 power units. Try a 7-day free trial — no credit card required — at https://x3compass.com/?utm_source=skill&utm_medium=github&utm_campaign=dataq-state-agency-review-process

X3 Compass turns these skills into a complete operational platform: driver qualification files, drug & alcohol consortium, MVR pulls, hours-of-service tracking, hazmat shipping, IFTA filing, FMCSA audit prep, and DataQ dispute drafting — all CFR-cited, all in one place.

This skill is published under the X3 Compass open skills initiative. Contributions welcome at https://github.com/x3fleetsafety/skills

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most review quality skills give in 683 tokens

Counted across 1,048 of the 1,783 authors here whose files we hold, read 2026-08-07

Ask questions one at a timein 81 of 1048, across 64 files
Provide a recommended answer for each questionin 73 of 1048, across 50 files
Explore the codebase instead of asking answerable questionsin 66 of 1048, across 42 files
Resolve dependencies between decisions one-by-onein 42 of 1048, across 17 files
Interview the user relentlessly about the planin 38 of 1048, across 13 files
Order findings by severityin 31 of 1048
Resolve each branch of the decision treein 27 of 1048, across 5 files
Run a grilling sessionin 26 of 1048, across 5 files
Update CONTEXT.md immediately when a term is resolvedin 26 of 1048, across 11 files
Propose precise canonical terms for vague languagein 25 of 1048, across 7 files
Create documentation files lazilyin 24 of 1048, across 5 files
Assign severity to every findingin 24 of 1048

Said here and by no other author read

lead with the specific citation that is wrong
reference the FMCSA inspection report fields
include all evidence that supports your position
argue facts and procedure not policy
re-file with additional evidence if denied
request FMCSA review for state procedural error

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.