Knowella

Adverse Weather Driving Record

The failure mode isn't the weather — it's the record appearing after the incident, backfilled to look like management called it. A driver checks the sky, decides to run because the load's already late, and by the time anyone writes anything down the ice has already caused the skid. This record exists so someone with the authority to say no makes that call before the wheels turn, not after.

KnowFleetRecordFLT-04046 fields across 6 sectionsFull researchSee the form

Reviewed by Siddarth SinghCSPLast reviewed 16 August 2026

Basis
ISO 39001 cl.8.1
Workspace
KnowFleet
Form type
Record
Completed by
Transport management, not the driver
Raised
The moment conditions deteriorate, before departure

The short version

  • This is a singleton control document recording who decided to run, delay or cancel journeys in bad weather — it is not a per-driver diary of conditions encountered.
  • Scoring rewards a decision made by management with the driver consulted, and penalises pressure applied to run and decisions recorded after the fact rather than at the time.
  • Forecast Source Used scores an official forecast above an app, and an app above 'looked outside' — the record distinguishes a genuine assessment from a guess.
  • It links to Journey Assessment (FLT-037) and Hours of Service, so the weather decision sits alongside the route risk it modifies rather than standing alone.

What this is

What is an adverse weather driving record?

What is an adverse weather driving record?

It is a singleton record in KnowFleet that captures the decision to run, delay or cancel one or more journeys because of weather, and names who made that call. It sits inside the Cold Chain and Transport programme and is built against ISO 39001 cl.8.1.

Why does management have to make the call rather than the driver?

A driver deciding whether to run in ice is weighing their job against their own safety, alone, usually under time pressure. Making the decision a recorded management act, with the driver consulted rather than left to decide, removes that conflict.

What counts as adverse weather for this record?

The Weather Condition field lists five triggers: ice or snow, high wind, fog, heavy rain or flooding, and extreme heat. Any one of them can raise the record, and more than one can apply to the same journey.

Scope

When is an adverse weather driving record required?

This record is one control point in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.

Use this template when

  • Severe weather is forecast or already affecting one or more scheduled journeys
  • A driver has raised concern about conditions and needs a management decision, not a personal one
  • The workspace is being set up, or the register needs an entry added or retired
  • You are running the Cold Chain and Transport programme and this is one of its control points
  • A linked Journey Assessment or Hours of Service record depends on this decision existing

Do not use it for

  • Journey Risk Assessment, which assesses a planned journey before it starts — route, hours, load and delivery point — not a live call made once weather has already turned.
  • Temperature Log, which records in-transit temperature readings for a refrigerated load, not the decision to run at all.
  • Cold Chain Excursion Record, which captures what happened after temperature control was lost, not the go or no-go call that preceded departure.
  • Delivery Point Assessment, which assesses a fixed site's access and reversing hazards, not conditions on the road that change hour to hour.
  • Anything outside KnowFleet, which belongs in the workspace that owns that process.

Compliance mapping

Which ISO 39001 cl.8.1 requirements does this satisfy?

ISO 39001 cl.8.1 covers operational planning and control for road traffic safety hazards, which is where the run, delay or cancel decision for adverse weather sits. The clauses below map to the sections that actually carry that requirement.

ClauseRequirementWhere it lands
ISO 39001 cl.8.1A defined operational control for adverse weather, applied consistently rather than left to individual judgementHeader
ISO 39001 cl.6.1Assessment of the specific hazards present before a decision is madeAssessment
ISO 39001 cl.8.1The decision made by someone with authority over the operation, not by the person exposed to the riskDecision quality
ISO 39001 cl.8.1Defined controls applied when the operation proceeds despite the hazardControls if running
ISO 39001 cl.6.1Coordination with the journey risk assessment the weather decision modifiesRelated records
ISO 39001 cl.9.1Monitoring of the outcome to confirm the decision was soundOutcome
ISO 39001 cl.10.1Corrective action where the decision or its controls proved inadequateOutcome

