Driver management software for Malta fleets, and the points that change habits
The driver record, then a reason to improve it
Three months into scoring, the same two names sit at the bottom of the weekly report and the coaching chat has stopped landing. This is what comes after that.
Profiles and status
Name, employee ID, hire date, emergency contact and medical notes. Status decides the rest: only an active driver can be assigned a vehicle.
Vehicle assignments
Assigned by hand, or automatically when a beacon or iButton is read at the start of a trip. Vehicle, start date, end date and source stay on the record.
Documents with expiry
Licence copies, forklift and HGV certificates, medical clearance, training records. Yipii warns you before one lapses.
Points and rewards
A ledger per driver, fed by trip scorecards, badges and challenges. Points come off the same ledger when a reward is redeemed.
One record per driver, and it survives the leaving date
A driver profile holds the personal and employment detail, the emergency contact and the medical note, plus every vehicle that driver has ever been assigned to. Status does the rest of the work. Active drivers can be assigned and picked up by automations, while inactive, suspended and terminated drivers keep their history without appearing in either. Nothing is deleted to tidy up a list, which matters the day an insurer asks who was driving in March.
- Four statuses: active, inactive, suspended, terminated
- Assignments record the vehicle, start date, end date and source
- Automatic assignment when a BLE beacon or an iButton is read at trip start
- Licence copies, certifications and medical clearance with expiry alerts
Included with Yipii Mobility, the add-on that extends your IoT account. One subscription covers everything in the app, so no feature here is sold on its own. What Yipii Mobility includes
The weekly grade, next to the fleet average
Grades land weekly and monthly, on an A to F scale, and the fleet average sits beside each one so a C is a position rather than an opinion. Underneath are the counts that produced it (harsh braking, rapid acceleration, hard cornering and speeding) and the five component scores. A trend chart per driver shows the direction of travel, which is the part that ends the argument about whether someone has improved.
- Weekly and monthly letter grades, A to F, against the fleet average
- Component scores for acceleration, braking, cornering, speed and eco
- The harsh-event counts behind every grade
- Trend chart per driver, week on week
Every point has a row and a reason
Five things write to the driver ledger. A total is the sum of those rows, so every number on the leaderboard traces back to the trip, the badge or the adjustment that produced it.
Trip scorecard
A completed trip produces a scorecard, and the safety score on it decides the points. Trip points are positive only, so a bad week costs a driver the chance to earn rather than taking points back.
Badge award
Every badge carries its own points reward, paid the first time the driver crosses the threshold and never again.
Challenge payout
The weekly challenge pays out on completion, once the driver has met the target you set for that week.
Reward redemption
Spending points writes a negative row for the cost of the item. That is the whole mechanism, there is no separate wallet to reconcile.
Manual adjustment
An admin can add or remove points by hand, for the Saturday callout that no trip captured. It lands as a row like any other.
The ledger only ever gains rows. A correction is a negative entry rather than a quiet edit, and running the same scorecard through twice does not pay a driver twice. That is the audit trail, and it is also the answer when someone asks why their total moved.
Small targets, earned once, worth chasing
Badges are set up per account against five criteria: days on a streak, points total, safe distance in kilometres, challenge wins, and a perfect week. Each one has a threshold and its own points reward, and each one is earned a single time. Streaks count qualifying days and reset when a driver misses one, with the all-time best kept alongside the current run so a good streak stays on the record after it breaks. One challenge runs at a time, built from a goal, a metric and a target, twenty trips in the week being the shape of it.
- Five badge criteria: streak days, points total, safe distance, challenge wins, perfect week
- Current streak and all-time best, tracked separately
- One active weekly challenge, with progress tracked per driver
- Badges and completed challenges pay straight into the ledger
Points come out the same way they went in
The leaderboard ranks every driver in your account by total points earned, computed from the same ledger rows. The rewards catalogue is yours to write: a name, a description, a points cost, a stock count that you can leave empty for unlimited, and an active flag to take an item out of circulation without erasing what people already redeemed. When a driver redeems, Yipii checks the balance and the stock, writes the negative row, drops the stock by one and creates a redemption record for you to fulfil.
- Leaderboard across your whole account, ranked on total points earned
- Catalogue items with points cost, stock count and an active flag
- Redemptions land as negative ledger rows, never as edits
- A redemption record per claim, so fulfilment is not settled on trust
What this does not do yet
One challenge at a time, and it is set up admin-side
Badges, the rewards catalogue and the weekly challenge are configured by an admin or a fleet manager. Drivers see the results, they do not create them, and there is no self-serve builder in the driver view.
Only one challenge can be active in your account at a time, so each week runs on a single goal rather than several competing ones.
We will not invent a rewards list for you
What the catalogue holds is your decision. Our documentation gives gift cards, time off and merchandise as the kind of item it is built for, and the points cost against each one is yours to set.
We are not going to dress up a Malta fleet that is already running one. Build the first catalogue with us on the call instead, priced against a budget you control.
Frequently asked
The mechanics, mostly. Every point is a row in the driver ledger with a source attached: a trip scorecard, a badge, a challenge, a redemption, or a manual adjustment by an admin. A driver total is the sum of those rows and nothing else, so there is no balance sitting somewhere that can drift. The ledger only ever gets new rows, which means a correction is a visible negative entry rather than a quiet edit, and reprocessing the same scorecard does not pay twice. Trip points come from the safety score itself, so the only way to earn more per trip is to brake and corner better. One thing to watch: points accumulate per trip, so a driver who is out on the road more has more chances to earn, and the leaderboard ranks on total points earned. Badges and the weekly challenge are where you balance that, because a perfect week or a streak is available to a driver doing four runs a day and one doing eight.
Yipii does not charge you for redemptions, and there is no reward we supply. The catalogue is yours to write: you name each item, set its points cost, set a stock count or leave it unlimited, and switch it off with the active flag when you want it out of circulation without deleting the history. Whatever an item costs you is whatever you decided to put in it, and fulfilment happens on your side once the redemption appears. Yipii Mobility itself is quoted per fleet rather than published as a price list, so talk to our Malta team and we will scope it against your driver count.
A driver sees their own scorecard and their own points summary, plus the leaderboard and the active challenge. They cannot open another driver safety card. Admins and fleet managers see every driver, which is the split most operators want: the ranking is visible to everyone, the individual coaching conversation stays private.
For scorecards and trip points, yes. A scorecard needs at least one completed trip recorded by a GPS tracker on the vehicle, so a driver with no trips has a profile but no grade and no trip points. The rest of the driver record works without any hardware at all: profiles, statuses, assignments, documents and expiry alerts are yours from day one. Badges, challenges and manual adjustments also work without trip data, they just have less to feed on.
By carrying an identifier the tracker can read. A BLE beacon or an iButton linked to the driver is picked up when a trip starts, and Yipii writes the assignment with the source recorded as automatic. That is how a van shared across three shifts on the Msida to airport run ends up with the right name against the right trip, without a dispatcher keying anything in. The tags themselves are configured on the IoT side and shown read-only on the driver profile.
Scoring, tags, licences and hours
Attribution is the part most fleets get wrong first, and it is covered under driver ID and auto-assignment, with the shared-van version of the problem written out on the delivery and courier page. The field-by-field detail behind everything above lives in the drivers guide and the driver gamification guide in the Yipii Mobility docs.