bugama
Bugama FleetsThe ERP for drivers, vehicles, workshop and settlements.Bugama DriverThe app for your drivers, on iOS and Android.Bugama CompliancePlanned shifts vs. real activity, every single day.Bugama GPSTelematics powered by Wialon, inside Bugama.AI & AgentsDemand forecasting, event radar and agents at work.
Bugama OSCustomers
Our visionThe team, and why we build Bugama.Case studiesHow operators run on Bugama today.ResearchOur white paper on demand forecasting.About BugamaWhat we build and what we believe.Help centerFeatures, definitions and guides.Book a demo30 minutes with our team.
ENES
Bugama Fleetsfleets.bugama.comBugama Compliancelabs.bugama.com
Request a demo
bugama

Bugama is the operating system for ride-hailing fleets: drivers, vehicles, shifts, compliance and money in one place, with AI agents doing the repetitive work.

All systems operationalhello@bugama.com

Products

  • Bugama Fleets
  • Workshop
  • Recruiting
  • Settlements
  • Bugama Driver
  • Bugama Compliance
  • Bugama GPS
  • AI & Agents

Bugama OS

  • The vision
  • Vehicle inspection
  • Energy & charging
  • Passenger care
  • All eight services

Resources

  • Case studies
  • Help center
  • Research
  • Glossary
  • System status

Company

  • Our vision
  • About Bugama
  • Book a demo
  • Contact
© 2026 Bugama. All rights reserved.
ENESHosted in the EUPrivacyTermsCookie policy
Home/Products/Bugama Compliance
Bugama Compliance

Know what happened on every shift. Every day

Bugama Compliance compares the shift you planned with what really happened on the platform and on the road. Then it gives every driver clear, fair feedback, automatically.

Request a demoHow it works
Shift compliance · Madrid · Tue 14 Oct
DR
Driver 4471
Corolla 1187-MZX · Shift LM2 · 07:30–19:30
2 checks failed
Peak
Peak
Planned
Real
08:14 · +44 min
06:0009:0012:0015:0018:0021:00
!Late arrivalFirst movement 08:14limit 30+44 min
!Revenue zones (RZI)312 of 420 min74%
✓Peak hours offline12 min in 18:00–20:00limit 3012 min
✓Eco-drivingWialon eventslimit 62 harsh
Next actionSMS sent at 21:32. If it repeats tomorrow, the voice agent calls.
How it works

From live states to a message on the driver’s phone

Four steps run every day for every driver, without anyone opening a spreadsheet.

01Live monitor

Watch every driver, live

The live monitor reads every driver’s state from the platform every few seconds (offline, waiting, going to a pickup, on a ride) together with orders and GPS. New drivers and cars are discovered automatically.

Live monitor · all companies
02Driver timeline

Rebuild each shift as a timeline

After the shift, Bugama reconstructs the day: planned start and end, the first real movement of the car, platform states, orders, earnings, kilometres and minutes inside revenue zones.

Shift compliance · Madrid · Tue 14 Oct
DR
Driver 4471
Corolla 1187-MZX · Shift LM2 · 07:30–19:30
2 checks failed
Peak
Peak
Planned
Real
08:14 · +44 min
06:0009:0012:0015:0018:0021:00
Next actionSMS sent at 21:32. If it repeats tomorrow, the voice agent calls.
03Rules engine

Check it against your rules

Each fleet manager turns on the checks that matter and sets the limits per city. The same engine runs for every driver about two hours after the shift ends.

Rules · Fleet manager settings
Late arrival
First movement ≤ 30 min after shift start
All cities
Revenue zones
≥ 420 min inside high-revenue areas
Madrid
Peak hours
≤ 30 min offline in city peak windows
Madrid · Murcia
Cancellations
≤ 3 driver cancellations per shift
All cities
Eco-driving
≤ 6 harsh events per shift (GPS)
All cities
Geofence time
Airport queue ≤ 90 min
Madrid
04Feedback

Tell the driver, the same day

Drivers receive a clear message with the facts. If it happens again, a voice agent calls them. The best earners are left alone, so feedback lands where it helps.

Feedback to drivers · automatic
Same evening · SMS

“Hi Daniel, yesterday your LM2 shift started 44 min late and you spent 312 of 420 minutes in revenue zones.”

Same evening · Email

The full timeline of the shift, with the rule, the target and the result for every check.

If it repeats · Voice agent

“I can see it happened again today. Is something stopping you from starting on time?” The answer is logged.

Top 10% earners · No message

Drivers in the top decile of their city are exempt. Good results are not interrupted.

