Skip to content
Company vehicle in Cyprus.

Driver behaviour monitoring in Cyprus

Review the events the tracker and Fleet actually record, with a fair process and a clear privacy purpose.

Know what each event represents

Fleet has alert kinds for speeding, harsh acceleration, harsh braking, harsh cornering, possible crash, towing, unplugging and other vehicle conditions. Some safety events depend on scenarios enabled on the installed tracker. An event is a device observation or a rule result; it is not a finding that a named driver acted recklessly. The usual-driver field is not the same as an iButton key identifying the driver on that trip. Before attributing an event, confirm the vehicle, time, driver identification and device configuration. A speed rule also needs a clearly stated threshold and context for the road and vehicle.

A good review starts from the event and opens the related journey. What was the last valid fix? Did reports arrive late? Was the vehicle in a private trip? Is the alert device-side or server-side? The answer may be incomplete. Fleet lets a manager acknowledge and comment on an alert, but the interface does not turn these events into a driver scorecard. Avoid rankings or claims of measured safety improvement that the code does not support.

Use alerts for coaching with context

Define which alert kinds are enabled and why. Decide which manager receives each one and when an immediate call is appropriate. A possible crash or towing event may deserve fast contact, while repeated harsh movement may be better discussed after checking the route and vehicle. The quiet-hours and recipient settings in Fleet make delivery configurable, but the response procedure belongs to the business. Record what a reviewer checked and what action followed. This prevents an automated label from becoming an unsupported accusation.

Give drivers the policy before monitoring begins. Explain the events, thresholds, who can see them, how long they are kept and how the driver can challenge an incorrect assignment. The Cyprus Commissioner’s proportionality approach and the EU workplace-monitoring opinion (WP249, non-binding guidance) support assessing necessity before rollout. Private mode and scoped permissions help enforce the policy, but neither by itself supplies a purpose. If a business cannot articulate why a particular alert is needed, leave that rule off.

Sources: [2][3]

Do not turn sparse data into a score

A vehicle may be shared across shifts. A driver may be assigned by a usual-driver field when no key event identifies the person. Reception may be interrupted at the moment of a manoeuvre. A simple count of alerts across drivers would ignore distance, route, vehicle condition and how the tracker was configured. Fleet does not provide a scorecard or ranking. Use individual events with their supporting records and state uncertainty plainly. When evidence is thin, the fair outcome is further review or no conclusion.

Set thresholds with an explanation

A speed threshold or long-idle rule should be stated in units the team can understand, applied to the intended vehicles and reviewed after a pilot. A notification without an owner can quickly become background noise. For harsh movement, confirm that the device-side scenario is enabled, then test how the event appears in Fleet. Do not advertise a safety event solely because the tracker hardware can theoretically detect it. The installed configuration and receiving service determine what a manager can actually review.

Different vehicles and routes have different contexts. A loaded van braking on a steep road and an empty van in a depot should not be judged through an unexplained event count. Review the full trip and timestamp, ask what happened and document the answer. If a device was transferred or reconfigured, establish the date of that change before comparing events across periods. A threshold is a prompt for a consistent review, not a verdict.

Do not overstate who was driving

Fleet can display a driver identified by an iButton key or the usual driver assigned to a vehicle. A shared van may have a usual-driver name even when another employee has the keys. For any event that may affect a person, check the source of the identity and the work roster. If the driver cannot be established reliably, keep the event attached to the vehicle and mark the person unknown. An inaccurate personal attribution can be more harmful than omitting the name.

Make the handover process workable for drivers. If a physical key is part of identification, explain when it must be used and what happens when it is missing. Test a shift change and a shared vehicle during rollout. A manager should see the difference between a recorded key event and a default assignment without opening a technical log. That distinction is essential to a fair coaching conversation.

Give staff a chance to understand and challenge data

The employee notice should describe which driving events are collected, why, who receives alerts and how long records are retained. It should also explain how a driver reports an incorrect vehicle assignment or an event caused by equipment trouble. Articles 5 and 13 GDPR set out purpose, data minimisation and transparency duties toward the people affected, while EU workplace guidance (WP249, non-binding) warns against treating consent as an easy answer to monitoring. An employer should assess these questions before turning rules on, not after the first complaint.

Consider the difference between an urgent safety call and a later pattern review. The first may justify prompt contact based on a possible incident; the second needs careful context and a chance for the person to respond. Fleet records acknowledgement and comments on alerts, which can support that process. It does not decide the outcome. Keep any disciplinary decision outside the automatic alert path and within the organisation’s normal procedure.

