Trucking Company Safety Plan: AI-Drafted Policies and Toolbox Talks

Give an AI assistant a one-page fact sheet about your fleet and ask for three drafts: a safety policy outline, a 52-week calendar of ten-minute toolbox talks and an incident review form. Edit them into your own words, then have a qualified person check every rule against the regulations for your vehicles and drivers before you issue anything.

The order matters. AI is quick at structure and wording and unreliable on which rule applies where, so use it for the parts that take hours and keep a person on the parts that carry legal weight. A good first draft takes about an afternoon. The checking takes longer than the drafting, and it is the part that protects you.

Follow me on Instagram@sagnikteaches

Who owns what: the drafting split

Before you open a chat window, decide which jobs AI does and which stay with people. This table is the split I would start from.

Connect on LinkedInSagnik Bhattacharya

The right-hand column is where AI goes wrong in ways that matter. A model writes a number such as "drivers must not exceed 11 hours" in the same confident voice as a sentence about wearing a hi-vis jacket. Only one of those is yours to verify. If you only remember one rule from this tutorial, make it that every figure in the plan is looked up in the source by a person, not copied from the draft.

Subscribe on YouTube@sagnikteaches

Write the fact sheet the assistant will work from

A generic safety policy is worthless to a driver. The difference between a generic draft and a useful one is the fact sheet you paste first. Spend 20 minutes on it and the drafts improve a great deal. Here is a filled-in version for an illustrative fleet:

FLEET FACT SHEET (illustrative)
- 9 tractors and 14 trailers; 7 full-time drivers, 2 part-time
- Work: general freight on two regular routes plus ad hoc loads;
  about 30% of loads are refrigerated
- Own yard with 6 bays, a fuel island and a small workshop
- Drivers start between 04:30 and 08:00; some overnight stays away
- Telematics fitted to all tractors; dashcams on 5 of them
- Incidents in the last 12 months: 2 minor yard strikes while
  reversing, 1 load shift on a tight bend, 1 slip on an icy step,
  4 near misses reported (2 at customer docks, 2 on the road)
- Existing paperwork: a driver handbook from 2019, a vehicle
  checklist on paper, no written incident procedure
- Who is the safety lead: owner, with the lead driver helping
- Language: plain English, drivers read on a phone

Notice the incident list. A plan built on what actually happened at your company will outperform one built on what trucking companies in general are said to worry about. The fact sheet also gives the assistant your reading level and your device, which is why a later talk will be short enough to read on a phone in the cab.

Do not put names, licence numbers or medical details in. An incident can be described as "driver A, second year with the company". If your assistant is on a personal plan, check the setting that controls whether chats are used to improve the model, and the AI usage policy tutorial has wording you can adapt for staff.

Step one: draft the policy outline, then fill your own rules in

Ask for an outline first, not a finished policy. A finished policy hides gaps behind smooth prose; an outline shows you what is missing. A prompt that works:

Using the fleet fact sheet above, draft an outline for a written
safety policy. For each section give: a heading, one sentence on
what it covers, and a list of "decisions the owner must make" (things
you cannot know). Do not state any legal limit, number or regulation.
Where a rule would normally apply, write [CHECK: RULES FOR OUR FLEET] instead. Plain English, short sentences.

A reasonable illustrative result would be an outline along these lines: purpose and who the plan covers; roles (owner, lead driver, drivers); vehicle checks before and after a shift; driving rules for fatigue, phones and speed; loading, securing and unloading; reversing and yard movements; weather and winter; incidents, near misses and reporting; training and talks; records; review. Under each heading sits the list of decisions the owner must make.

The "decisions" lists are the valuable part. Under yard movements it might ask: who is allowed to marshal a reversing vehicle, what is the yard speed limit, are pedestrians kept out of the bays, and is there a rule on engine off during loading? Answer each one in a sentence, in your own words, as a short note beside the outline. That note is the policy. The assistant's job after that is only to turn it into clean paragraphs.

What you should fix in the draft

