Driver behaviour monitoring for Tanzanian fleets
Driver behaviour monitoring turns each trip into evidence: which drivers speed, who pressed the panic button, and when a vehicle moved with its ignition off. Trakora's fleet engine scores drivers on three shipped rules — overspeed, sos and ignition_off_moving — and lets you replay any trip behind an alert.
Driver behaviour monitoring at a glance
- Rules it scores on
- overspeed · sos · ignition_off_moving
- Shipped screens
- /drivers · /replay · /reports
- Speed limit threshold
- —1 configurable, no fixed default
- Alert channels
- SMS · WhatsApp · push
- Panic input
- SOS button raises sos
- Evidence
- Every alert links to trip /replay
- Not shipped as a rule
- Harsh braking / cornering — see honest limits
- Related depth
- sos detail on personal tracking
- Who it's for
- Fleet managers, safety officers, LATRA-regulated operators
The rules that actually fire
Driver scoring is only as honest as the events behind it. These are the three the fleet engine ships — each shown as what fires it, what the manager sees, and what they do next. Nothing here is inferred.
The vehicle went over the configured speed limit
A GPS fix reports a speed above the limit set for that vehicle or zone. The limit is configured per deployment — no single number is hard-coded.
An overspeed alert naming the driver, the vehicle, the speed and the place, plus a running count that ranks drivers by how often they cross the line.
Open /replay to see exactly where it happened, raise it in the driver's file, and use the trend — not one event — for the disciplinary conversation.
The driver pressed the panic button
The driver triggers the panic input in the cab — a hijack, an accident, a medical emergency, a roadblock that feels wrong.
An immediate SOS alert with the vehicle's live position, pushed to SMS, WhatsApp and push so the control room sees it wherever they are.
Call the driver, dispatch help to the live location, and keep the alert as the timestamped record of when the call for help came in. Deeper SOS handling lives on personal tracking.
The vehicle is moving with the ignition off
Position is changing while the ignition line reads off — a truck being towed, rolling on a slope, or an ignition wire that has been defeated.
An alert that separates a genuine drive from a tow or a roll, so a parked truck sliding downhill is not mistaken for a driver on shift.
Treat it as a possible theft or a safety fault, check the live track, and call the yard. On the vehicle-tracking side this same signal is the lead anti-theft alert.
What is deliberately not on this list: harsh braking, harsh acceleration and sharp cornering. The fleet module does not ship a rule for those, so this page does not claim them. Scoring here is built on the three signals above — the ones the engine really evaluates.
The driver leaderboard
Drivers ranked by the events they actually generate this week. Realistic Tanzanian data, not a stock photo.
| Driver | Vehicle | Overspeed | SOS | Ign-off moving | Standing |
|---|---|---|---|---|---|
| J. Mushi | T 412 KCA | 1 | 0 | 0 | Good |
| A. Kimaro | T 208 DKM | 4 | 0 | 0 | Watch |
| S. Mwakalinga | T 519 KDA | 11 | 0 | 1 | At risk |
| H. Juma | T 634 CFT | 2 | 1 | 0 | Watch |
| R. Massawe | T 771 BXA | 0 | 0 | 0 | Good |
The red row is not colour alone — the word At risk carries the state too. Every count is a link into /replay, so an accusation is always one click from the track that produced it.
From a trip to a conversation
Four steps turn raw position data into a fair, evidence-backed talk with a driver.
Set the limits
Configure the speed limit per vehicle or zone so overspeed means your limit, not a generic one.
Drive under watch
Each trip is scored as it happens. Overspeed, SOS and ignition-off-moving raise alerts to SMS, WhatsApp and push.
Rank on the leaderboard
The /drivers view ranks drivers on the events they generate, so attention goes to the real risk, not a hunch.
Replay and review
Open the trip in /replay, confirm what happened, and hold a conversation backed by a track, not a rumour.
What this cannot do
What to expect
- There is no shipped rule for harsh braking, acceleration or cornering. Scoring is built on overspeed, SOS and ignition-off-moving only — anything else would be an invented feature.
- Overspeed reads the GPS-derived speed against a configured limit. There is no single default speed value; the threshold is set per deployment, so no number is stated here as fact.
- The panic button raises an alert; it does not summon emergency services on its own. A human in the control room still has to act on it.
- Behaviour data is only as complete as the position feed. In a coverage dead zone events buffer and backfill, so a score can update after the trip rather than during it.
The — speed-limit value is a figure to be confirmed: the overspeed threshold is configured per vehicle or zone and no default is fixed in the module manifest, so none is published here.
Frequently asked questions
What driver behaviours does Trakora monitor?
Three shipped rules: overspeed, sos (panic) and ignition_off_moving. Harsh braking and cornering are not shipped rules, so they are not claimed.
What speed counts as overspeeding?
Whatever limit you set. The overspeed threshold is configured per vehicle or zone; there is no fixed default, so overspeed always means your own limit.
What happens when a driver presses the panic button?
An SOS alert fires immediately with the live position to SMS, WhatsApp and push, so the control room can call the driver and send help.
Can I prove what happened on a specific trip?
Yes. Every alert links into /replay, so you can watch the exact track that produced the overspeed, SOS or ignition-off-moving event.
Does this help with LATRA compliance?
The overspeed and trip-history data supports LATRA vehicle-tracking-system reporting. The regulatory detail is on the LATRA-VTS compliance page.
More in fleet management
See which drivers are the risk
Tell us your fleet size and routes and we will scope driver behaviour monitoring in TZS, with a VAT invoice and Swahili support.