CSA
About

Who builds VioCodes — and where the data comes from

VioCodes is built and maintained by one working safety manager, not a content farm. This page explains the author, the dataset, and exactly how the tools work.

The author

I'm Yurii Chornous — a trucking safety manager who builds software for the problems I deal with every day. Running safety for a fleet means living inside CSA scores, roadside inspections, and DataQs challenges, and I got tired of digging through PDFs to answer questions a search box should handle. So I built the tools I wanted to exist, and I publish them free.

VioCodes is one of those tools. Another is Safety Hub, a fleet safety management platform. You can find me on LinkedIn or see everything I've shipped on my portfolio.

Where the violation data comes from

The core dataset is built from the FMCSA SMS Methodology, Appendix A (v3.20) — the official table that maps every roadside-inspection violation code to its BASIC category, severity weight, and out-of-service indicator. That publication is the source of truth for every code page on this site.

On top of that baseline, users can submit codes they've seen on real inspection reports that aren't in the published table yet. Community submissions are reviewed before publishing — nothing goes live automatically. When FMCSA revises the methodology, the dataset gets updated against the new publication.

Carrier data

Carrier profiles and inspection details are pulled live from public FMCSA records at the time you look them up — VioCodes doesn't maintain its own shadow copy of carrier safety data. What you see reflects what the public FMCSA systems report, with the same lag those systems have.

How the DataQs drafter works

The DataQs drafter takes your description of the violation and any supporting documents, and uses an AI model to draft a Request for Data Review that cites the relevant 49 CFR sections. The draft then goes through a self-review pass that checks the argument and citations before you see it.

To be clear about the limits: the output is a starting point, not a finished filing. AI drafts can get facts or citations wrong, and only you know your records. A human must review and verify every draft against the inspection report and the actual regulation text before submitting it to DataQs. The DataQs guide covers what makes a challenge actually win.

Independence

VioCodes is not affiliated with FMCSA or any government agency, carries no ads, and doesn't sell data. See the terms of use and privacy policy for the details.