One Terminal's Crash Report Becomes Every Terminal's Safety Rating
FMCSA's CSA safety measurement system scores carriers by USDOT number, not by terminal. One site's violations can move the whole fleet's public safety rating.
A regional operator with terminals in four states has one location with an aging tractor fleet and a maintenance backlog. The other three terminals run tight preventive maintenance programs and rarely see a roadside violation. Ask a safety director at head office how the fleet is doing, and the honest answer depends entirely on which terminal they mean.
FMCSA's Compliance, Safety, Accountability program does not see it that way. The Safety Measurement System scores a motor carrier, identified by its USDOT number, not a location. Every roadside inspection violation, every crash, feeds into one set of BASIC scores for the entire carrier, regardless of which terminal's truck or driver was involved. The site with the maintenance backlog is not just that site's problem. It is dragging down a number that follows the whole company into every shipper's vendor review and every insurance renewal.
The unit of measurement is the carrier, not the site
CSA organizes violations into Behavior Analysis and Safety Improvement Categories, covering things like unsafe driving, hours of service compliance, vehicle maintenance, and crash indicator. Each category produces a percentile score, and those scores are what shippers, brokers, and insurers pull when deciding whether to do business with a carrier, and at what rate.
A multi-site operator with decentralized maintenance and decentralized driver management often has, in effect, several different safety cultures operating under one DOT number. One terminal's inspection results and one terminal's driver hours-of-service violations do not stay local. They post to the same carrier-level score that a terminal running a disciplined program also contributes to, and a percentile score cannot distinguish which contribution came from where. A shipper reviewing the carrier's profile sees one number. They do not see that three of four terminals are performing well.
This is structurally different from a single-site operator's problem. A one-location carrier's CSA score is, by definition, a direct reflection of that location's practices. A multi-site carrier's score is an average, and averages hide the site that is actually driving the number down until someone goes looking for it.
Roadside inspections happen wherever the truck is, not where it is domiciled
A driver domiciled at the well-run terminal can still be inspected in a state where the carrier has no other presence, and a violation there posts to the same carrier record as one from the home terminal. This means a multi-site fleet's CSA exposure is not just the sum of its terminals' individual practices. It is the sum of everywhere its trucks physically travel, inspected by whichever state or local enforcement happens to pull them over that day.
A carrier that only reviews inspection data by terminal, matching violations back to the site that dispatched the truck, can still miss the aggregate picture that FMCSA and everyone reading the FMCSA data actually sees. The terminal-level view is useful for assigning accountability internally. It is not the view a shipper's safety department uses to decide whether to award freight.
Maintenance standards drift apart faster than anyone notices
Vehicle maintenance is one of the categories most directly under a carrier's control, and it is also the one most likely to diverge quietly across a multi-site fleet. Each terminal may have its own shop, its own mechanics, its own sense of what "due for service" means in practice versus on paper. Two terminals following what everyone believes is "the same maintenance program" can produce meaningfully different out-of-service rates at roadside inspections if the underlying execution differs, even when the written policy is identical.
A written maintenance standard that exists at the corporate level is a necessary condition for consistency, not a sufficient one. The question worth asking is not whether every terminal has the same policy document. It is whether every terminal's actual out-of-service and violation rate at roadside inspection looks the same, and if it does not, whether anyone at the level that sees the aggregated CSA data is the same person who can see why one terminal differs operationally.
A high-risk carrier can trigger a compliance review before a single crash
FMCSA uses CSA data, among other factors, to prioritize which carriers get investigated. A carrier whose scores cross certain thresholds becomes a higher priority for intervention, up to and including a full compliance review, independent of whether an actual crash has occurred. A multi-site carrier whose aggregate score has drifted upward because of one terminal's practices can find itself facing a compliance review triggered by data that, terminal by terminal, would not have flagged any single location on its own.
That review, when it happens, examines the carrier's systems as a whole: driver qualification files, hours of service records, maintenance files, drug and alcohol program records. A multi-site operator whose recordkeeping is decentralized by terminal, rather than standardized and centrally auditable, discovers during a compliance review that pulling a consistent picture across every location under short notice is itself a significant undertaking, separate from whether the underlying safety practices were adequate.
The intervention does not have to reach the level of a full compliance review to matter commercially. Many shippers and brokers now screen carriers against CSA thresholds before ever awarding freight, and some insurers price fleet coverage off the same public percentiles. A carrier whose aggregate score sits at an unfavorable percentile because of one terminal's contribution can lose bids or see premiums rise for reasons that have nothing to do with the terminals actually being evaluated by the party reading the score. Nobody on the losing end of that bid sees the terminal breakdown. They see the carrier's number.
What consistency actually requires here
Centralizing CSA monitoring is the first step, and it is more available than most multi-site operators realize: FMCSA's own portal and several third-party services let a carrier pull its current BASIC percentiles and see the underlying violation data in a form that supports drilling down by terminal, driver, or vehicle. Reviewing the aggregate score without also reviewing which terminal is contributing which violations produces the same blind spot as reviewing terminals individually without ever looking at the aggregate.
Maintenance standardization has to mean auditable execution, not a shared policy manual. If two terminals report the same preventive maintenance interval but have different roadside out-of-service rates, that gap is the thing to investigate, not the paperwork that says the intervals match.
Driver qualification and hours-of-service compliance benefit from the same treatment. A driver's record should be reviewable centrally regardless of which terminal domiciles them, particularly for a multi-site operator whose drivers periodically move between locations or run routes that cross multiple terminals' territory.
The number that follows the company
A carrier's CSA profile is public, visible to any shipper, broker, or insurer who looks it up. It does not carry a footnote explaining that the maintenance issue was isolated to one terminal, or that three of four locations run a tight program. It is one score, attached to one USDOT number, and it moves as one number regardless of how many buildings, fleets, and safety cultures sit underneath it.
The operators best positioned to manage that exposure are the ones who treat CSA data the way FMCSA does: as a carrier-level signal that requires a carrier-level view to interpret correctly, with the terminal-level detail available underneath it rather than substituted for it.
General guidance only, not legal advice. FMCSA scoring methodology and thresholds change periodically. Verify current requirements against FMCSA guidance and consult a qualified compliance professional regarding your fleet's specific profile.
Not sure where you stand?
Take the 5-minute compliance assessment. Answer a few questions about your business and get a prioritized list of what OSHA expects, free.
Related Articles
Continue learning about OSHA compliance and workplace safety
Construction Safety
Excavation's Competent Person Is Designated at the Site. Corporate's Org Chart Assigns the Role by Title.
OSHA's excavation standard, 29 CFR 1926.651, requires a competent person who evaluates that specific site's soil daily. A title alone cannot substitute for it.
Fire Protection
Combustible Dust Isn't One Hazard. Across a Portfolio of Sites, It's a Different One at Each Address.
Combustible dust falls under OSHA's General Duty Clause and NFPA standards, not one rule — a portfolio policy must fit a different material at each site.
Health Hazards
Silica Table 1 Is Written Per Task, Per Tool. Your Compliance Program Is Written Per Company.
OSHA's respirable silica standard, 29 CFR 1926.1153, specifies controls by task and tool. Across many job sites, that specificity is exactly what a corporate policy tends to flatten.