How to write a fleet driver safety program for small delivery companies

Last updated 2026-07-11

Does OSHA require a fleet driver safety program?

OSHA has no regulation titled 'fleet safety program.' What it has is Section 5(a)(1) of the Occupational Safety and Health Act, the General Duty Clause, which requires every employer to furnish a workplace 'free from recognized hazards that are causing or are likely to cause death or serious physical harm to employees.' ^[1] Driving for work is a recognized hazard. It's the biggest one there is.

The Bureau of Labor Statistics counted 1,942 transportation-related deaths out of 5,283 fatal work injuries in 2023, the leading category for the third decade running. ^[2] That's 37 percent of every occupational death in the country, from one hazard. If you run deliveries and a driver gets hurt on the road, OSHA can cite you under the General Duty Clause even without a vehicle-specific standard.

Some federal rules apply depending on what you run. If your drivers operate commercial motor vehicles over 10,001 lbs gross vehicle weight rating, the Federal Motor Carrier Safety Administration (FMCSA) rules at 49 CFR Parts 390-399 stack on top of OSHA. ^[3] Even if your vans sit under that line, OSHA's recordkeeping rules at 29 CFR 1904 still require you to log and report serious road injuries. ^[4]

The written program ties all of this together. More to the point, it's the paper trail that proves you took reasonable steps before anything went wrong.

What should a fleet driver safety program include?

A workable program for a small delivery company has six sections. Make them as long or short as your operation needs, but all six have to exist in writing.

1. Policy statement and scope One page. Who it applies to, who owns it, and the company's commitment. Name the person responsible by title, not name, so you don't rewrite it every time someone quits.

2. Driver qualification standards Define the minimum bar to drive a company vehicle. At a floor: a valid license for the vehicle class, no DUI convictions in the past three to five years (pick a number and write it down), and a motor vehicle record (MVR) check before hire. Annual MVR reviews are standard practice and catch problems before they turn into claims.

3. Pre-trip inspection procedures Drivers need a written checklist to run before every shift. Brakes, lights, tires, mirrors, fluid levels the driver can see, cargo securement. The checklist is the record. Keep completed ones for at least 90 days. If your vehicles are regulated CMVs, 49 CFR 396.11 requires a daily driver vehicle inspection report kept for 3 months. ^[3]

4. Rules of the road and behavioral standards This is where you ban phone use while driving, set speed expectations, require seatbelts at all times, and deal with fatigue. Be specific. 'No handheld phone use' is enforceable. 'Use good judgment' is not. The FMCSA rule at 49 CFR 392.82 bans handheld mobile phone use by CMV drivers outright. If your vehicles qualify, you follow it, and your program should say so. ^[3]

5. Incident reporting and post-incident procedures Every crash, near-miss, and moving violation gets reported. Set the timeline (many companies require same-day reporting), name who gets notified, and state whether a post-incident drug test is required. Connect this to your OSHA 300 Log obligations under 29 CFR 1904. ^[4] An incident report form drivers can fill out on a phone cuts the odds of anything slipping through.

6. Training requirements Document who gets trained, on what, and how often. New-hire orientation before the first solo delivery. An annual refresher. More training after an incident or a run of violations. Keep the records.

How do you screen and qualify drivers before they start?

The MVR check is where it starts, and it's non-negotiable. Pull the record from your state DMV. Most states let employers do it directly or through a screening company for $10 to $25 per record. Read it before the driver's first day, not after.

Decide in advance what disqualifies a candidate. Here's a common standard for delivery companies:

Violation Type	Disqualifying Threshold
DUI / DWI	Any conviction in past 5 years
Reckless driving	Any conviction in past 3 years
At-fault accidents	2 or more in past 3 years
Moving violations	3 or more in past 3 years
Suspended license	Current suspension

Write these thresholds into your program. If you use a consumer reporting agency to pull records, the Fair Credit Reporting Act (FCRA) applies, and you have to follow adverse action procedures before rejecting a candidate based on the report. ^[5]

A behind-the-wheel evaluation on your actual routes before solo work is worth the hour it takes. You're not testing whether someone can drive. You're testing whether they know your specific vans, the loading dock at your biggest customer, and where to park when there's no legal spot. Those are the moments where a green delivery driver makes a bad call.

