Abhinav Sharma
All work

Federal trucking regulations, rebuilt as something a driver can actually search.

ClienteRegs, LLC
RoleProduct engineer
Year2025
Duration5 months
TypeScriptReactReact NativePostgreSQLeCFR APIStripe
18CFR parts, boolean-searchable
4Sources unified in one search
3Platforms — web, iOS, Android

The problem

A motor carrier has a legal duty under 49 CFR 390.3(e) to ensure every driver is instructed on and knowledgeable of the regulations, which in practice has meant posting a printed rulebook to each cab. Printed books are stale the moment a rule changes, unsearchable at a roadside inspection, and produce no evidence that anyone read them. The underlying text is also not one document — it is eighteen CFR parts, plus FMCSA guidance, plus PHMSA interpretations, each published separately and cross-referencing the others.

The approach

Regulation text syncs from eCFR rather than being copied, so currency is a property of the pipeline instead of an editorial task someone has to remember. Full-text search spans all four bodies at once — regulation text, FMCSA guidance, PHMSA interpretations and Trucksafe educational material — because a safety manager looking up a rule needs the interpretation attached to it, not a separate hunt. Annotations sync across web and mobile so a note made at a desk is there at a roadside. Driver invitations produce an acknowledgement receipt, which turns the legal duty into something a carrier can evidence.

The outcome

Fleets can push current regulations to in-cab devices instead of mailing books, and hold a record that each driver received them. The same content is searchable on web, iOS and Android.

What mattered

Currency as a pipeline property

Syncing from eCFR rather than copying means the text is current because of how it is built, not because someone remembered to update it.

One search, four bodies of text

Regulation, FMCSA guidance, PHMSA interpretations and training material return together — a rule without its interpretation is half an answer.

Evidence, not just access

Driver acknowledgement receipts turn a 390.3(e) obligation into something a carrier can actually produce at audit.