Expect three kinds of fault. First, rules from the wrong world: a draft might mention "the logbook" or a daily vehicle report by a name that does not fit your equipment. Second, stray numbers that slipped in despite the instruction. Search the draft for digits and strike every one you cannot source. Third, generic filler such as "safety is everyone's responsibility", which can go. Keep the sections short enough that a driver can read one on a phone in two minutes.

Step two: a year of ten-minute toolbox talks

A toolbox talk is a short, regular safety briefing given to the people doing the work, traditionally standing around a toolbox on site. In a fleet it happens in the yard before the shift, at a depot meeting or as a short read on a phone. The aim is repetition of one useful idea, not coverage of everything.

Ask the assistant for a calendar, then edit it against your incident list. A prompt:

Make a 52-week calendar of toolbox talk topics for the fleet in the
fact sheet. Rules: one topic a week; weight the topics towards our
incident history (reversing, load security, icy steps, customer docks);
put winter topics in the cold months and heat and tyres in summer;
every 4th week is a review of a real near miss (leave a blank for me
to fill in). Output as a table: week, topic, one-line aim, who leads.

Here is how the first twelve weeks of an illustrative output might look after editing:

Reordering is the part that makes this yours. If your winter incident was a slip, the ice topic belongs in the first cold week, not at week 40 where the assistant placed it. A calendar like this also removes the Monday scramble of deciding what to talk about.

A full talk, filled in: reversing in the yard

This is what one finished talk can look like. Ask for the structure "hook, two or three rules, one question for the drivers, one action", and supply the real event.

TOOLBOX TALK: Reversing in the yard (10 minutes)

Why now: Two minor strikes in the past year, both while reversing
into bay 4 or 5 with a trailer attached. No injuries. Both
happened in the first hour of the shift.

Three rules we are keeping
1. Get out and look. If you cannot see the whole path, stop, get
   out and look before you move.
2. One marshal at a time, standing where you can see them in the
   mirror. If you lose sight of them, stop.
3. Hazards and horn before reversing, every time.

Question for the room
What makes bay 4 harder than bay 1?

Action this week
Lead driver paints a stop line at the top of bays 4 and 5 and
reports back at next week's talk.

Record: date, who attended, topic covered.

Two things make this talk work. It refers to your yard and your two incidents, so drivers recognise the bay. And it ends in an action with an owner and a date, so the next talk can open with "the stop lines are painted". A talk without an action is a lecture; a talk with one builds a record that safety is managed.

Making the AI's version sound like it came from this yard

Left alone, an assistant produces talks that open with a statistic or an inspirational line. You can see the difference in a before and after on the same topic.

Before (typical draft): "Slips, trips and falls remain one of the leading causes of injuries in the transport sector. This week we will explore best practices for safe entry and exit from the vehicle cab."

After (edited): "On the icy morning last month a driver slipped off the second step of tractor 6. Nobody was hurt. Today we look at how to get down, and who clears the frost."

The "before" quotes a general claim you cannot source; strike it. The "after" is shorter, true and local. As a rule, delete any sentence that begins "studies show" or states how common an injury is, unless a person finds the source. If you want a talk's text to sound like your company, give the assistant three of your own messages to drivers and ask it to match that tone. The brand voice guide tutorial covers that technique in detail.

Step three: an incident and near-miss review that does not blame

This is where AI saves the most time and where care matters most. An incident review form has four jobs: record what happened, find causes, agree actions, and check back later. The assistant can draft the form and tidy a rough account. It must not decide who was at fault.

Here is a driver's rough account of a minor incident, written in
his own words. Do the following:
1. Rewrite it as a neutral timeline, with times if given.
2. List what we know and what we do NOT know.
3. Suggest five questions for me to ask on the "why" side:
   equipment, yard layout, schedule pressure, training, and
   communication. Do not suggest blame or a disciplinary step.
4. Draft three possible corrective actions, each with an owner and
   a due date field left blank.

