Skip to main content
TruckCodex
Hubs

Data Methodology & Principles

How TruckCodex sources, processes, and presents trucking industry data. Transparency and provenance are core to every page.

Data Sourcing

TruckCodex uses official government datasets as primary sources. Carrier census and safety data come from the Federal Motor Carrier Safety Administration (FMCSA). Recall, complaint, and investigation records come from the National Highway Traffic Safety Administration (NHTSA). Diesel fuel prices come from the Energy Information Administration (EIA). Derived overlays (for example the RMIS broker carrier-setup harvest) are labeled as derived on /meta/sources/ and are not substitutes for FMCSA records. No scraped forums, crowdsourced tips, or paid reseller feeds are used as primary sources. Full registry: /meta/sources/.

Provenance

Every fact displayed on TruckCodex links back to its upstream source. Each data table shows a source identifier and an as-of date indicating when the data was last refreshed. This lets users verify any claim against the original government record.

Update Cadence & Freshness

  • Carrier census: daily delta sync plus weekly full refresh from FMCSA SAFER.
  • Recalls and complaints: daily sync from NHTSA ODI flat files.
  • Diesel prices: weekly from EIA Weekly Petroleum Status Report.
  • Inspections: daily from the FMCSA SMS database (data is 24 hours old at minimum).
  • Live import timestamps: /meta/freshness/ (cron runs and last-success per source).

Compliance Status Resolution

Carrier pages resolve operating status, out-of-service, authority, insurance/BIPD signal, FMCSA safety rating, and booking-verdict inputs through one shared resolveCarrierStatus() object. Status chips, FAQ answers, explainers, and book/don't-book copy must read from that object so they cannot contradict each other.

Safety Grading

  • FMCSA safety rating labels (Satisfactory / Conditional / Unsatisfactory / none published) come from the carrier census and are shown as official labels — not TruckCodex grades.
  • Per-carrier compliance grade on USDOT detail pages: expandable card with five components (authority/census, insurance/BIPD, OOS vs same-size peers, FMCSA safety rating, insurance-watch tier). Letter = mean of scored components; NR when fewer than two components resolve — we do not invent grades for thin data.
  • State Safety Report Cards publish a documented composite letter grade (BASIC percentile + OOS + crash components) on /insights/ — a separate geographic ranking surface.
  • Booking verdicts (Clear / Caution / Do not book) remain a separate triage card; the grade decomposes the same underlying signals for evidence, not a second opaque score.

History Tracking

Meaningful field changes are recorded as history-watch events (entity, field, old value, new value, changed_at, source) rather than full daily snapshots. We never physically delete entity rows when upstream sources remove them — rows are status-flagged so historical record remains queryable.

Known Limitations

  • All inspection data has a minimum 24-hour lag from the time of the roadside event.
  • Carrier census contact information (phone, address) may lag behind real-world changes by days or weeks.
  • Inspections conducted under tribal or military jurisdiction are not included in the FMCSA dataset.
  • NHTSA recall data covers only federally reportable safety defects, not voluntary service campaigns.
  • Booking verdicts and insurance-watch tiers are heuristics for due diligence, not legal determinations.
  • The broker carrier-setup overlay is a 2026-08-27 harvest of public RMIS/Wayback pages, not FMCSA. Gates are point-in-time; confirm with the broker.

Entity Resolution

  • Carriers are identified by their USDOT number, which is a unique federal identifier assigned by FMCSA.
  • Vehicles are identified by 17-character VIN (Vehicle Identification Number) decoded via the NHTSA vPIC service.
  • Recalls are identified by NHTSA campaign number, a unique identifier for each safety recall.

Trust Tiers

  • Tier 1 — Official Primary Source: Data taken directly from the issuing agency's authoritative dataset (e.g., FMCSA carrier census, NHTSA recall flat files).
  • Tier 2 — Official Derived/Aggregated: Data computed from official sources (e.g., state rollup counts, inspection rate calculations, resolveCarrierStatus labels).
  • Tier 3 — Third-Party Verified: Data from external providers that has been validated against official records. Currently not used.

Corrections

TruckCodex does not modify source data. Data corrections flow through official government channels. For inspection disputes, carriers use the FMCSA DataQs system. For recall or complaint corrections, contact the NHTSA Office of Defects Investigation (ODI). Display bugs and broken joins: /corrections/. When upstream corrections are published, they are reflected in TruckCodex at the next scheduled sync.

Frequently Asked Questions

Where does TruckCodex get its data?
TruckCodex uses official government datasets as primary sources. Carrier data comes from FMCSA, recalls and complaints from NHTSA, and diesel prices from EIA. Derived overlays such as the RMIS broker carrier-setup harvest are labeled as derived on /meta/sources/ — not substitutes for FMCSA. No scraped forums or paid reseller feeds are used as primary sources.
How often is TruckCodex data updated?
Carrier census data syncs daily from FMCSA. Recalls and complaints sync daily from NHTSA. Diesel prices update weekly from EIA. Inspection data comes from the FMCSA SMS database with a minimum 24-hour lag. See /meta/freshness/ for live import timestamps.
How does TruckCodex decide Active vs Not Authorized vs Do not book?
USDOT status chips, FAQ answers, and booking verdicts all read from one resolveCarrierStatus() object built from census status, OOS, authority, BIPD insurance signal, and FMCSA safety rating. Heuristics are labeled as such — not legal advice.
Does TruckCodex publish a per-carrier safety grade yet?
Yes on USDOT detail pages: an expandable compliance grade built from authority/census, BIPD insurance, peer OOS, FMCSA safety rating, and insurance-watch tier via resolveCarrierStatus(). Components can be NR with an honest reason; the letter grade is withheld when too few signals resolve. It is a due-diligence heuristic — not an FMCSA rating or legal advice. State Safety Report Cards remain a separate geographic ranking.
How does TruckCodex verify data accuracy?
Every fact displayed links back to its upstream source with an as-of date. Users can verify any claim against the original government record. TruckCodex does not modify source data.
How are carriers, vehicles, and recalls identified?
Carriers are identified by USDOT number. Vehicles are identified by 17-character VIN decoded via NHTSA vPIC. Recalls use NHTSA campaign numbers.
How do I correct inaccurate data on TruckCodex?
Data corrections flow through official government channels. For inspection disputes, use the FMCSA DataQs system. For recall or complaint corrections, contact the NHTSA Office of Defects Investigation. Display issues: /corrections/. Corrections are reflected at the next sync.

Related pages

Last reviewed: .