A login is Geotab's UserLogin record in the Audit log — the same records MyGeotab's Audit log shows. Geotab writes the same record for a MyGeotab web, Geotab Drive or API sign-in (only the user name is in it), so integrations are left out by account (see "Who is listed"). Failed attempts, lock-outs and logoffs are not logins. Days are whole days on your MyGeotab time zone, up to yesterday: today is never complete, so a range ending today stops at yesterday and the page says so. A range can start at most 2 years back. The page runs by itself when you open it, with the last range you used (30 days the first time); change the dates and press Run to update.

A login 2 seconds or less after the same user's previous one is the same sign-in: it is merged into it, and the list shows "+N merged" (the ranking draws them hatched). A user is marked Machine-like when at least 10 of their logins are such repeats and they make up a quarter or more of their logins — software signing in under a person's account. Their logins still count.

Red = no login in the dates you ran, whatever they are (7 days, 3 months, a year): the user didn't sign in at all, an unused licence to review. The user's panel still says when they last signed in (the 12 months up to yesterday are looked at; "Not in 12 months" when there is none). Everyone who signed in is neutral. There is no amber.

Every user whose account was active at some point in the dates — one archived during them is kept, marked Archived; one added during them is marked New in range. Driver = set as a driver in MyGeotab. Hidden: addresses ending in @et-envue.com, @geotab.com and @emkay.com, MyGeotab service accounts and accounts with "api" or "integration" in their user name (before the @). Not listed: records with the "Nothing" clearance — they can't sign in (driver records, mostly); the tag in the header ("N can't sign in") opens a panel that names them.

A night-time sign-in is a login between 00:00 and 05:00, always on your MyGeotab time zone (not each user's own).

The dark panel shows the share of users who signed in on a gauge, with the counts that need a decision beside it — No login in these dates and Machine-like, click one to filter the list — and every user ranked by logins (Top 10 or Top 20). Below it: Longest not seen (the users with no login in the dates, longest since their last login first), By clearance (who signed in per security clearance — click one to list its users), Sign-ins per day (one bar per Monday-first week when the dates run over 90 days; click a bar to list who signed in that day or week) and Unusual sign-ins (machine-like accounts and night-time logins). The cards and the ranking describe the whole run; the list below follows the filters you choose.

Click a user for their panel, docked beside the list (it covers the page on a narrow screen; ← → step through the list, Esc closes): their figures, a calendar of the dates (darker = more logins that day), when in the day they sign in, their logins in each of the last 12 months and their 20 most recent sign-ins.

Report downloads exactly what the list shows — its tab, status, clearance, day, unusual and search filters, in its order — plus a Sign-ins sheet, the Top 10, the records not listed and these rules. It is built from the last finished run.

Utilization = days used ÷ days available. Days available are the days of the range the vehicle existed (one added or archived mid-range only counts its own days). Days are whole days on your MyGeotab time zone, up to yesterday: today is never complete, so a range ending today stops at yesterday and the page says so. Utilization never passes 100%.

A day is used when the vehicle moved at least 0.5 km (0.3 mi) that day, adding up its trips. A trip belongs to the day it ended. Shorter days — a 0 km "ghost" trip, a tracker's GPS drift, a few metres in the yard — are not used, and their trips, minutes and distance are left out of every total (MyGeotab's own utilization report does the same).

The cluster and the two rankings count driveable vehicles only: a Geotab GO device, or another device that sent engine (or, electric, battery) readings. A trailer used two days a month can be normal; a pickup used two days a month is money parked. Records set as Trailer, Equipment or Container in MyGeotab, and devices with No engine data (asset trackers, tags), stay in the list — on the Trailers & equipment tab — with a grey chip; their days used and distance are real, from GPS, and they get their own line under the cluster. Hours used (driving + idling) are shown only for a device that reads an engine: a tracker's "ignition" stays on, so its hours would not be use.