Live monitor · all companies
Shift compliance · Madrid · Tue 14 Oct
DR
Driver 4471
Corolla 1187-MZX · Shift LM2 · 07:30–19:30
2 checks failed
Peak
Peak
Planned
Real
08:14 · +44 min
06:0009:0012:0015:0018:0021:00
Next actionSMS sent at 21:32. If it repeats tomorrow, the voice agent calls.
Rules · Fleet manager settings
Late arrival
First movement ≤ 30 min after shift start
All cities
Revenue zones
≥ 420 min inside high-revenue areas
Madrid
Peak hours
≤ 30 min offline in city peak windows
Madrid · Murcia
Cancellations
≤ 3 driver cancellations per shift
All cities
Eco-driving
≤ 6 harsh events per shift (GPS)
All cities
Geofence time
Airport queue ≤ 90 min
Madrid
Feedback to drivers · automatic
Same evening · SMS

“Hi Daniel, yesterday your LM2 shift started 44 min late and you spent 312 of 420 minutes in revenue zones.”

Same evening · Email

The full timeline of the shift, with the rule, the target and the result for every check.

If it repeats · Voice agent

“I can see it happened again today. Is something stopping you from starting on time?” The answer is logged.

Top 10% earners · No message

Drivers in the top decile of their city are exempt. Good results are not interrupted.

Explained · shift groups

How a 12-hour, two-driver car is planned

Most salaried fleets in Madrid share each car between a morning and an afternoon driver, in 12-hour shifts. Drivers are organised in groups by their two rest days, and each group has three staggered start times so cars don’t all change hands at once.

  • Groups (LM, MX, XJ, SD) define the rest days. Bugama knows who should be working on any day.
  • Slots stagger the start, so the real start of each driver is measured against their own plan.
  • Other cities, like Pamplona, use different windows. Each one is configured separately.
Shift groups · Madrid
MonTueWedThuFriSatSun
LMrestrest
MXrestrest
XJrestrest
SDrestrest
Slot 107:00 – 19:00
Slot 207:30 – 19:30
Slot 308:00 – 20:00

Morning and afternoon drivers share each car. LM2 morning starts at 07:30, LM2 afternoon at 19:30.

Guardian

Catch the trips that nobody planned

Every night Guardian compares GPS movement with platform activity. When a car moves and no authorised driver is working, or a cash ride is cancelled and the car still leaves with the passenger, it opens an incident for review.

  • Four detection patterns, tuned with real fleet incidents.
  • Evidence attached: route, times, platform states and the driver on shift.
  • Review queue for the operations team, with the history of each car.
Guardian · last night
DEPOT
03:12 · 1187-MZX5.2 km driven · no driver online
Phantom trip

Car moves with no driver online on any platform

Unauthorised use

Movement outside the driver’s shift or by someone else

Cash-cancelled ride

Cash ride cancelled, then the car leaves with the passenger

Base return

Unplanned trips back to base during working hours

Productivity

Euros per hour, by driver, group and city

Because every shift is measured the same way, productivity becomes comparable. Operators see the gap between shifts that follow the rules and shifts that don’t, and use it to coach drivers and adjust the roster.

  • Earnings per hour from platform data and real working minutes.
  • Weekly reports by email to each manager, in Excel.
  • Market studies: supply and waiting time by hour, compared with other fleets in the city.
Read the A Coruña study
Productivity · € per hour · example view
Shifts that met the rules Shifts that did not
24.1
19.6
LM
23.4
18.2
MX
22.8
19.1
XJ
25.3
20.4
SD

Compliance in practice

All case studies
LM · MX · XJ · SD SHIFT GROUPS
Compliance · Madrid

Turning shift rules into daily feedback for every driver

Late starts, time in revenue zones and peak-hour availability are measured for every shift, and drivers hear about it the same evening.

Read the story →
SUPPLY VS DEMAND · BY HOUR
Market study · A Coruña

Finding the afternoon hours when a third of the city waits

Live data across nine fleets showed 35–38% of cars parked in the afternoon versus about 20% in the morning, so the roster could change accordingly.

Read the story →
8 CITIES · 90 COMPANIES · 1 RECORD
Payroll fleet · Spain

One system for ~1,000 drivers, 90 companies and 8 cities

A Spanish operator with salaried drivers moved hiring, rosters, workshop, damage claims and payroll inputs out of spreadsheets and into one shared record.

Read the story →
FAQ

About Bugama Compliance

Which data does Compliance use?

Driver states and orders from the platform’s fleet tools, GPS from Bugama GPS (Wialon), and the shift plan from your roster or spreadsheet. Everything is matched by driver, car and time.

Can each city have different rules?

Yes. Each check is configured per fleet manager and can be limited to specific cities, with its own thresholds. Peak hours and shift groups are defined per city too.

What happens when two drivers share a car?

Morning and afternoon drivers on the same plate are separated automatically: GPS kilometres and activity are split by shift, so nobody is measured on the other driver’s hours.

Is it fair to drivers?

Every message contains the facts behind it (times, minutes and targets), and the full timeline is available on request. Top performers are exempt from messages, and repeated issues go to a conversation, not a penalty.

Get started

See yesterday’s shifts, measured

Show us how your operation works today. In 30 minutes we will show you what Bugama would measure, automate and simplify from the first week.

Request a demoRead the case studies