What it does not cover

  • Recording the decision after the journey has already run, which turns a safety control into an after-the-fact justification.
  • Leaving Decision Made By blank, or filled with the driver's own name, which puts the call back on the person under the most pressure to say yes.
  • Selecting 'Looked outside' as the forecast source, which treats a decision with journeys and lives attached as a guess rather than an assessment.
  • Proceeding with Winter Equipment Carried and Recovery Arrangements Confirmed left unanswered, which sends a vehicle into the conditions with no plan for what happens if it goes wrong.
  • Closing the record without linking the Journey Assessment ID, which leaves the weather decision disconnected from the route risk it was supposed to sit alongside.

Global

Adverse Weather Driving Record requirements by country

ISO 39001 is the base standard, but the exposure this record manages runs through general workplace safety law and, in the US, through hours-of-service rules written specifically around adverse weather.

United Kingdom

Health and Safety at Work etc. Act 1974, s.2 and s.3, alongside HSE driving-for-work guidance

An employer can be liable for a crash caused by pressuring a driver to run in conditions they should have refused — the record is the evidence the call was made properly and by the right person.

A signed, timed decision record showing driver consultation is the practical defence against a work-related road safety enforcement action.

United States

49 CFR 395.1(b) — adverse driving conditions exception

The exception extends a driver's permitted hours when conditions genuinely could not have been foreseen at the start of the shift, but only if the decision was made in real time.

This record's Decision Time field is what an auditor checks against the hours-of-service log to see whether the exception was earned or claimed after the fact.

International

ISO 39001 cl.8.1

The standard treats adverse weather as an operational hazard requiring a defined control, not a judgement call left to whoever happens to be driving.

Certification audits ask for the record showing who decided and what they considered — a verbal decision with nothing written satisfies neither the clause nor an insurer after an incident.

How to complete it

How to complete an adverse weather driving record, step by step

Filling in every field correctly still leaves four judgement calls that decide whether the record actually holds up:

Who actually decided, versus who is named as deciding

Decision Made By must be the person with authority to say no, not the driver reporting what they already did. If the same name appears here as on the vehicle log, the record isn't doing its job.

Whether the forecast source matches the scale of the decision

Cancelling or delaying multiple journeys on 'looked outside' is a weak record even when the outcome turns out right. Forecast Source Used and Authority Warnings Checked exist to show the call was informed, not lucky.

Whether 'proceed with restrictions' actually names the restrictions

A Decision of proceed with restrictions is only defensible if Reduced Speed Instructed, Increased Journey Time Allowed and Check In Points Agreed are answered, not left as a stated intention. An undefined restriction is the same as none.

Whether the record closes with a genuine outcome, not a rubber stamp

Outcome Acceptable and Any Incident Occurred should reflect what actually happened on the road, checked against the linked Journey Assessment, not defaulted to 'Yes' or 'No' before the journey has even returned.

What auditors find

Most common adverse weather driving record findings

What an auditor or insurer typically finds wrong with this record in practice:

FindingClauseWhat fixes it
Decision Time logged hours after the journey departed, matching when the paperwork was done rather than when the call was made.ISO 39001 cl.8.1Require the record to be raised and Decision Time populated before departure is authorised, not at the end of the shift.
Decision Made By Management Not The Driver scored Yes with the driver's own name entered as Decision Made By.ISO 39001 cl.8.1Restrict who can complete this field to transport management roles, and cross-check it against Completed By.
Forecast Source Used answered 'Looked outside' on a record affecting multiple journeys.ISO 39001 cl.6.1Require an official forecast or app check before any decision affecting more than one journey is authorised.
Winter Equipment Carried and Recovery Arrangements Confirmed left blank on a 'Proceed as planned' decision in ice conditions.ISO 39001 cl.8.1Make the controls section mandatory whenever Decision is anything other than Cancel journey.
Journey Assessment ID left blank, so the weather decision has no link back to the route risk it modifies.ISO 39001 cl.6.1Enforce the link at submission so the record cannot close without a Journey Assessment reference.
Review Date left blank on records where Outcome Acceptable was 'No' or an incident occurred.ISO 39001 cl.10.1Make Review Date mandatory whenever the outcome shows a problem, and route it to Action Owner automatically.