Sources: [1][3][6][7]

Use a review sheet instead of a scorecard

For each event, record vehicle, recorded time, alert kind, identity source, route context, device state, the reviewer and the driver’s explanation. Mark facts separately from interpretations. A possible crash is a possible crash until someone verifies what happened. A no-signal period is not a jamming finding. If the record is incomplete, choose “needs follow-up” or “unresolved” instead of filling gaps with a plausible story.

Review the rules periodically. If one threshold produces many harmless alerts, narrow it or turn it off. If a driver disputes a record, inspect the original report and assignment rather than only the notification text. Fleet has no ranking or safety score, so this process centres on individual events and fair examination. That is enough to make alerts useful without claiming a measurement the product does not provide.

A fair review of one driving event

Suppose Fleet shows a harsh-braking alert. First confirm the installed device scenario was active and the alert rule applied to this vehicle. Open the original time and nearby route, noting any missing fix or delayed reports. Then check who the driver field represents: a key identified on the trip or a usual assignment. A shared van makes the latter uncertain. These steps establish what the system actually observed before anyone interprets it.

The reviewer then asks for context. A pedestrian, a blocked road, weather or a mechanical problem may explain sudden braking; the alert itself cannot distinguish them. Record the explanation and any follow-up, such as checking the vehicle or discussing a repeated pattern. If evidence is incomplete, keep that uncertainty in the outcome. Do not create a rank or score from an event count without a contextual measurement. Fleet does not provide a driver scorecard.

Before the rule is used again, ask whether its threshold and recipient were right. Did the message reach someone who could act? Did quiet hours delay a non-urgent event appropriately? Was a private trip handled without exposing location? A rule that repeatedly generates harmless alerts should be narrowed or disabled. This is a safety process with human review, not an automatic personal judgement.

Keep a short review record for each event that matters: the tracker state, original time, rule, identification source and the person who checked it. A later reviewer should be able to see which facts came from the device and which came from a conversation. If the key identifying the driver was absent, do not silently replace it with the usual driver. The uncertainty belongs in the record and in any decision built from it.

What a harsh-braking event measures

The FTC164 eco-driving scenario can use its accelerometer or speed and heading changes. Teltonika lists default thresholds of 2.5 metres per second squared for acceleration, 2.7 for braking and 3.4 for cornering, with speed above 10 km/h and a half-second duration. The scenario is disabled by default, so a fleet must confirm the installed configuration before interpreting a missing event. A firm mount and calibration matter because a loose unit can alter the measured axes.

Fleet can alert on harsh events and show them for review. It does not calculate a driver safety score. The tracker also produces a crash event and can buffer a high-rate crash trace. Fleet sends a crash alert with summary values, but does not store or draw the waveform for reconstruction. Ask for the trace separately if that level of analysis is required, and do not treat an alert as proof of fault.

Identify the person before attributing the event

A shared van needs an identity event if managers want to attribute a journey to one driver. Fleet registers iButton keys and can show the identified driver in the live view. A usual driver assigned to a vehicle is a different, weaker fact. The FTC164 can also use Bluetooth devices or RFID in device scenarios, but Fleet does not currently provide the same driver identification flow for those keys. Verify the actual key method and a handover between shifts before using the alert history for coaching.

Sources

  1. Cyprus Law 125(I)/2018
  2. Cyprus DPC Opinion 2/2018
  3. Article 29 Working Party Opinion 2/2017
  4. GDPR Article 35
  5. GDPR Article 88
  6. GDPR Article 5
  7. GDPR Article 13
  8. Article 29 Working Party Guidelines on Data Protection Impact Assessment (WP248 rev.01)
  9. EDPB Opinion 10/2019 on the Cyprus draft list of processing operations subject to a DPIA
  10. Teltonika FTC164 features
  11. Teltonika FTC164 system settings
  12. Teltonika FTC164 Bluetooth

Frequently asked questions

Does Fleet rank drivers?

No. Fleet has no driver scorecard or ranking; it presents alert events for review.

Does a harsh-braking alert prove fault?

No. Check the trip, the device configuration, vehicle and road context, and the driver assignment.

Can alerts reveal private locations?

Fleet stores private trips without position. Test the privacy flow and alert display for your installation.

Discuss your fleet requirements

Ask for a quote based on your vehicles and operational needs.