Say the account is "Backed trailer into the post at bay 5 about 06:15, a bit dark, marshal had gone to take a call". An illustrative reply would list a timeline, then unknowns (was the yard light working? how long had the marshal been away? was there a time pressure from a 07:00 departure?), then five "why" questions and three actions: add a light, add a stop line, agree that reversing waits if the marshal leaves. You still choose which of those fits, and you decide whether a retraining talk is enough.

Keep a one-page form so that near misses, which are cheaper to learn from than injuries, are easy to report. The fields are: date and time, where, what happened, what nearly happened, what we think caused it, what we will do, by whom, by when, and checked on. Ask the assistant to write it as a phone-friendly form your drivers can complete in two minutes. The more painless it is, the more near misses you hear about. For the same idea in a different trade, see the near-miss logging tutorial.

Where the AI draft put a rule that did not belong

A fleet owner asked for a driving-rules section and received a tidy paragraph describing a daily logbook procedure and a specific limit on weekly driving time. The wording sounded official. The problem was that the fleet ran smaller vehicles under a different set of rules from the heavy tractors the paragraph assumed, and the figure was out of date for their class.

It was caught because the owner had asked the assistant to mark every rule with [CHECK: RULES FOR OUR FLEET], and the adviser who reviewed the draft looked at each marker. Had the paragraph read as plain text, it might have gone out unchecked. The instruction costs nothing and it turns a hidden risk into a visible list.

A three-question quiz and a first-week pack for new starters

Two smaller jobs use the same fact sheet and take almost no extra effort. The first is a quick check that the talk landed. Ask the assistant for three questions on each talk: one recall question, one "what would you do" scenario and one about your own yard. For the reversing talk, an illustrative set would be: "Name the first thing you do before reversing into bay 4" (recall), "The marshal steps out of view. What happens next?" (scenario) and "Where is the new stop line?" (your yard). Drivers answer on a phone form or out loud. The point is not to pass or fail anyone. If three drivers in nine get the scenario wrong, the rule needs a better explanation, which is a finding about the talk rather than the people.

The second is a first-week pack for a new driver. Ask for a one-page checklist ordered by day: day one is the yard walk, fuel island, bays and where pedestrians are allowed; day two is the vehicle walk-round done alongside the lead driver; day three is the incident and near-miss form, completed once on a pretend event so that the first real one is not the first attempt. A filled-in line reads: "Day 2, 09:30, walk-round of tractor 4 with the lead driver, covering the order we always use. Done / not done / questions." Keep each line short enough to tick on a phone. The assistant produces this in one pass; you correct the order and delete anything you do not actually do.

Both items feed the record. A dated quiz result and a signed-off first-week list are the sort of evidence an insurer's risk visit or a customer's supplier questionnaire may ask for, and both are cheap to produce once the fact sheet exists.

The check by a qualified person: what to hand over

Someone who knows the rules for your vehicles has to review the plan. That could be your insurer's risk adviser, a transport or safety consultant, a trade association's helpline or a qualified safety manager. Make the review quick for them:

1. Send the policy with every [CHECK] marker still visible, plus your fact sheet so they can see your vehicle classes, loads and routes.
2. Ask them to confirm or correct each rule, give the source for each figure, and list anything missing.
3. Ask what records they expect you to keep, and for how long.
4. Ask whether your toolbox talk record and sign-in sheet are enough.
5. Update the plan, note the date of the review in your records, and set the next review.

For the paperwork side, the audit checklist tutorial shows how to organise the records an inspector may ask to see, and the driver qualification file tutorial covers expiry tracking for licences and medicals.

Feeding real data back into the plan

A plan that is written once and filed becomes shelfware. The plan improves if the incident log and your telematics data feed the next set of talks. If your telematics shows harsh braking clustered on one road, that is a talk. If your yard time audit finds a long stay at the gate, ask whether it is a safety queue. The yard time and toll audit tutorial shows how to ask Claude the first of those questions, and the same approach works for harsh-braking events, provided driver names are replaced with codes before the file is uploaded.

