Getting started
Driiver answers one question your telematics cannot: who was driving. A driver scans the QR sticker in the cab, and from that moment every trip carries their name. Everything else in this portal is built on top of that one fact.
MyGeotab is the source of truth. The portal never invents a person or a vehicle. If someone is archived in MyGeotab they disappear from here and lose access on the next sync — you do not need to remember to remove them.
Your first fifteen minutes
- Sign in at
driiverapp.com/portalwith the email your account was created under. - Check the roster. Open Drivers. Everyone active in MyGeotab is already listed — you do not add people here.
- Turn on access for the drivers who should use Driiver. Each gets a six-digit activation code.
- Print the cards and stickers. Driver cards from Drivers, vehicle stickers from Vehicles & stickers. One sticker per vehicle, somewhere the driver can reach from the seat.
- Run one-click setup in Scoring rules — it seeds the behaviour catalogue, maps your rules, backfills events and computes first scores. Then tune weights per rule — see Scoring rules.
- Wait for miles. Scores appear once a driver has enough driving to be judged fairly.
Dashboard
The morning screen. Designed so you can read the top third and know whether today needs you.
Fleet safety briefing
Your greeting, the fleet safety score, and a short list headed Start here this morning. That list is not a feed — it is ranked by what would move the fleet number most, and each item says what it is worth in points. Below it, Insights read patterns out of your own data: risk concentration, recoverable ceiling, behaviours becoming habits, and the spread between your best and worst driver.
Everything there is computed from your numbers and your weights. Nothing is forecast, estimated, or filled in with zeros.
The four tiles
| Tile | What it means | What to do |
|---|---|---|
| Attribution rate | Share of trips with a verified driver. The number Driiver exists to move. | Below 90%? Find who is not scanning — Unattributed trips names the vehicles. |
| Drivers activated | How many have finished setup, out of your active roster. | Chase the outstanding codes. An unactivated driver is an unattributed trip waiting to happen. |
| Unattributed trips | Trips in the last 7 days that drove without a badged driver. | One or two is normal. A pattern on one vehicle usually means a missing or damaged sticker. |
| Scans today | Today's sign-ins and the time of the first one. | A quick pulse check that the morning went normally. |
Below those: Attribution rate — last 7 days as a daily trend, and the Unattributed trips list itself. At the bottom, codes outstanding, vehicle count, and last sync time.
Attribution, unattributed trips and scans are not yet computed for live fleets — they show as dashes with the reason written on them. This is deliberate. See Sections that are deliberately blank.
Drivers
Your roster, synced from MyGeotab, plus the one thing you control: who has Driiver access.
| Status | Meaning |
|---|---|
| Activated | Set up and scanning. Trips carry their name. |
| Code issued | Card printed, not yet activated. Chase these. |
| No access | Access is off. They can drive; trips just will not carry a name. |
| Archived | Archived in MyGeotab. Access and any live session are revoked on the next sync. |
Activation codes are six digits and single-use. Reissuing one invalidates the previous card.
Driver scores
The screen you will use most. Drivers see exactly these numbers in their app — there is no separate version for management, which is what makes the conversation possible.
How the score actually works
Every driver starts at 100. Each coachable event deducts its rule's weight — the price you set per event per 100 work miles — times a repeat multiplier when the same behaviour recurs within a work week. Clean driving earns some back.
100 − Σ(weight × repeat multiplier) × 100 / max(work miles, 100) + clean-streak credit = score
| Mechanic | How it behaves |
|---|---|
| Rolling 30 days | The window moves every day. Nothing waits for a month to end; an event simply ages out at day 31. |
| Burst collapse | Exceptions inside a behaviour's cooldown are one event with sources. Three hard brakes at one intersection are one conversation, not three deductions. |
| Worst wins | When several rules fire on one event, only the heaviest enabled rule is charged. Overlapping rules never double-bill. |
| Repeat multiplier | The 2nd event of a behaviour in a work week costs ×1.5, the 3rd and later ×2 — capped there, reset every Monday. |
| Evidence floor | Deductions are per 100 work miles on max(miles, 100), so a handful of yard moves cannot blow up a score. |
| Earned back | A 30-day clean streak with 500+ miles credits +2. Clean miles also dilute the rate on their own. |
| Two scores | Work hours (Mon–Sat 06:00–18:00, editable) and after hours are scored separately; the work score ranks. |
| Attribution | Only trips the driver was signed into count. A shared truck never charges someone for another person's driving. |
| Mileage floor | Under 100 miles a driver is tagged low mileage and leaves the ranking — not ranked last; under 20 miles the tile shows —. New drivers spend 14 days in a baseline window, scored but unranked. |
Bands: 80–100 good 60–79 fair below 60 needs work — the same cut lines on every Driiver fleet.
Reading the screen
Score leaders sits at the top — the top three, as an honour roll, with a 7-day / 30-day / since-activation toggle. The score itself is a rolling 30-day number; it is not a monthly leaderboard. Ties break toward the cleaner record: fewer events, then more miles.
Then four tiles:
01Fleet safety score — the average of every qualifying driver, with a note on how many sit below 60. The purple box tells you the recoverable ceiling: where the fleet would sit if every driver cleared only their single worst behaviour.
02Behaviours to correct first — every behaviour ranked by share of the fleet's total deduction, not by how often it happens. Frequency is not cost.
03Top performing driver — your leader, with their events consolidated by behaviour and what they earned back.
04Driver needs attention — the lowest qualifying driver, events consolidated most-broken-first, and what clearing the top one alone would do to their score.
Below the tiles, the stack rank — sortable by score, events per 100 miles, miles or top behaviour. Click any row for detail. Unqualified drivers are listed separately underneath.
Events per 100 miles, not event count. A driver doing 3,000 miles a month will always out-event a driver doing 600. Rate is the fair comparison.
Driver detail
Click any driver. This is the screen to have open during a coaching conversation.
- Header — score, rank, miles and the window it covers.
- Metric row — events, events per 100 miles, idle hours and estimated idle cost.
- Score trend — the daily line.
- Events — what happened, with dates.
- What cost points / What earned back — the itemised breakdown. Repeats, stacked and capped deductions are all labelled, and clean miles since each behaviour last fired are shown.
- The bottom line — the arithmetic, spelled out: baseline, deducted, earned back.
The itemised rows sum exactly to the deduction total. If a driver challenges their score you can walk the arithmetic line by line — and that is the whole point. A number nobody can explain is a number nobody accepts.
Vehicles & stickers
Every tracked asset from MyGeotab, each with a QR sticker and a printed fallback code for when a camera will not focus.
Regenerating a sticker immediately revokes the printed one. Only regenerate when a sticker is damaged, stolen, or the vehicle changes hands — and print the replacement before you do it.
Archived or untracked assets never appear here.
Scoring rules
Rules come from MyGeotab. Weights, thresholds and routing are yours.
Each synced rule carries an On switch and a weight — switch a rule off and it produces nothing at all: no deduction, no coaching lane, no streak break. After one-click setup, scoring rules arrive on, priced from the behaviour catalogue; engine and vehicle-condition rules are shown but never scored — they describe the truck, not the driver.
The catalogue is six behaviour categories: Collision · Speeding · Seatbelt · Phone Use · Distraction (eating, drinking, smoking, fatigue) · Harsh Driving (braking, acceleration, cornering, rolling stops). Every rule points at one of them — pick it right on the row. The behaviour carries the coaching columns, shared by every rule mapped to it: First event → (where the first event lands — keep watch, self coach, or coach now), Self coach at and Coach now at (absolute event counts in a 30-day window). A rule left unmapped is skipped honestly — its events never score and never coach until you map it.
Setting weights sensibly
- A weight is a price: the points one event costs per 100 work miles. The catalogue runs 0.25 (idling) to 20 (collision) — roughly doubling per step of severity.
- Overlapping rules never double-bill. If "Speeding" and "Speeding Over 90" both fire on one event, only the heaviest enabled rule is charged — so enable as many tiers as you like and price them differently.
- Start from a preset (Balanced is the shipped catalogue), then tune any number by hand.
- Weight changes take effect on the next scoring pass. No deploy, no downtime.
Settings
| Setting | What it does |
|---|---|
| Auto-release | Time of day sessions close automatically, so a driver who forgets to sign out does not carry a truck overnight. |
| Takeover | What happens when a second driver scans a vehicle someone is already signed into. |
| Drivers can see their rank | Off makes the score private to each driver. Some cultures thrive on the leaderboard; some do not. You choose. |
A session ends on sign-out, on takeover, at auto-release, or when MyGeotab says the driver is archived. There is no silent timeout — a driver is never dropped mid-shift.
Resources, in the sidebar, opens this guide, the driver walkthrough, the driver workflow, the sticker maker, and the legal documents. Available to every role.
Sections that are deliberately blank
Some panels show a grey card naming what is missing instead of a number. That is a choice, not a bug.
A chart drawn from data we do not have is worse than no chart. If a panel cannot be computed honestly it says so, and says what it is waiting on. Nothing here is ever zero-filled to look complete.
| Panel | Waiting on |
|---|---|
| Attribution rate, unattributed trips | The trip watcher — daily comparison of trips against verified drivers. |
| Scans today | Scan event logging. |
| Score trend, score change indicator | Daily score history. The snapshot currently holds one current row per driver, so there is no yesterday to plot. |
| Idle hours, idle cost | Idle data is not yet in the scoring snapshot. |
| Coaching | Not built. The tab and the Coach this driver button are the hooks for it. |