What this is
What is a speeding event record?
What is a speeding event record?
It is the record raised each time a driver exceeds the speed threshold set for monitoring, whether the alert comes from telematics, a camera, an enforcement notice or a member of the public. It captures the reading, the context around it, and the conversation held with the driver, and it feeds a running count against ISO 39001 cl.8.1's requirement to monitor road safety performance.
What counts as the threshold, and who sets it?
The threshold is whatever the telematics or camera system is configured to alert on, typically a margin above the posted limit rather than the limit itself. It is set by the fleet operator, not mandated by ISO 39001, so two operators running the same standard can have materially different event volumes for the same driving.
How does this differ from a Telematics Performance Review?
A Telematics Performance Review looks at a driver's or route's aggregate pattern across harsh braking, acceleration, cornering, speeding and idling over a period. A Speeding Event Record is the single-event log that feeds that aggregate. You need the event records to be complete and accurate before the periodic review means anything.
Scope
When is a speeding event record required?
This record is for the single event: one driver, one alert, one conversation. Once the question shifts from what happened this time to what keeps happening, or what caused physical harm, it belongs somewhere else in the programme.
Use this template when
- A telematics alert, camera flag, enforcement notice or public report identifies one driver exceeding the speed threshold on one occasion
- The line manager needs to hold the post-event conversation with the driver and record what was discussed and agreed
- The event needs to be linked back to a live Telematics Review period so it rolls into the periodic pattern analysis
- A pattern of events on the same route or by the same driver needs a documented decision on whether the schedule, not the driver, is the problem
- The workspace register needs an entry retired or a new threshold event type added
Do not use it for
- Telematics Performance Review, which reviews harsh braking, acceleration, cornering, speeding and idling by driver and route as an aggregate over a period, not a single event.
- Camera Footage Review Record, which records the review of forward or in-cab footage after an event and what it showed, and is the right place once footage review itself is the task.
- Driver Performance Review, which sits above single events and covers the driver's overall conduct across a review cycle.
- Road Collision Report, once the event involves a collision or physical harm rather than a speed reading alone.
- 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 requires operational planning and control of road safety performance factors, which for a speed-threshold event means the record has to show the event, its cause, and what changed as a result. The form maps that requirement onto five sections.
| Clause | Requirement | Where it lands |
|---|---|---|
| cl.8.1 operational control | Capture the event with enough detail to identify driver, location, recorded speed and limit at the time. | Header |
| cl.8.1 operational control | Establish whether the event is isolated or repeat, on the same driver or the same route. | Context |
| cl.8.1 operational control | Test whether the schedule is achievable at the posted limit, rather than assuming the driver is the variable. | Context |
| cl.8.1 operational control | Confirm the limiter, where fitted, was working at the time of the event. | Context |
| cl.8.1 monitoring and response | Hold and document a conversation with the driver, including their explanation, before any action is decided. | Response |
| cl.8.1 monitoring and response | Escalate where the event repeats, rather than treating each occurrence as a first offence. | Response |
| cl.8.1 corrective action | Record the root cause and the action taken, and route a change of schedule or route where that is the finding. | Outcome |
| cl.8.1 corrective action | Record the event against the driver's file and raise a CAPA where further action is required. | Outcome |
What it does not cover
- Root Cause left as Driver habit, which is entered without checking whether the same route produced the same event for a previous driver too.
- Schedule Achievable At The Limit, which is marked Yes without anyone timing the route at the posted limit to confirm it.
- Repeat Events Same Route, which is answered No from memory rather than by pulling the driver's or the route's event history.
- Conversation Held With Driver, which is marked Yes for a conversation that consisted of a text message rather than a discussion.
- Escalation Applied Where Repeated, which is left No on a fourth event because the previous three were each treated as isolated.
Global
Speeding Event Record requirements by country
ISO 39001 is voluntary everywhere, but what a speeding event record is later used to defend differs sharply by jurisdiction, and the three below carry the most weight in practice.
FMCSA Compliance, Safety, Accountability programme — Unsafe Driving BASIC
Speed violations feed a carrier's Unsafe Driving score directly, and a pattern of unresolved events raises the carrier's intervention risk independent of any single incident's severity.
A thin or informally-handled event record is a liability at audit: the CSA data already shows the events happened, and a file that cannot show what the carrier did about each one looks like a carrier that did nothing.
Traffic Commissioner operator licence undertakings; DVSA earned recognition
An operator licence is held on the basis of undertakings to manage drivers' hours, vehicle condition and safe driving, and repeated unaddressed speeding is treated as evidence the operator is not managing the licence conditions.
This record is the evidence trail a Traffic Commissioner's office asks for at a public inquiry: not that speeding never happens, but that each event was seen, discussed and acted on.
ISO 39001:2012 cl.8.1, cl.9.1
The standard treats speed management as a road safety performance factor to be planned, controlled and monitored, not eliminated to zero, and certification audits sample event records against that control.
An auditor is checking the loop closes: event logged, cause investigated, action taken, and the result fed back into scheduling or coaching, not just that a form exists.
How to complete it
How to complete a speeding event record, step by step
Filling in the fields is mechanical. The judgement sits in four calls that decide whether the record actually defends the operator or just documents a conversation.
Driver habit is the easiest box to tick and the hardest to defend later if the same route keeps producing events across different drivers. Cross-check Repeat Event Same Route before accepting habit as the answer.
This field decides whether the corrective action lands on the driver or on the timetable. Answering Yes without ever driving or timing the route at the limit turns a scheduling defect into a permanent driver problem.
Data error scores as the cleanest outcome and is sometimes reached for when a telematics reading looks implausible but nobody has actually checked GPS drift, calibration, or a mismatched speed limit database entry. It should only be selected once that checking has happened.
Coaching is proportionate for a first, isolated event. Once Repeat Event Same Driver or Same Route reads Yes, the Action Taken and Schedule Change Required fields should reflect that this is no longer a coaching-only situation.
What auditors find
Most common speeding event record findings
The findings an auditor or a new manager reviewing the register typically raises, mapped to the clause behind them and the fix.
| Finding | Clause | What fixes it |
|---|---|---|
| Events logged with no route or driver history check | cl.8.1 | Require the Context section's repeat-event fields to be answered against the actual register, not from memory, before the record can be marked complete. |
| Root Cause consistently recorded as Driver habit across a whole route | cl.8.1 | Pull the last four quarters of events for that route and route ID; if the pattern holds across multiple drivers, reclassify as a scheduling issue and raise the CAPA against the schedule, not the driver. |
| No conversation evidence beyond a tick in Conversation Held With Driver | cl.8.1 | Require the Driver Explanation Recorded field to hold an actual quote or summary, not be left blank alongside a Yes. |
| Limiter status assumed rather than checked | cl.8.1 | Cross-reference the vehicle's most recent inspection or defect record before answering Limiter Fitted And Working. |
| Escalation not applied on a documented repeat event | cl.8.1 | Add a register-level check that flags any driver or route with more than two open events in a rolling quarter before a new one can be closed without escalation. |
| Action Required marked No while a schedule or route change is still pending | cl.8.1 | Tie Action Required to Schedule Change Required and Action Taken so a Route change or Schedule change answer forces a linked CAPA reference. |
Case in point
Case in point: the route nobody re-timed
A regional depot logged eleven speeding events over six months on the same delivery run, spread across four different drivers. Each record was closed the same way: Root Cause set to Driver habit, Action Taken set to Coaching, Schedule Change Required left at No.
When a fifth driver raised it directly with the transport manager, a re-time of the route at the posted limit showed the schedule allowed eleven minutes less than the drive genuinely took. Four drivers had absorbed that gap the only way available to them. The fix was a schedule change, not a fifth coaching conversation, and it should have been visible after the third record if Repeat Event Same Route had been checked against the register rather than answered from memory each time.
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.
5 sections
- Reference
- FLT-042
- Archetype
- Record
- Record ID
- SPD-2026-000
- Scoring
- Events per driver
- Direction
- Low is good
- Singleton
- Yes
- Basis
- ISO 39001 cl.8.1
- Links
- Links Telematics review, Journey planning
- Tags
- Fleet, Speeding
- Sections
- 5
- Fields
- 40
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 4
Header
13 fieldsRecord ID*
Auto sequence. Format SPD-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Driver*
Event Source*
Event Time*
Location*
Recorded Speed*
Speed Limit*
Repeat Events On One Route Mean The Schedule Is Wrong
A driver speeding on the same stretch every week is usually a driver who cannot make the delivery window any other way.
Context
6 fieldsRepeat Event Same Driver*
- Yes3 pts
- Partly1 pt
- No0 pts
Repeat Event Same Route*
- Yes3 pts
- Partly1 pt
- No0 pts
Schedule Achievable At The Limit*
- Yes3 pts
- Partly1 pt
- No0 pts
Delay Earlier In The Journey*
- Yes3 pts
- Partly1 pt
- No0 pts
Traffic Or Diversion Involved*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Limiter Fitted And Working*
- Yes3 pts
- Partly1 pt
- No0 pts
Response
6 fieldsConversation Held With Driver*
- Yes3 pts
- Partly1 pt
- No0 pts
Driver Explanation Recorded*
- Yes3 pts
- Partly1 pt
- No0 pts
Coaching Provided*
- Yes3 pts
- Partly1 pt
- No0 pts
Route Or Schedule Reviewed*
- Yes3 pts
- Partly1 pt
- No0 pts
Escalation Applied Where Repeated*
- Yes3 pts
- Partly1 pt
- No0 pts
Outcome Explained To The Driver*
- Yes3 pts
- Partly1 pt
- No0 pts
Related records
1 fieldTelematics Review ID
The review period this event falls in.
Links to FLT-041 Review ID
Outcome
14 fieldsRoot Cause*
- Schedule pressure0 pts
- Driver habit1 pt
- Unfamiliar route1 pt
- Limiter fault0 pts
- Data error3 pts
Action Taken*
- Coaching2 pts
- Written warning1 pt
- Route change3 pts
- Schedule change3 pts
- No action0 pts
Schedule Change Required*
- No3 pts
- Yes1 pt
Recorded On Driver Record*
- Yes3 pts
- No0 pts
Driver Record ID
Links to FLT-008 File ID
Review Date
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Transport*
Signature*
Line Manager*
Second Signature*
FLT-042 · record IDs look like SPD-2026-000 · Links Telematics review, Journey planning
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures one event well. Catching the pattern across a hundred events, on time, without someone remembering to check, is the part that needs a workspace behind it.
Holds the speeding event register, flags repeat events on the same driver or route automatically, and keeps the link to the Telematics Review current.
Tracks whether coaching logged against a speeding event actually happened and was recorded, rather than left as an open action nobody closes out.
Surfaces route and schedule data alongside the event, so 'is the schedule achievable at the limit' can be checked against real drive times instead of a guess.
Rolls open speeding events and overdue escalations into one view across drivers and routes, 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
Speeding Event Record definitions and key terms
- Speed limiter
- A device fitted to a vehicle that mechanically or electronically restricts its maximum speed, required on many HGV and PSV categories and checked as part of routine inspection.
- Telematics
- Onboard systems that capture and transmit vehicle and driving data, including speed against posted or configured limits, feeding both single-event alerts and periodic performance reviews.
- Root cause
- The underlying factor behind an event, distinct from its immediate trigger; for a speeding event this is what decides whether the fix is coaching, a route change or a schedule change.
- Operator licence undertaking
- A commitment made by a UK operator when granted a licence to manage drivers' hours, vehicle roadworthiness and safe driving, against which enforcement bodies assess compliance.
- CSA Unsafe Driving BASIC
- One of the FMCSA's Behaviour Analysis and Safety Improvement Categories, scoring a carrier's safety performance on speeding and other unsafe driving violations.
FAQ
Frequently asked questions about speeding event record
What is the speeding event record template based on?+
It is built against ISO 39001 cl.8.1, the road safety performance factor control requirement, which asks that speed management be planned, monitored and acted on rather than left to individual judgement.
What sections does it contain?+
Five sections: Header, Context, Response, Related records and Outcome, holding 40 fields, 33 of which are required before the record can close.
Is one record created per driver or per event?+
Per event. Every qualifying alert gets its own record, which is what makes the events-per-driver score meaningful; batching multiple events into one record breaks the metric.
Which programme does this belong to?+
Fleet and Driver Compliance, whose stated outcome is an operator licence position defensible at an audit with no notice.
How is it scored, and why is low good?+
Scoring is events per driver, and low is good because the metric is tracking how often the threshold is crossed, not how well each individual event was handled afterwards.
Can the threshold or the scoring weights be changed?+
Yes. The threshold that triggers an alert sits in the telematics or camera configuration outside this template, but every field, option weight and conditional rule inside the record is editable.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Fleet and Driver Compliance
Transport Provider Assessment
Assesses a haulier for licensing, driver management, vehicle standards, temperature capability and load security
Driver Vehicle Inspection Report
The pre-trip and post-trip inspection a driver completes on a commercial vehicle
Annual Vehicle Inspection
The yearly statutory inspection of a commercial vehicle
Trailer Inspection
Checks trailer coupling, brakes, lights, tyres, doors and structure
Reefer Unit Check
Checks refrigeration unit operation, fuel, temperature setpoint and alarm history
Vehicle Defect Report
Reports a defect found on a vehicle at any time, not just during a scheduled inspection
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
Sources and last review. Reviewed 16 August 2026 against:
- ISO 39001:2012 cl.8.1 — Operational planning and control
- FMCSA Compliance, Safety, Accountability — Unsafe Driving BASIC
- UK Traffic Commissioner operator licence undertakings
- Road Traffic Regulation Act 1984, s.89 — speeding offences (England and Wales)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.