The Conversation Goes Better With Data
Harsh braking, heavy acceleration and hard cornering recorded per driver and per trip. Not to catch people out, but so the discussion is about what happened rather than who said what.
You Hear About It From Someone Else
A member of the public rings about one of your vehicles. A tyre wears out early. Someone has a near miss and mentions it a week later. You are always finding out second-hand, and always without detail.
- Complaints about company vehicles you cannot verify or dismiss
- Brake and tyre wear that varies wildly between drivers
- Near misses that never get reported
- No evidence when an incident becomes a dispute
- Safety conversations that turn into arguments about opinion
Recorded, Attributed, Reviewable
Each harsh event captured with the time, the place and the vehicle, so a pattern is visible before it becomes an incident.
- Harsh braking, acceleration and cornering events
- Speed against the road's limit, per trip
- Events attributed to a driver and shown on the map
- Trends per driver, so you can see improvement
- A record that stands up if an incident is disputed
How It Works
The unit notices what a passenger would notice
The Unit Detects the Event
Sharp deceleration, heavy acceleration or a hard corner registers as an event with a time and a place.
It Lands Against a Driver
The event is attached to the vehicle and the driver, and plotted where it happened.
You Look at the Pattern
One hard brake is traffic. Forty in a fortnight, in the same three streets, is something worth talking about.
What Gets Recorded
The events that predict incidents, and the context around them
Harsh Braking
The single most useful signal. Frequent hard braking usually means following too closely or going too fast for the road.
Harsh Acceleration
Costs fuel, wears drivetrains, and tends to travel with the other behaviours worth knowing about.
Hard Cornering
Matters most on loaded vehicles and anything with a high centre of gravity, where it is a rollover precursor.
Speed Against the Limit
Recorded against the road's posted limit rather than a flat number, so a highway run does not read like a school zone.
Per-Driver Trends
Events over time per person. The point is watching a number come down after you have talked about it.
Evidence If It's Disputed
When a complaint or an incident is contested, the record shows the speed, the location and the time.
This Works as Coaching, Not as Surveillance
The fleets that get value from driver data treat it as a conversation starter. The ones that use it as a stick end up with drivers who know exactly where the unit is.
Tell people the vehicles are tracked and why. In most states there are workplace surveillance obligations that require notice anyway, and beyond the legal position, a driver who finds out by being shown a report in a disciplinary meeting is a driver who will never trust the system again.
The pattern is what matters, not the event. Everyone gets a hard brake when somebody pulls out in front of them. What is worth acting on is one driver generating five times as many as everyone else on the same routes.
- Tell people first. Notice obligations vary by state, so check what applies to you and be straight about it regardless.
- Compare like with like. Urban delivery work will always produce more events than highway running.
- Look for trends, not incidents. One event is noise. A pattern across weeks is information.
- Close the loop. Show people their own numbers improving. That is the part that changes behaviour.
Built in Ballarat. Backed by Real People.
Protekt GPS has been Australian-owned and operated since 2015, founded by Matt Penhall and Robert Layton. Every feature is developed in-house by our Ballarat team, your data stays on Australian servers, and we're CyberCert SMB1001 Gold certified.
Meet the team behind ProtektSee the Driver Report
Book a demo and we will walk through what a month of events looks like across a real fleet, and what people usually do about it. Or call 1300 95 25 30.