Once a quarter, paste the incident log (anonymised) into the assistant and ask: "Which three topics from our talk calendar should be moved up, and which should be replaced?" That takes five minutes and keeps the year aligned with what is actually happening on your roads.

What a ten-vehicle fleet spends in hours and subscriptions

For a fleet of about ten vehicles, expect this rough effort:

• Fact sheet: 20 to 30 minutes, once, then 10 minutes a quarter.
• Policy outline and your answers to the decision lists: about two hours.
• Clean draft and edit: another two hours.
• Talk calendar and the first twelve scripts: one hour, then ten minutes a week.
• External check: depends on the person you use; ask for a quote before you commit.

Add it up for the illustrative nine-tractor fleet. Set-up is about five and a half hours: 30 minutes for the fact sheet, two hours on the decision lists, two hours editing and one hour on the calendar and first scripts. Running it costs about nine hours a year in talk preparation (52 weeks at 10 minutes is 520 minutes) plus 40 minutes of quarterly fact-sheet updates. Each talk then takes ten minutes of nine drivers' time, which is 90 driver-minutes a week, the largest cost in the whole plan and the reason to keep every talk to one topic.

The assistant itself costs little. ChatGPT Plus lists at $20 a month and Claude Pro at $20 billed monthly or $17 a month billed annually, either of which is enough. Free plans work for the drafting but have tighter limits on uploads and long chats, so check the allowance if your documents are big.

The value is less in the money than in what you can show: a dated plan, a year of talks, a log of incidents with actions and a record that someone qualified reviewed it. Those are what an insurer, a customer's safety questionnaire or an auditor ask for, and they are what a driver notices when the owner keeps turning up to the Monday talk.

Questions before you issue an AI-drafted safety plan

Can AI write my whole trucking safety plan?

It can write a usable first draft of the structure, the wording and a year of talks. It cannot know which rules apply to your vehicles, loads and drivers, and it can state a rule with total confidence that is wrong or out of date. Someone qualified has to check the finished plan against the rules that apply to you.

Which AI tool should I use for this?

Any current chat assistant that can hold a long conversation and read an uploaded file will do, such as ChatGPT, Claude or Gemini. A Project or saved workspace helps because your fact sheet and house style stay attached from one session to the next.

How long should a toolbox talk be?

Ten minutes is a sensible ceiling. One topic, one real example from your own fleet, two or three things drivers should do differently, and a minute for questions. Talks that run longer tend to lose the room and the sign-in sheet becomes a formality.

Do I need drivers to sign for each talk?

Keeping a dated record of who attended and what was covered is good practice, and an insurer or auditor may ask for it. Whether a signature is required depends on the rules that apply to you, so confirm that with your adviser or insurer.

Further reads

• AI in the Trucking Industry: What a Small Fleet Owner Can Use Now — Wider list of jobs a small fleet can hand to AI.
• Farm Safety Plan: Draft Risk Assessments and Toolbox Talks With AI — Same method for a different workplace with moving vehicles.
• Detention Pay: AI Tracks Wait Times and Invoices Brokers — Waiting time at customer sites is a safety and a cost issue.
• Can AI Help a Roof Cleaning Business? Photo Quotes and Safety Notes — Shows how another high-risk trade writes safety notes.
• How to Use AI in a Trucking Company: Load Paperwork Without Retyping — Cuts paperwork time so talks actually happen.
• AI Incident Response Plan for Small Businesses (With Template) — Separate plan for when an AI tool itself goes wrong.
• Can AI Write Toolbox Talks? What a Competent Person Must Check — AI can plan a year of toolbox talks, script each five minutes and format the sign-in sheet. A competent person still reviews and signs every one.
• Operator Licence Compliance: AI Tracks Checks, Audits and Renewals — A diary-and-sheet system for safety inspections, driver checks, maintenance records and change notifications, with AI prompts that keep it current.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: claude.com/pricing and openai.com/chatgpt/pricing (checked 5 November 2026). No regulations are quoted because they differ by place and vehicle class.