What it is for
It shows the places where the same violations keep happening — an idling zone, a speeding road, a crossroad with harsh braking, a curve taken too fast — so you can find out why. A violation that happens once here and once there is not shown: it isn't a pattern.
What a pattern is
A place where one rule's violations repeat: 5 or more of them on 3 or more different days (one long idle that fires 20 times in an hour is not a pattern). Each is named for what it is: Idling zone, Braking spot, Cornering curve, Seat belt zone, Acceleration spot or road, Speeding spot or road. A spot is a circle 200 m across around the busiest point; speeding and hard acceleration can also run along a road (a stretch longer than 300 m — its length is shown).
The map is the dark panel at the top (dark in both themes). Each rule has its own colour and icon — on its chip, on the map and in the list. The map glows only where patterns are, brighter where they are stronger; the Top 10 beside it are numbered like the markers on the map.
The rules and the filters
The chips along the top of the map are its legend — Harsh Braking, Hard Acceleration, Harsh Cornering, Seat Belt, Speeding, Idling — each with how many violations it had. Click a chip's name to show or hide it on the map (✓ = shown; a hidden one is struck through). Click its Rule ▾ to choose which of your Geotab rules it uses (Geotab's own rule by default, tagged "Geotab"; archived rules aren't listed; a rule already on another chip is greyed out); the new rule loads straight away. A chip using one of your own rules shows "Rule" in amber.
The bar under the chips always says what is shown. When anything is filtered — a rule hidden, one vehicle, a pattern type, a search — it turns solid amber with FILTERED, the map gets an amber frame, and Show everything brings everything back.
Finding a place
Under the map: Vehicles most involved (click one to see only its patterns) and Patterns by type (click one to list only that type). All patterns lists every pattern shown — ranked, sortable, with Spots and Roads tabs. The search at the top (press /) finds places by address or type, and patterns by the vehicles and drivers involved.
Every violation counts here as Geotab reports it, whatever recorded it. A grey chip marks a record that isn't a driveable vehicle reading an engine — a Trailer, Equipment or Container (its Asset Type in MyGeotab), or a device with No engine data (an asset tracker) — because a towed trailer's speeding is usually its truck's. A tag at the top counts them: click it for a panel that groups them by reason, each with its violations; Show its violations shows only that vehicle on the map. Idling Cost and Driver Safety leave such records out of their totals and scores.
Click a marker, a Top 10 row or a list row to open the pattern beside the page: its address with Google Maps and Street View, its violations, vehicles, days and length, a bar for each day of the range, and What the data shows, worked out from its own violations on every run: When (its busiest 2 hours; "weekdays only" when under 3% happen at weekends, "often at weekends" above 45%), Who (when 3 vehicles or fewer make 60% or more of it: "start with their drivers"; otherwise it is more likely the place) and Trend (the last 7 days against the weeks before; within 20% either way is steady; it needs 14 days or more). What to check gives advice for that kind of place. ← and → step through the list; Esc closes.
What is counted, and where
Every violation of those rules that started in the chosen days is counted — the same violations MyGeotab lists; dismissed ones are left out. Days are whole days on your MyGeotab time zone; the quick ranges end yesterday, and choosing today in the date box runs to now ("today so far"). Dates, Groups and Vehicles in the strip choose what the run covers: press Run after changing them (the page says what changed and Run pulses).
Geotab doesn't store where a violation happened, so FleetLume looks up where the vehicle was at that moment. It looks them up in a fair order (every rule gets its share, every vehicle and day mixed) — when a vehicle has several violations close together, one request places them all — and shows the patterns as they appear, with a "Still looking up positions" pill at the top. A fleet that fits in 2 minutes is placed completely and its counts are exact. On a bigger fleet the results are ready after 2 minutes from a fair sample (a pattern's count is then an estimate, "≈ 340"), and FleetLume keeps looking in the background: every 2 minutes the patterns, counts and Excel report update, until every violation is placed (while a pattern is open, the update waits until you close it). Stop ends it; Run again continues where it stopped. The chip counts and the vehicle list are always exact.
Positions already found are remembered in this browser (a violation never moves), so the next run starts from them and refines the picture — a daily check takes seconds. Clearing this site's data in your browser forgets them.
The Excel report
Report downloads it as soon as it is ready, and it follows every filter: a Summary (the filters, how many positions were looked up), the Patterns the list shows (in the list's order: name, rule, address, length, violations — exact or estimated —, vehicles, days, when it usually happens), the Vehicles, the Violations of the rules and vehicle shown (the newest 100,000 at most) with time, vehicle, driver, rule and their pattern, if any, and an About sheet that explains it.