Case in point

Case in point: the delay that looked like a refusal

A transport manager delayed three refrigerated journeys by four hours after an ice warning. Decision Made By showed the manager's name, Driver Consulted was Yes, Forecast Source Used was Official forecast, and Authority Warnings Checked was Yes. When a customer complained about the late delivery, the record showed the delay was a documented decision, not a driver's excuse.

Contrast that with a record from the same fleet three weeks later: a driver ran in similar conditions, Decision Made By was left blank, and Forecast Source Used was answered 'Looked outside' after the vehicle had already left the yard. The only reason it surfaced at all was a near-miss report — the record itself would have said nothing happened.

The template

The template, field by field

The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.

46fields
6 sections
Reference
FLT-040
Archetype
Record
Record ID
AWD-2026-000
Scoring
Decisions recorded
Direction
High is good
Singleton
Yes
Basis
ISO 39001 cl.8.1
Links
Links Journey assessment, Hours of service
Tags
Fleet, Weather
Sections
6
Fields
46
Follow up fields
3
Repeating sections
0
Links out
3
Field typesOwn ID, generated on saveCase thread and parentPick list from a registryLinked to another templateFollow up, dashed outlineScored

Header

13 fields
Text

Record ID*

Generated on save

Auto sequence. Format AWD-2026-000.

The record's own ID. Other templates point at this value.

Single Choice

Status*

Scored

Drives who this goes to next.

  • Planned2 pts
  • In progress2 pts
  • Complete3 pts
  • Deferred0 pts
  • Open0 pts
  • Closed3 pts
  • Overdue0 pts
Date & Time

Date and Time*

Users

Completed By*

Pick List

Site*

From FDN-001 Site NameFilter: Status is Active
Text

Site ID*

Linked

Format SITE-000.

Links to FDN-001 Site ID

Single Choice

Weather Condition*

Ice or snowHigh windFogHeavy rain or floodingExtreme heat
Date & Time

Decision Time*

Users

Decision Made By*

Numeric Answer

Journeys Affected*

Scored
Single Choice

Forecast Source Used*

Scored
  • Official forecast3 pts
  • App2 pts
  • Looked outside0 pts
Single Choice

Authority Warnings Checked*

Scored
  • Yes3 pts
  • No0 pts
Info

Drivers Should Not Make This Call Alone

A driver deciding whether to run in ice is a driver weighing their job against their safety. Making it a recorded management decision removes that.

Assessment

6 fields
Single Choice

Road Conditions Assessed*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Route Specific Risks Considered*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Vehicle Suitability Considered*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Driver Experience Considered*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Delivery Urgency Considered*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Alternative Timing Considered*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts

Decision quality

6 fields
Single Choice

Decision Made By Management Not The Driver*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Driver Consulted*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Driver Empowered To Stop En Route*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

No Pressure Applied To Run*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Customer Informed Of Delay*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Decision Recorded At The Time*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts

Controls if running

6 fields
Single Choice

Reduced Speed Instructed*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Increased Journey Time Allowed*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Check In Points Agreed*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Winter Equipment Carried*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Recovery Arrangements Confirmed*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Communication Maintained*

Scored
  • Pass2 pts
  • Partial1 pt
  • Fail0 pts
  • N/Aexcluded from denominator

Related records

1 field
Text

Journey Assessment ID

OptionalLinked

The journey affected by the conditions.

Links to FLT-037 Assessment ID

Outcome

14 fields
Single Choice

Decision*

Proceed as plannedProceed with restrictionsDelay departureCancel journey
Text

Reason

Optional
Single Choice

Outcome Acceptable*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Any Incident Occurred*

Scored
  • No3 pts
  • Yes0 pts
Text

Case ID

OptionalThread key

Thread key

Date & Time

Review Date

Optional
Single Choice

Action Required*

Scored

Raise the action record, then enter its reference here.

  • No2 pts
  • Yes0 pts
Single Choice

Priority

OptionalScoredShows if Action Required equals Yes
  • High0 pts
  • Medium1 pt
  • Low3 pts
Text

CAPA ID

