SMS control
Safety Management & SMS Compliance
SMS scores are business signals. BOF connects roadside inspections, violations, crashes, DataQ challenges, driver qualification, corrective action, and dispatch consequence in one reviewable record.
What the Safety Page Must Answer
| Question | BOF Evidence | Operating Consequence |
|---|---|---|
| What happened? | Inspection, citation, crash notice, telematics event, driver statement | Ready, review, hold, or blocked status. |
| Who owns it? | Safety lead, driver file owner, maintenance owner, dispatcher | Named follow-up and due date. |
| What clears it? | Corrected inspection proof, DataQ result, coaching record, repair evidence | Driver or load can return to dispatch only after the clearance rule is met. |
SMS BASIC Review
Unsafe Driving, Crash Indicator, HOS Compliance, Vehicle Maintenance, Controlled Substances/Alcohol, Hazardous Materials, and Driver Fitness must be tracked by cause and consequence. BOF does not just show a score; it shows the reason the score moved and the correction path.
- Capture the event. Inspection or telematics signal attaches to driver, unit, and load.
- Classify the exposure. BASIC, severity, preventability, and operational risk are recorded.
- Assign corrective action. Coaching, document correction, maintenance repair, or DataQ challenge is opened.
- Close with proof. Completion evidence stays with the record before release language changes.
Governing policyBOF-POL-005 - Claims and Incident Response
Incident, claim, corrective-action, and evidence-routing standards support the safety control record.
View policy →