Introduction
The primary purpose of the driver role is to transport Clinicians to and from patient locations in a safe and timely manner together with all the equipment and medication needed to deliver the highest possible standards of patient experience
Audits will be performed to ensure that all staff drive at an appropriate speed that is safe for the conditions even when responding to an urgent patient, and that national and local speed limits are respected at all times.
Auditing Process
Audits will cover each car and include all journeys, thus encompassing every single journey, regardless of the purpose of the journey or identity of the staff member. Audits will be carried out on a monthly basis to maintain a consistent and equitable approach across all journeys.
A journey deemed to contravene safe driving law and therefore picked up as an unsafe act in the audit process, is when/if any journey where a Brisdoc vehicle has been driven at 10% more than the speed limit for longer than 1 minute.
Action taken with offending staff members is detailed further below.
Staff members should be re-audited for assurance that driving styles have changed and no further speeding incidents are found within 3 months.
Audit Tasks
| Task | Resources | Frequency | Responsible |
| Run report for 1 month period to
identify any journeys with a recorded speed of 10% over the speed limit. |
Car Tracking software | Monthly | Team
manager Driver Lead |
| Identify the team member most likely responsible for the journey | Rota Master / Driver logs | Monthly | Team manager Driver Lead |
| Enter Data onto a quarterly log to document speed, highlight drivers with more than one offence per
quarter (Appendix B) |
Word Document | Monthly | Team manager Driver Lead |
| Email to be sent out to anyone exceeding the speed limit CC’ng their
line managers (Appendix C) |
Monthly | Team manager
Driver Lead |
|
| Log is reviewed quarterly with repeat offenders highlighted with a distinctive
colour( 3 speeding incidents per quarter) |
Car Tracking software/ Rota Master / Driver logs | Quarterly | Team manager Driver Lead |
Monitoring
Repeat offenders will be offered an online course following a discussion with their line manager, courses are available through governance team, if the driver has another speeding incident, then we may look at more formal action.
|
|||||||||||
Appendices
Appendix A – Audit Process
Appendix B
S:\GOVERNANCE TEAM\CONFIDENTIAL – DAC\6. H&S\Safe Driving
Appendix C
Dear XXX
We have recently analysed the data we have received from the in-car trackers in the SevernSide vehicles during the Last 3 month.
Unfortunately, the data shows that, on XX occasion during this period, a vehicle that you were driving has exceeded the legal speed limit on XXXXX by at least 10%. This was also confirmed by your driver logs and rotamster.
As a BrisDoc employee you are required to comply with the legal speed limits at all times which, as a general rule, are XXX mph unless local or national speed limits say otherwise.
In the future, I must urge you to always make sure you are driving within the legal speed limit, as per the BrisDoc Safe Driving Policy instructions, the key elements of which I have quoted below:
“Speed is often a key factor in the cause of accidents particularly when the vehicle is “en route” to a patient whom it is believed is very ill. Emergencies are the prerogative of specially trained emergency drivers. BrisDoc is not an emergency service. High speed lessens the time a driver has to respond to any developing situation in front of them. Good driving requires that a driver drives at an appropriate speed that is safe for the conditions even when responding to an urgent patient. It is imperative that national and local speed limits are respected at all
times.”
In the event of any future data analysis identifying a repeat offence or offences it may be necessary to look to more formal action to assist in bringing performance back in line with the safe driving policy.
Thank you for your support and understanding. Regards
XXX
Change tables
| Date | Version | Author | Change details |
| 01-08-23 | V1.1 | HE | Review |
| 21/08/24 | V1.2 | HE | Full review |