OptionalLinkedShows if Action Required equals Yes

Format CAPA-2026-00000.

Links to FDN-014 CAPA ID

Users

Action Owner

OptionalShows if Action Required equals Yes
Users

Transport Manager*

Signature

Signature*

Users

Site Manager*

Signature

Second Signature*

FLT-040 · record IDs look like AWD-2026-000 · Links Journey assessment, Hours of service

Open in Knowella

Run it with agents

From a document you fill in to a programme that runs itself

The form captures the decision. Keeping the right person in the approval chain, and making sure a delayed journey doesn't just vanish from the schedule, is the part that needs a workspace behind it.

KnowFleet

Holds the adverse weather driving record against your fleet register, and links it automatically to the Journey Assessment and Hours of Service records it depends on.

KnowSafe

Picks up any incident logged against a journey that ran in adverse weather, so a sound decision on paper still gets checked against what actually happened on the road.

KnowOps

Surfaces the delay or cancellation against the day's schedule, so a defensible weather decision doesn't quietly become a missed delivery nobody flagged.

Ella
Ella

Coordinates the crew, rolls open weather decisions and their outcomes into one view, and holds every write for your approval before it touches a record.

This template lives in KnowFleet — fleet and transport. Drivers, vehicles, hours, cargo securement and operator licence compliance.

Meet KnowFleet→

Glossary

Adverse Weather Driving Record definitions and key terms

Run, delay or cancel decision
The three outcomes available when weather threatens a journey — proceed, push the departure back, or stop the journey entirely — and the point this record exists to capture.
Adverse driving conditions exception
The US hours-of-service allowance under 49 CFR 395.1(b) that extends driving time when conditions genuinely could not have been foreseen at the start of the shift.
Operational control
An ISO management-system term for a defined method of managing a hazard during day-to-day operation, as distinct from a one-off risk assessment carried out in advance.
Singleton record
A record type set up once per workspace and reused, rather than created fresh for every event — appropriate here because the decision framework doesn't change between weather events.
Journey risk assessment
The planning-stage assessment of a specific journey's route, hours, load and delivery point, which this weather decision sits alongside rather than replaces.

FAQ

Frequently asked questions about adverse weather driving record

Who is allowed to make the run, delay or cancel call?+

Transport management, not the driver on their own. The Decision Made By Management Not The Driver field exists specifically to stop a driver under schedule pressure from making a safety call alone.

What counts as an adverse weather condition on this record?+

Ice or snow, high wind, fog, heavy rain or flooding, and extreme heat. Any one of these can trigger the record, and more than one can apply to the same journey.

Does the driver get a say in the decision?+

Yes — Driver Consulted and Driver Empowered To Stop En Route are both scored fields. The intent is a management decision made with the driver's input, not a decision made about the driver without it.

What happens if the journey proceeds and something still goes wrong?+

Any Incident Occurred and Outcome Acceptable capture that, and Case ID links the record to whatever incident thread follows. A sound decision at the time doesn't guarantee a clean outcome, and the record is built to hold both.

How does this connect to the Journey Assessment?+

Through the Journey Assessment ID field. The weather decision modifies a journey that was already risk-assessed for route, hours and load — it doesn't replace that assessment.

Is this a one-off form, or does every weather event get its own record?+

It's a singleton — one record per workspace, reused for each weather event rather than rebuilt from scratch, so the decision framework and its scoring stay consistent over time.

Keep going

Related templates and programmes

Siddarth Singh

Written and reviewed by

Siddarth Singh

Founder & Chief Executive Officer, Knowella

Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.

  • Certified Safety Professional (CSP), Board of Certified Safety Professionals
  • MBA, University of Chicago Booth School of Business
  • MS and BS, The Ohio State University, Industrial and Systems Engineering
  • Six Sigma Black Belt
Verify with BCSP →

Sources and last review. Reviewed 16 August 2026 against:

  • ISO 39001:2012 cl.8.1 — Operational planning and control
  • 49 CFR 395.1(b) — Adverse driving conditions exception
  • Health and Safety at Work etc. Act 1974, s.2 and s.3

This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.