Key Takeaways
- Use an internal fleet safety scorecard to combine leading indicators such as scheduling pressure, unresolved driving time, open safety defects, repeat defects, and telematics events. Do not treat the scorecard as a duplicate of FMCSA’s Safety Measurement System.
- FMCSA’s SMS uses violations recorded during roadside inspections, reportable crash data, and investigation results. An internal ELD alert or near-limit event does not enter SMS unless it results in reportable enforcement data.
- For property-carrying CMVs, a post-trip DVIR is generally required when a defect or deficiency was discovered or reported. Passenger-carrying CMVs have different daily reporting requirements.
- Log edits are not violations by themselves. Review whether the original record was preserved, the edit was properly annotated, and the driver accepted or rejected a carrier-proposed change.
- Use DataQs to request review of inspection or crash data believed to be incomplete or incorrect. Correcting a defect after an inspection does not make the original violation erroneous.
- FMCSA currently organizes SMS into seven BASICs and updates results monthly. Approved future methodology changes should be monitored, but fleets should use the current system until FMCSA announces implementation.
- Verify the exact ELD name and model on the FMCSA Registered ELDs list; registration is based on provider self-certification and does not replace ongoing compliance review.
- Geosavi Compliance Now can bring ELD, DVIR, and GPS information into one workflow, while your safety policy determines the metrics, thresholds, review cadence, and corrective actions.
| Table of Contents |
|---|
| Scorecard Problem |
| CSA Score Basics |
| HOS Data Gaps |
| DVIR Data Gaps |
| Behavior Blind Spots |
| Metrics Compared |
| Buyer Questions |
| Scorecard FAQs |
Introduction
A fleet safety scorecard is an internal management tool that turns operational data into a repeatable review process. It can combine hours-of-service trends, unresolved driving time, safety-related defects, maintenance history, roadside inspection results, and telematics events so your team can identify patterns and assign follow-up.
The scorecard is not an FMCSA requirement and it is not the same as a CSA percentile. FMCSA’s Safety Measurement System uses roadside inspection violations, reportable crashes, and investigation results. Your internal scorecard can include earlier signals that never enter SMS, such as repeated near-limit schedules, open defects, or hard-braking trends.
This guide explains which metrics are useful, which records are legally required, how to distinguish an internal signal from an SMS input, and what action should follow a threshold. Start with a small set of reliable measures and add data only when it improves a real safety decision.
If you would like to see how this applies to your operation, you can schedule a call with our team or call (800) 261-4361.
What Problem Does a Fleet Safety Scorecard Actually Solve?
A fleet safety scorecard solves a practical problem: useful safety information often sits in separate ELD, maintenance, inspection, claims, and telematics systems. Reviewing those sources together can reveal a pattern before it results in a cited violation, roadside out-of-service condition, crash, or repeated repair.
A driver who repeatedly approaches an hours limit, unresolved unidentified driving time, a safety defect that stays open, or an increase in hard-braking events may justify review. None of those signals proves misconduct by itself. The scorecard should direct a manager to the underlying record and a defined response, not automatically label a driver unsafe.
Why Do CSA Scores Belong on Your Fleet Safety Scorecard?
SMS results belong on a fleet scorecard as external, lagging indicators. They should provide context for your internal trends, not become a homemade CSA formula.
FMCSA’s current Safety Measurement System uses 24 months of roadside inspection, reportable crash, and investigation data and updates results monthly. It organizes data into seven BASICs: Unsafe Driving, Crash Indicator, Hours-of-Service Compliance, Vehicle Maintenance, Controlled Substances/Alcohol, Hazardous Materials Compliance, and Driver Fitness. Not every carrier receives a percentile in every BASIC, and some results are not public.
A percentile at or above an applicable intervention threshold can prioritize a carrier for FMCSA attention, but it does not guarantee a particular intervention. Track the cited violations and inspections behind the result, then compare them with internal leading indicators. Our guide to CSA scores and SMS explains the current categories, thresholds, and forthcoming methodology changes in more detail.
How Do You Fix HOS and Log Data Gaps on a Fleet Scorecard?
Use ELD data to identify records that need review before they become enforcement findings. Useful measures include actual hours-of-service violations, repeated approaches to an operating limit, unresolved unidentified driving time, late log certification, unresolved ELD malfunctions, and carrier-proposed edits awaiting driver action.
What Should You Pull From the ELD?
Separate violations from leading indicators. An actual hours-limit violation requires prompt review. Repeated near-limit schedules may indicate dispatch pressure but are not violations by themselves. Unidentified driving should be reviewed and assigned or annotated under the applicable ELD procedures, and late certifications or malfunction records should be tracked to closure.
Why Does Log Integrity Belong on the Same List?
False records of duty status can produce Hours-of-Service Compliance violations, but edit frequency alone does not prove falsification. ELDs preserve the original record, and valid corrections are expected. Review whether an edit is supported, annotated, and handled through the driver confirmation process required by 49 CFR 395.30. Escalate unexplained patterns after examining the underlying records.
How Do You Fix DVIR and Maintenance Gaps on a Fleet Scorecard?
The useful vehicle-side metrics are open safety defects, time to repair and certify them, repeat defects by unit, roadside vehicle violations, and whether maintenance records agree with driver reports.
Under FMCSA’s current 49 CFR 396.11 guidance, a driver of a property-carrying CMV generally prepares a post-trip DVIR when a defect or deficiency was discovered or reported that day. Passenger-carrying CMVs have different daily reporting requirements. A listed defect that would likely affect safe operation must be repaired before the vehicle is operated, and the carrier must certify the repair or that immediate repair was unnecessary as allowed by the rule.
For a property fleet, a blanket no-defect DVIR completion percentage can be misleading because federal rules generally do not require no-defect reports. Track the records your operation is actually required to create, along with any stricter state, Canadian, contract, or company requirements. Geosavi Compliance Now lets drivers attach photos to defect reports, and our ELD and DVIR integration guide explains how those records can support maintenance follow-up.
How Do You Fix Driver Behavior Blind Spots on a Fleet Scorecard?
Telematics events can add useful context, but they are internal indicators rather than automatic FMCSA violations. Calibration, road conditions, vehicle type, route, and exposure all affect the meaning of a raw event count.
Normalize speeding, hard-braking, and hard-acceleration events by miles, driving hours, route, or shift so drivers with different exposure are not compared unfairly. Use an event threshold to trigger review of the underlying trip, not to presume distraction, fatigue, fault, or unsafe intent. Where video is available, our guide to choosing a video telematics system covers event validation, coverage, privacy, and coaching considerations.
How Do the Main Scorecard Metrics Compare?
| Metric | Data Source | Problem It Catches | Regulation or BASIC | Typical Next Step |
|---|---|---|---|---|
| Confirmed HOS violations | ELD and supporting records | Hours-limit or recordkeeping noncompliance | 49 CFR Part 395; HOS Compliance when cited | Review cause promptly and document corrective action |
| Unidentified driving awaiting resolution | ELD | Missing or misattributed driving records | ELD record-management requirement | Review, assign or annotate, and close |
| Log-edit and certification exceptions | ELD audit history | Unsupported edits, missing annotations, or overdue certification | 49 CFR 395.30; not a standalone SMS violation | Review original record, annotation, and driver action |
| Open safety-related defects | DVIRs, defect reports, and work orders | Unsafe dispatch or overdue repair risk | 49 CFR 396.11; Vehicle Maintenance when cited | Repair, certify, and verify before operation when required |
| Repeat defects by unit | Maintenance and defect history | Recurring component or maintenance-program problem | Internal leading indicator; may relate to Vehicle Maintenance | Root-cause and shop review |
| Hard-braking events per exposure | Telematics | Following-distance or situational trend requiring review | Internal leading indicator; not a direct BASIC input | Review trip context and coach when supported |
| Speeding events per exposure | Telematics | Speed-policy and crash-risk trend | Unsafe Driving only when a qualifying violation is cited | Review route context and repeated patterns |
| Reportable crashes and internal preventability reviews | Crash and claims records | Outcome trend and recurring crash factors | Crash Indicator uses qualifying crash data; internal preventability review is separate | Complete a documented root-cause review |
What Should You Ask Before Building a Fleet Safety Scorecard?
Which Data Do You Already Have, and What Is Actually Missing?
Start with reliable ELD records, roadside inspection data, defect and maintenance records, crashes, and claims. Add telematics metrics only when the hardware is configured consistently and the team has a defined process for reviewing the underlying events.
How Many Metrics Should You Track to Start?
Five to eight measures are usually enough for an initial scorecard. Each metric should have a clear owner, denominator, review frequency, source record, and response. Remove measures that do not change a decision.
How Do You Weight a Compliance Violation Against a Behavior Event?
Do not give a cited violation and a single sensor event the same meaning. Weight measures using severity, exposure, data quality, recurrence, and confidence. A telematics alert should usually trigger contextual review, while a confirmed regulatory violation requires compliance follow-up.
What Happens Once a Driver Crosses a Threshold?
Define the response before launch: verify the record, speak with the driver, identify dispatch or maintenance factors, document coaching when appropriate, and escalate repeated or high-severity findings under a consistent policy.
What if a Violation Was Recorded in Error?
Use FMCSA DataQs to request review of Federal or State inspection and crash data believed to be incomplete or incorrect. Provide supporting evidence. A violation that was accurate when recorded does not become erroneous merely because the underlying defect was later repaired.
What Does a Poor Score Actually Cost You?
Costs depend on the underlying event. They can include repairs, downtime, driver or manager time, claims, citations, civil penalties, out-of-service consequences, and additional enforcement attention. Use current agency materials for penalty amounts because maximums change and actual exposure depends on the violation and circumstances.
Who Should Own the Scorecard Day to Day?
Assign one accountable owner, usually a safety or compliance manager, and named partners for dispatch, maintenance, and driver coaching. A consistent weekly review with a deeper monthly trend review is more useful than sporadic checking.
What Does Adding This Cost on Top of Your Existing ELD?
Cost depends on whether the fleet can use existing ELD, inspection, and maintenance data or needs additional telematics and camera services. Our price calculator provides a starting point for Geosavi ELD, DVIR, and GPS configurations.
Fleet Safety Scorecard FAQs
Scorecard and CSA Basics
What is a fleet safety scorecard?
A fleet safety scorecard is an internal report that combines selected compliance, inspection, maintenance, crash, and driver-behavior measures with defined review and follow-up actions.
Does FMCSA require carriers to keep a scorecard?
No. A fleet safety scorecard is an internal management tool. FMCSA separately uses SMS to prioritize carriers based on roadside inspections, reportable crashes, and investigations.
How closely does a scorecard need to match the CSA categories?
It does not need to reproduce SMS. Map confirmed violations to the relevant BASIC for context, but include useful leading indicators such as open defects, scheduling pressure, and unresolved driving records that SMS does not directly measure.
What are the seven BASIC categories?
The current BASICs are Unsafe Driving, Crash Indicator, Hours-of-Service Compliance, Vehicle Maintenance, Controlled Substances/Alcohol, Hazardous Materials Compliance, and Driver Fitness.
Does a good internal score guarantee you avoid a compliance review?
No. An internal score does not control FMCSA intervention decisions. SMS results, investigation findings, complaints, crashes, and other enforcement information may affect agency action.
Is the CSA scoring system changing in 2026?
FMCSA has approved forthcoming methodology changes, including reorganized compliance categories and a split of Vehicle Maintenance. As of this review, the live SMS still uses the current seven BASICs and FMCSA maintains a separate prioritization preview. Fleets should monitor FMCSA for an implementation announcement.
Your Scorecard Questions Answered
What metrics should a small fleet start tracking first?
Start with confirmed HOS violations, unresolved unidentified driving, open safety defects, repeat defects, roadside inspection results, and crashes. Use rates or exposure where fleet size and mileage affect comparisons.
How often should you review the scorecard?
Weekly review works well for active exceptions and open defects, with a monthly trend review for recurring driver, route, dispatch, and maintenance patterns.
Can you add telematics data later?
Yes. Add speeding, hard-braking, or camera events after the underlying system is configured consistently and the fleet has a process for reviewing context rather than relying on raw alert counts.
What if a driver disputes something on their scorecard?
Review the underlying source record with the driver. If Federal or State inspection or crash data appears incomplete or incorrect, submit a supported Request for Data Review through DataQs. Internal disputes should follow a documented correction and escalation process.
How do you know a recurring defect is a bigger problem?
A repeat defect on the same unit, component, or vehicle group should trigger review of the repair history, root cause, inspection process, parts, and maintenance interval rather than another isolated fix.
Does our ELD platform support this kind of scorecard?
Geosavi Compliance Now brings ELD, DVIR, and GPS information into one platform. The fleet still needs to choose appropriate metrics, verify the underlying records, and define its own review and corrective-action process.
Should an owner-operator bother with a scorecard?
Yes, in a simple form. An owner-operator can track confirmed HOS issues, unresolved driving records, safety defects, maintenance deadlines, roadside inspections, and crashes without creating a complex scoring formula.
What Should You Do Next With Your Fleet Safety Scorecard?
A useful fleet safety scorecard does not collapse every signal into one unexplained number. It shows which records need attention, why they matter, who owns the follow-up, and whether the issue was resolved.
Start with a small set of reliable measures: confirmed HOS violations, unresolved driving records, open safety defects, repeat defects, inspection results, and crashes. Add normalized telematics events when they improve a specific coaching or safety decision. Review active exceptions weekly, trends monthly, and the metric definitions whenever regulations, routes, equipment, or operating practices change.
If you want to see how your fleet’s ELD, DVIR, maintenance, and GPS information could support this workflow, schedule a call with our team or call (800) 261-4361.