Driver behavior monitoring turns the speed, braking and idling data your trackers already collect into a record of how each vehicle is driven, so a manager can coach the habits that cost money and cause accidents. It is a module of the vehicle tracking system, not a separate device, and HHET configures it from Jeddah for fleets across Saudi Arabia, with the thresholds set to your vehicles and your roads rather than to a generic default.
What driver behaviour monitoring measures
The tracker reports position and speed every few seconds while the vehicle moves, and many units add a built-in accelerometer that samples motion hundreds of times a second. From those two sources the HHET platform derives a short list of events, each stamped with a time, a place and a driver.
- Speeding. Speed above a limit you set, either fleet-wide or per vehicle type, with the duration and the road where it happened.
- Harsh braking and harsh acceleration. A change in speed within a short window, confirmed by the accelerometer, which is how the system tells a hard stop from a gentle slowdown on a ramp.
- Harsh cornering. Sideways force above a threshold, relevant for loaded trucks and buses on roundabouts and slip roads.
- Idling. Ignition on, wheels still, for longer than your allowance.
- Night and out-of-hours driving. Movement outside the shift window you define.
Nothing here needs a camera. Where a company wants video evidence beside the data, dash cam and video telematics adds it as a separate, consent-based layer.
How the driver score is built
A score is only useful if drivers can see how it was made. The platform counts events per 100 km, not per trip, so a driver on a long Jeddah–Riyadh run is not penalised against one doing short city drops. Each event type has a weight that you can change: a fleet of tankers may weight harsh cornering heavily, a delivery fleet may weight idling and speeding. The weighted total becomes a score from 0 to 100 for the week and the month, with the individual events one click beneath it, plotted on the map and in the trip playback.
Because the score rests on events you can open and replay, the conversation with a driver starts from what happened at 14:20 on Tuesday near the Makkah Road interchange, not from a number the driver has never seen explained.
Alerts for speeding, harsh braking and idling
Reports tell you about last week; alerts let you act today. Each event type can raise a push notification, an SMS or an email, and you choose which ones deserve interrupting a manager. A typical setup sends speeding above the limit for more than 30 seconds to the supervisor immediately, groups harsh braking into the daily digest, and flags idling past 15 minutes outside a loading bay. Alerts can also play a short buzzer in the cab on units that support it, which corrects the habit at the moment it happens, and many drivers adjust after a few days of that alone.
| Event | Detected from | Typical setting | Instant alert | In score |
|---|---|---|---|---|
| Speeding | GPS speed against your limit | Limit per vehicle type, with a grace period of a few seconds | Yes | Yes |
| Harsh braking | Accelerometer plus speed drop | Set by vehicle weight; trucks use a lower threshold than cars | Optional | Yes |
| Harsh acceleration | Accelerometer plus speed rise | Tuned to the engine and load | No | Yes |
| Harsh cornering | Lateral force from accelerometer | Lower for loaded trucks and buses | Optional | Yes |
| Idling | Ignition on, speed zero | Allowance in minutes, by location | Yes | Yes |
| Out-of-hours use | Ignition or movement outside a schedule | Shift window per vehicle | Yes | Separate report |

Driver ID and multi-driver vehicles
A tracker knows the vehicle; it does not know who is driving unless you tell it. Where one truck is shared across shifts, or a pool car moves between staff, the score would land on the wrong person. HHET solves this with driver identification: each driver carries an RFID card or an iButton key that is tapped at the start of the shift, or enters a PIN on a small in-cab reader. Until the key is read, the platform records the vehicle as unassigned, and you can set an alert, or an immobiliser lock-out where it suits the operation, for movement without a driver logged in. Every event from then on belongs to a named driver, across whichever vehicles he uses that week. For fleets that do not use keys, the platform lets a dispatcher assign drivers to vehicles by roster instead.
Coaching with reports, not blame
Monitoring that only punishes breeds drivers who learn the thresholds. The fleets that see lasting change use the data to coach. The usual routine is a weekly driver league table, with the top and bottom of the list reviewed by the supervisor; a short one-to-one for anyone whose score falls two weeks in a row, using the trip replay to show the event; and recognition, such as a small monthly bonus tied to the score, for those who improve. Managers should tell drivers before monitoring begins what is measured, who sees it and how it will be used, and put that in the driver's written terms. It is fairer, it is better practice for employee data, and it makes the system far less likely to be resented.
Driver data also compounds with other modules. Speed and harsh events sit beside litres per 100 km in fuel monitoring, which shows a driver's real fuel cost per kilometre, and the whole picture comes together in the fleet management system, where driver scores sit beside maintenance and utilisation. Operators who want a figure to take to the owner can read our guide to fleet tracking benefits and ROI.
Saudi notes: speed limits, Saher and TGA
Speed limits in the Kingdom are enforced by the Saher camera network and by traffic patrols, and fines attach to the vehicle's registered owner, which is usually the company. Heavy vehicles and public transport are typically subject to additional speed rules, and where your activity is licensed by the Transport General Authority (TGA), the tracking device is linked to the WASL platform. Confirm the limits that apply to your vehicle class and licence with the authority before setting alert thresholds; HHET can then configure the platform to match.
Practically, a speeding report helps with Saher: you can see which driver was at the wheel when a fine arrives and recover it from the right person according to your own policy. Setting the platform's speed alert a few km/h below the enforced limit gives the driver time to correct before a camera does. Alerts are configurable per vehicle type, so a van on a city street and a loaded truck on the highway are not judged against the same number.
Setting up and pricing
Driver behaviour monitoring runs on trackers with an accelerometer and, for driver ID, an RFID or iButton reader, so HHET checks the units you already have before quoting. Cost depends on the number of vehicles, whether driver ID readers or in-cab buzzers are included, and the subscription term. Request a quote with your vehicle list and tell us which events matter most; HHET will return a configuration and a line-by-line proposal.
Last reviewed .

