Hey, everyone!

We’ve released Driver App Version 6.9.1 on Friday, November 7, 2025.

Geofence validation, Fairmatic Integration Enhancement

This release includes important enhancements that improve trip integrity, reduce false no-shows, and give dispatchers better visibility into driver actions.

Geofence Validation for Trip Actions

To improve accuracy and prevent false no-shows, the Driver App now verifies the driver’s location before allowing key trip actions.

How it works:

When performing actions like Start Run, Arrived at Pickup, Passenger On Board, Arrived at Destination, Passenger Off Board, the app checks if the driver is within 100 meters of the location.

If not, the driver will see a warning message that allows them to:

• Back — return to the previous screen, or
• Bypass — continue the action if necessary

This ensures location-based actions are accurate, while still allowing flexibility when needed.

Bypass Tracking for Trip Integrity

Every time a driver chooses to bypass the geofence warning, the system automatically records the event.

What gets logged:

Timestamp of the bypass

Driver and tenant

Expected vs. actual GPS location

This ensures clear traceability and supports audit, compliance, and operational visibility.

Configuration / Enablement

Geofence enforcement is off by default.

To enable it for your account, send a quick email to:help@tobicloud.com

Prevent Duplicate Period Events During Active Runs (Fairmatic Integration)

This release introduces improved event-handling logic for the Fairmatic integration, ensuring that duplicate “Period Start” events are not triggered while a Fairmatic period is already active. These enhancements strengthen data integrity between the Driver App and Fairmatic’s backend, maintaining accurate trip event synchronisation.

Key Highlights

Single Active Period Validation:

The system now enforces a single active Fairmatic period at any given time. If a new “Period Start” event is attempted while another period is active, the system prevents the duplicate event from being sent to Fairmatic

• Run Start Event Logic
  • The Run Start event now triggers only once — when the driver begins a run.
  • Additional P2 triggers during the same run are automatically suppressed.
  • Prevents redundant start signals and ensures consistent trip state reporting.
• First Passenger Pickup Event Logic
  • The First Passenger Start event now triggers only once when the first passenger is onboarded during a run.
  • The app prevents duplicate events even if multiple passengers are picked up subsequently.
  • Guarantees Fairmatic receives a single, accurate transition from “pickup” to “in-transit.”
• Run End Event Handling
  • Upon completion of the run, the app now sends a single “Stop Period” event.
  • This marks the official end of the active Fairmatic period and finalizes the event lifecycle for that run.
  • Ensures clear boundaries between runs for Fairmatic event tracking.

As always, thank you for your feedback. You help us build a better TOBI experience.