Colour means the decision a vehicle needs. Underused (amber) = used on fewer than 30% of its days (about 2 days a week or less): a candidate to share, reassign or sell. Not used (red) = it reported but never moved 0.5 km in a day. Not reporting (grey, dashed) = its device sent no trip and no GPS position in these dates (readings Geotab generates itself don't count): a device to check, left out of the utilization and the rankings. Click a count to list those vehicles. Avg hours per day used = hours used ÷ days used.

One bar per day of the range: how many vehicles were used that day (vehicles only). Weekends are hatched; the dashed line is the average. Over 90 days, one bar per week: the vehicles used per day, on average that week (its busiest day on hover). Click a bar to list the vehicles used that day or week; click it again to clear.

Top 10 least active: lowest utilization first; ties = the longest since it last moved (a trip of 0.5 km or more; ghost trips are skipped). Busiest: the most hours used per day used. Click any vehicle for its panel: its figures and a calendar of the range — used days filled (darker = farther), moves under 0.5 km dotted, not-used days empty, days before it was added or after it was archived hatched.

The page runs by itself when you open it, with the last range you used (30 days the first time). Changing the dates or groups afterwards says "Settings changed — Run to update". A ticked group includes its sub-groups; a vehicle in several groups is in if any of them is ticked. Report downloads exactly what the list shows (tab, colour, day, search) in its order, plus the two rankings and these rules. If Geotab doesn't answer a question, the run says so in its notes; a record is never called silent without an answer.

Idle time is Geotab's trip idling: every minute a vehicle sat stopped with its engine on, however short, on trips that ended in the date range. It is the same data, chosen the same way, as MyGeotab's trip-based idling reports. Dates are whole days on your MyGeotab time zone.

Only driveable vehicles whose engine data reaches Geotab add to the idle time, fuel, cost, ranking and averages: a vehicle with a Geotab GO device (it reads the engine), or one whose other device sent engine readings in the date range. An asset tracker, tag or sensor has no engine connection, so the time Geotab records as "idling" for it is the device awake while parked, not an engine running.

Nothing is hidden. Records set as a Trailer, Equipment or Container in MyGeotab, and devices with No engine data, stay in the list with a grey chip and "—" instead of their idle time; their panel shows what Geotab recorded and why it isn't counted. Electric vehicles show their idle time with no fuel and no cost. A tag at the top counts them all: click it to open a panel beside the list that groups them by reason, each with its own reason line (its Asset Type, or what its device sent in the dates run), its device, when it last reported and Geotab's idle time; Show in the list scrolls to its row. The Excel report lists each one with Geotab's own idle time, so counted + not counted = what MyGeotab reports.

Fuel wasted = idle hours × the fleet type's idle fuel burn (Light 0.5, Medium 1.0, Heavy 1.2 US gallons an hour). Idle cost = fuel wasted × your fuel price. Change the price, currency, unit or fleet type under Fuel and the numbers update at once. Real burn varies with the engine, load and accessories, so treat the cost as a well-founded estimate, not a fuel bill.

The page runs by itself the first time you open it after signing in, with the last range you used. After that, changing the dates, groups or vehicles fetches nothing until you press Run: the strip says "Settings changed — Run to update" and the results stay as they were. Data as of in the header says when the trips were fetched.

A later run of the same dates can show a little more idling. Geotab records a trip's idle time when the vehicle's next trip starts, so each vehicle's most recent trip shows its idling only after that.

Idling by group shows each group tree at the first level where vehicles split into several groups, so a group that holds the whole fleet doesn't become one big bar. A vehicle in more than one group counts in each, so the groups can add up to more than the total. Click a group to focus the list on it.

The cost panel, the ranking and the two cards describe every counted vehicle in the run. The list follows the filters you add: a group from Idling by group, and the search. Report downloads exactly the vehicles the list shows, and its Summary sheet names the filters.

FleetLume By EnVue gives you a live view of the health of every vehicle in your fleet: how many are healthy, which ones need attention, and why. It connects directly to your Geotab database and refreshes automatically in the background so you always see current data without reloading the page.

Fault data comes straight from Geotab and follows the same rules as the Faults page in MyGeotab: the last 30 days, one row per fault code and failure mode, dismissed faults left out. A vehicle's color is based on its current vehicle faults — the ones whose status is Active or Pending — and on the warning lamps the vehicle's computer reports. It does not depend on how many times a fault was logged.

"N faults" is the number of different faults the vehicle currently has. "Logged M×" is Geotab's Times logged: how many times in the last 30 days the vehicle's computer reported them. A single unresolved problem can be logged dozens or hundreds of times — it is still one fault, and a high number only tells you it keeps coming back.

A fault leaves the list of current faults when Geotab reports its status as None (no longer active), or when it is dismissed in MyGeotab. A new status shows up at the next automatic refresh; a dismissal within 5 minutes (FleetLume re-reads the full 30 days of faults every 5 minutes and, in between, only what is new). A dismissed fault that triggers again comes back, counting only the new records. Faults not logged for 30 days drop out on their own. Faults whose status is None stay listed in the vehicle details under No longer active (MyGeotab still lists them too), but they no longer count toward the vehicle's faults or color.

Each fault in the vehicle details matches a row on the MyGeotab Faults page:

A current fault may show a badge. Lamps come straight from the vehicle; "Check immediately" and "Check at next halt" are Geotab's own ratings:

No badge means the vehicle reports no lamp and Geotab rates the fault "maintenance only" or "no repair needed". MyGeotab's own screen may show a different severity word (e.g. "High") that isn't available to add-ins, so FleetLume shows the lamps and ratings above instead.

FleetLume By EnVue refreshes all vehicle data automatically in the background — no manual reload needed. The refresh speed adjusts to the size of your fleet to keep the page responsive: every 10 seconds up to 500 vehicles, 30 seconds up to 2,000, and 60 seconds above that. New faults arrive at every refresh; the complete 30-day fault list is re-read every 5 minutes. The Live pill in the header shows when data was last received from Geotab and counts down to the next refresh.