What goes on a pre-trip vehicle inspection checklist?

A pre-trip checklist does two jobs: it catches mechanical problems before they cause a crash, and it creates a dated record you can produce after one. Here's a practical structure for light and medium delivery vans.

Outside the vehicle:

• Tires (pressure weekly, visual daily for cuts, bubbles, embedded objects)
• All lights and turn signals (have someone watch while you cycle through)
• Mirrors (adjusted for that driver's sight lines)
• Body damage (note anything new before leaving the yard)
• Cargo door operation and latches

Inside the cab:

• Seatbelt operation
• Windshield (no cracks in the driver's line of sight)
• Wipers and washer fluid
• Horn
• Warning lights on the dash
• Fire extinguisher present and pin intact

Under the hood (weekly or per schedule):

• Oil level
• Coolant level
• Brake fluid
• Battery terminals

The driver signs and dates the form. You keep it. That's the whole system. Digital forms in a fleet app are fine, but a paper clipboard that lives in the van works just as well if drivers actually use it. Pick whichever one they'll complete every single morning.

How do you address distracted driving and cell phone rules?

Distracted driving killed 3,308 people on U.S. roads in 2022, according to NHTSA. ^[6] Delivery drivers are on the road all day and constantly checking apps for navigation and delivery confirmation, so the risk is specific and real.

Your program needs a bright-line rule: no handheld phone use while the vehicle is moving. Hands-free calls are permitted. Texting is banned even at red lights. Navigation gets set before departure or by voice command only. Plenty of small delivery companies go further and ban all phone use while in the driver's seat with the engine running. That's defensible and easier to enforce consistently.

Don't ignore the dispatch side. Your program should say dispatchers won't contact drivers while they're driving in any way that demands an immediate response. If a driver needs to reply to dispatch, they pull over first. This matters in litigation. If a driver crashes while answering a dispatch message, your liability picture shifts hard depending on whether that expectation was on paper.

Enforcement is the hard part. Some companies run telematics that log phone use and hard braking. Others lean on reporting and spot checks. Whatever your mechanism, write it down. A rule with no stated consequence isn't a rule.

What training do delivery drivers need, and how often?

OSHA sets no specific training frequency for fleet programs under the General Duty Clause. The practical standard the agency looks to is what a reasonable employer in your industry would do. For delivery operations, that means three things.

• New-hire orientation before the first delivery, covering your program, the vehicles, reporting procedures, and job-specific hazards like lifting heavy packages or working unfamiliar facilities.
• Annual refresher training for every driver. One hour covers distracted driving, defensive driving, and a review of the past year's incidents.
• After-incident retraining for any driver in a crash or a pattern of moving violations.

Document every session. Each record needs the driver's name, the date, topics covered, and a signature. Keep them for the length of employment plus three years.

Forklifts are a different animal. If drivers operate powered industrial trucks at your warehouse or dock, forklift certification under 29 CFR 1910.178(l) is separate, mandatory, and comes with a re-evaluation interval of at least every three years. ^[7] Don't fold that into the general driver training record.

If your ops manager or safety lead wants broader OSHA training grounding, an OSHA 30 course covers hazard recognition and program management in depth, and insurance carriers respect it.

How do you handle a crash or incident after it happens?

The first ten minutes after a crash matter more than any binder on your shelf. Your incident response section should hand drivers a simple action sequence they can follow while they're rattled.

Immediate steps (driver): 1. Move to safety if possible. 2. Call 911 if anyone is injured. 3. Do not admit fault or apologize at the scene. 4. Exchange information: name, license number, insurance, vehicle plate. 5. Photograph the scene, all vehicles, and any damage before anything moves. 6. Call the designated company contact (name and number on a card in the glove box).

Company-side response:

• Notify your insurance carrier.
• Determine whether a post-incident drug and alcohol test is required under your policy or DOT rules.
• Run the OSHA recordkeeping check: is this a work-related injury that goes on the OSHA 300 Log? Crashes on public roads during work are generally recordable if the driver misses work or gets medical treatment beyond first aid. ^[4]
• For any employee fatality, report to OSHA within 8 hours. For an in-patient hospitalization, report within 24 hours. ^[4]

Do a post-incident review within 48 hours while the details are fresh. The goal is finding what failed in the system, not punishing the driver. Write down what you find and what you changed.

Do you need separate rules for vehicle maintenance?

Yes, and this is the section small companies skip most often. A driver safety program that says nothing about who keeps the vans road-worthy leaves a gap that looks terrible in a lawsuit.

Your maintenance section doesn't need to read like an engineering document. It needs to answer three questions: who schedules maintenance, how defects get reported and fixed, and who decides when a vehicle is too unsafe to drive.

A simple structure works. Define a preventive maintenance schedule (oil changes by mileage, brake inspections by mileage, tire rotation), name one person responsible for tracking it, and build a defect reporting form drivers use when the pre-trip check turns up a problem. That form gets a field for 'cleared for use / not cleared for use,' signed by the responsible person.

Never pressure a driver to take out a vehicle with a known defect. That's the exact scenario where a General Duty Clause citation becomes almost impossible to fight, and where personal injury liability gets genuinely severe. Write into your program that a driver can refuse to operate an unsafe vehicle without retaliation.

How do you write the program if you've never done it before?

Start with a one-page policy statement and build outward. You do not need a 60-page manual. A workable program for a 5 to 15 vehicle delivery company fits in 10 to 15 pages if you write in plain language.

Here's a realistic sequence:

1. Write the policy statement. One page, signed by the owner or top manager. 2. Pull a sample MVR and write your qualification standards based on what you see. 3. Build the pre-trip checklist for your actual vehicles. Walk around one van with a notepad. 4. Write the phone and distracted driving rule. One paragraph. 5. Write the incident reporting procedure. Use the action sequence above as your starting point. 6. Write the training section. List what training exists now and what gap you're closing. 7. Write the maintenance section.

Once you have a draft, hand it to someone who wasn't involved and ask: if I were a new driver, would I know what to do? That one question catches most of the holes.

Want a faster start? SafetyFolio's safety program generator walks you through a set of questions and produces a document formatted for your operation in about 15 minutes. It won't replace your judgment, but it beats staring at a blank page.

After you have a draft, check it against OSHA's motor vehicle safety guidance and any FMCSA rules for your vehicle class. Update the document at least once a year, or after any significant incident.

What records do you need to keep, and for how long?

Record retention is where small companies get burned. They write a decent program, run decent training, then can't prove any of it happened because the papers are gone.

Here's a practical retention schedule for fleet safety records:

Record Type	Minimum Retention
MVR checks	Duration of employment + 3 years
Driver qualification files	Duration of employment + 3 years
Pre-trip inspection reports	90 days (3 months for CMV operators per 49 CFR 396.11) [3]
Training records	Duration of employment + 3 years
Incident / accident reports	5 years
OSHA 300 Log	5 years following the calendar year [4]
Vehicle maintenance records	Current calendar year + 1 year

Digital storage is fine. A shared Google Drive folder organized by driver and year works well for companies without dedicated fleet software. The one thing that matters: you can find a specific record in under five minutes when an OSHA inspector or an attorney asks for it.

What does a good fleet safety program actually cost to build?

Writing the program yourself costs time, not money. Budget 8 to 16 hours for a first-time writer at a 5 to 20 vehicle company, spread across drafting, reviewing with drivers, and revising.

The ongoing costs matter more:

• MVR checks: $10 to $25 per driver per year through a state DMV or screening vendor. For 10 drivers, that's $100 to $250 a year.
• Training: Run it in-house on FMCSA or NHTSA materials (both free) and the only cost is time. Third-party defensive driving courses run $25 to $75 per driver for the online versions.
• Telematics: If you want data on speeding, hard braking, and phone use, basic fleet telematics runs $15 to $40 per vehicle per month. Optional for a small fleet, but it's one of the few safety spends that also cuts insurance premiums directly.

The business case is blunt. FMCSA data puts the average cost of a truck crash involving an injury at $148,279, and a fatal crash at $3.6 million once you count litigation and lost productivity. ^[8] The program costs a few hundred dollars a year to maintain. The math isn't close.

How does your fleet safety program connect to OSHA recordkeeping?

Fleet safety and OSHA recordkeeping meet at the incident. When a driver is injured in a work crash, the injury is generally work-related and subject to 29 CFR 1904 recordkeeping if it hits any recording criterion: death, days away from work, restricted work, transfer to another job, medical treatment beyond first aid, loss of consciousness, or a significant injury diagnosed by a healthcare professional. ^[4]

You log work-related injuries and illnesses on the OSHA 300 Log. You complete an OSHA 301 Incident Investigation form (or equivalent) for each recordable case. The OSHA 300A summary gets posted every year from February 1 through April 30. Employers with 10 or fewer employees and those in certain low-hazard industries are partially exempt from 1904, but delivery operations are not in an exempt industry. ^[4]

Your incident reporting procedure should flow straight into your OSHA 300 process. When a driver reports a crash, the company-side response includes a recordability determination. If you're not sure how to make that call, OSHA's recordkeeping advisor tool at osha.gov walks the decision tree. ^[4]

For a closer look at filling out the forms correctly, the incident report guide walks through each field.

And if you're growing and want to understand the wider regulatory picture, what does OSHA stand for covers the agency's authority and how it reaches employers well outside the traditional factory floor.

Frequently asked questions

Is a fleet driver safety program legally required for small delivery companies?

OSHA has no regulation titled 'fleet safety program,' but the General Duty Clause (Section 5(a)(1) of the OSH Act) requires employers to protect workers from recognized hazards. Motor vehicle crashes are the leading cause of occupational fatalities in the U.S., so a written program is how you show you took reasonable steps. FMCSA rules at 49 CFR Parts 390-399 add requirements if your vehicles exceed 10,001 lbs GVWR.

How often should delivery drivers be trained on fleet safety?

At minimum, a new-hire orientation before the first solo delivery and an annual refresher for all drivers. After any crash or pattern of violations, retraining is standard. OSHA sets no specific frequency for General Duty Clause programs, but 'annual' is what most compliance consultants and insurers treat as the baseline for delivery work. Document every session with dates, topics, and signatures.

What is an MVR check and why does it matter for a fleet program?

An MVR, or motor vehicle record, is the driving history issued by a state DMV. It shows license status, convictions, suspensions, and at-fault accidents. Pulling one before hire and annually after is the base of driver qualification. MVR checks typically cost $10 to $25 per record. Without them, you may hire drivers with disqualifying histories and face heavy liability exposure if they later crash.

Do OSHA rules apply to delivery drivers who use their own vehicles?

Yes. OSHA's General Duty Clause covers employees whether they drive a company van or a personal car for work. If you send an employee on a work errand in their own car and they're injured, that injury is still work-related for OSHA recordkeeping. Your program should set company rules that apply to all work-related driving, including personal vehicles used for deliveries.

What should I do immediately after one of my drivers is in a crash?

Have the driver call 911 if anyone is injured, document the scene with photos, exchange information, and call the designated company contact. On the company side: notify your insurance carrier, determine whether a post-incident drug test is required, evaluate OSHA recordability under 29 CFR 1904, and report to OSHA within 8 hours if an employee died or 24 hours if an employee was hospitalized. Run a post-incident review within 48 hours.

Can I use a template for my fleet driver safety program?

Yes, a template is a reasonable starting point, but it has to be customized to your actual vehicles, routes, and operation. A template that says 'all drivers must follow company vehicle rules' without defining those rules won't protect you legally or operationally. Customize at least the qualification standards, vehicle checklist, and incident reporting contacts so the document matches what actually happens at your company.

Do I need a fleet safety program if I only have two or three delivery vans?

Fleet size doesn't change the legal obligation under the General Duty Clause. A two-van operation that has a crash with a driver injury faces the same OSHA recordkeeping requirements and the same liability exposure as a larger company. The program can be shorter for a small fleet, maybe 8 to 10 pages, but the core elements (qualification, inspection, training, incident reporting) still need to be documented.

What's the difference between a fleet safety program and a DOT safety program?

A fleet safety program is the general term for written policies covering driver qualification, training, vehicle inspection, and incident response. A DOT safety program refers specifically to compliance with FMCSA regulations at 49 CFR Parts 390-399, which apply to commercial motor vehicles over 10,001 lbs GVWR. If your vans are under that threshold, FMCSA rules don't apply, but OSHA's General Duty Clause still does.

How do I enforce phone and distracted driving rules with delivery drivers?

Write a bright-line rule (no handheld use while the vehicle is moving) and define the consequence for violations in your program. Enforcement options include telematics that log phone use and hard braking, manager spot checks, and a self-reporting requirement. Whatever mechanism you use, it must be written down. A rule with no stated enforcement is hard to apply consistently and harder to defend in litigation.

What records from my fleet safety program do I need to keep?

Keep MVR checks and driver qualification files for the duration of employment plus three years. Keep training records for the same period. Pre-trip inspection reports: 90 days minimum, three months if you operate CMVs under FMCSA rules. Incident reports: five years. OSHA 300 Logs: five years following the calendar year they cover. Vehicle maintenance records: current year plus one year. Store them where you can retrieve them fast.

Does my fleet safety program need to cover loading and unloading, or just driving?

It needs to cover both. Delivery driver injuries happen at both ends of the route. Your program or a companion document should address safe lifting, dolly and hand truck use, loading dock procedures, and cargo securement. If drivers use forklifts at your facility, OSHA's powered industrial truck standard at 29 CFR 1910.178 requires specific training and evaluation separate from general driver safety training.

How do I calculate whether my fleet safety program is actually working?

Track four metrics quarterly: crashes per 100,000 miles driven, moving violations per driver per year, near-miss reports (higher is actually better, it means people are reporting), and days of work lost to vehicle-related injuries. Compare year over year. If crashes climb after you launch the program, check whether training actually happened and whether drivers feel safe reporting near-misses without punishment. That matters more than whether the binder exists.

Do I need to report vehicle crashes to OSHA?

You may need to record them, and in serious cases report them. Under 29 CFR 1904, work-related injuries from crashes that meet recording criteria go on your OSHA 300 Log. If an employee dies in a work-related crash, you must call OSHA within 8 hours. If an employee is hospitalized as in-patient, you must call within 24 hours. These obligations apply whether or not the crash also involves a police report or insurance claim.

Sources

1. OSHA, OSH Act of 1970 Section 5(a)(1) General Duty Clause: The OSH Act requires employers to furnish a workplace free from recognized hazards that are causing or are likely to cause death or serious physical harm to employees.
2. Bureau of Labor Statistics, Census of Fatal Occupational Injuries Summary, 2023: Transportation incidents accounted for 1,942 of the 5,283 fatal work injuries in 2023, making them the leading category of occupational fatalities.
3. Federal Motor Carrier Safety Administration, 49 CFR Parts 390-399: FMCSA regulations govern commercial motor vehicles over 10,001 lbs GVWR, including daily driver vehicle inspection reports under 49 CFR 396.11 (retained 3 months) and the ban on handheld mobile telephone use under 49 CFR 392.82.
4. OSHA, Recordkeeping Rule 29 CFR 1904 and OSHA Recordkeeping Advisor: 29 CFR 1904 requires employers to log work-related injuries and illnesses on the OSHA 300 Log for 5 years; fatalities must be reported to OSHA within 8 hours and in-patient hospitalizations within 24 hours.
5. Federal Trade Commission, Fair Credit Reporting Act guidance for employers: Employers who use a consumer reporting agency to obtain MVR or background check information must follow FCRA adverse action procedures before rejecting a candidate based on the report.
6. National Highway Traffic Safety Administration, Distracted Driving 2022 data: Distracted driving killed 3,308 people on U.S. roads in 2022 according to NHTSA.
7. OSHA, Powered Industrial Trucks standard 29 CFR 1910.178: 29 CFR 1910.178(l) requires employer-conducted forklift operator training and evaluation before unsupervised operation, with re-evaluation at least every three years.
8. Federal Motor Carrier Safety Administration, Large Truck and Bus Crash Facts: FMCSA data shows the average cost of a truck crash involving an injury is $148,279; a fatal crash averages $3.6 million in total costs including litigation and lost productivity.
9. OSHA, Motor Vehicle Safety guidance: OSHA cites employers under the General Duty Clause for vehicle-related hazards and provides fleet safety guidance applicable to all employers whose workers drive for work.
10. FMCSA, Driver Qualification Files (49 CFR 391 subpart): FMCSA requires driver qualification files including MVR checks; standard industry practice for non-CMV fleets mirrors these requirements for driver screening.