Release Notes

What is new in TruStar Connect, newest first.

v2.425August 25, 2026

Set a driver’s cycle from their file

Added

A driver’s hours of service cycle can now be switched from their own file. It could only be set as an organization default before, so a carrier running most drivers on one cycle and a few on the other had no way to say so — and the cycle decides which limits their log book is measured against.
The file says what a switch actually costs: 36 consecutive hours off before moving to Cycle 1’s counterpart and 72 the other way. Changing the setting records which rules the driver is measured against; it does not give them the rest.

Fixed

The carrier profile still said Fleet did not track CVOR violation points. It now describes what the CVOR screen does, and links to it — while being clear that the official rate is entered from your abstract rather than calculated here.

v2.424August 25, 2026

CVOR fixes from using it

Fixed

Recording an abstract was only possible from the panel at the very top of the CVOR page, so anyone on the Abstracts tab had to scroll back up past the ladder and the estimate to do the one thing that tab is for. The button beside the tabs now matches whichever tab you are on.
The CVOR row only appears in the menu for carriers who operate in Ontario. Everyone else was seeing a menu entry for a registration they do not hold, leading to a screen that turned them straight back.
The CVOR page reads properly on a phone: the rate and count tiles sit two across rather than one, headings stack above their buttons instead of colliding with them, and the abstract form no longer puts four number fields in a row.

v2.423August 25, 2026

Fleet covers the whole country

All ten provinces and the three territories, with the northern hours of service rules.

Added

Where you operate now lists all ten provinces and the three territories, not just the five it started with.
Hours of service north of latitude 60°N: 15 hours driving and 18 on duty rather than 13 and 14, a 20-hour elapsed limit rather than 16, and 80 hours in a seven-day cycle rather than 70. North of 60 sets no daily off-duty total at all, only the eight consecutive hours, so the log book no longer reports a shortfall against a rule that does not apply.
The split is on where the driving happens rather than where you are registered, and it is not a provinces-versus-territories split — Quebec and Labrador both reach above the parallel. Tick a jurisdiction that does and the settings screen explains what changes.
Settings tells you which of the jurisdictions you picked were built against their own regulation and which follow the national standard, so you know when to read a prescribed figure off your own province’s schedule.

Fixed

The log book never checked the 16-hour elapsed limit — the rule that ends a driver’s day 16 hours after their last 8-hour rest even if they are inside the driving and on-duty caps. It is the limit most often missed, because waiting at a dock does not pause it.

v2.422August 25, 2026

An estimated CVOR rate between abstracts

With a warning label, and a check that tells you whether to believe it.

Added

Classify each CVOR event as you record it — a major conviction, a trip inspection failure, a clean inspection — and the screen estimates your rate from the events in your window, so you know roughly where you stand between abstracts.
Your thresholds are worked out from an abstract you already hold rather than from a table: a printed component rate and the points behind it give the threshold by division. So the scale of the estimate comes from the Ministry even where the point values do not.
The estimate checks itself against a second abstract from a different date and reports the result — whether it landed within a couple of points of what that abstract actually printed, or was far enough off that you should ignore it. With only one abstract it says plainly that it cannot be checked yet.

Changed

The estimate is labelled an estimate everywhere it appears. We have not been able to confirm the points schedule against any Ministry publication, so the figures from your abstract stay separate, are never overwritten by it, and win wherever the two disagree.

v2.421August 25, 2026

CVOR, for Ontario carriers

Keep your abstracts and the events behind them, and see what is in the 24-month window.

Added

A CVOR screen under Fleet for any carrier who operates in Ontario. Record each abstract as you pull it, with the violation rate, the three component rates and the safety rating exactly as printed on it.
Abstracts are kept as a history rather than overwritten, so two side by side show which way your rate is moving — the earliest warning you get.
The collisions, convictions and inspections behind the rate, with the 24-month window worked out for you: what is inside it today, and the date each event leaves it. Anything dropping out in the next 60 days is listed.
Record an event before it reaches an abstract — a stop at the scale house last week — and it is counted separately, so you can see what is coming rather than waiting to be told.
An event can be linked to a roadside inspection you already recorded, so the same stop is never typed in twice.

Added

Your rate is placed on the Ministry’s published intervention ladder, with how many points of room are left before the next one: under 35% monitoring, 35% a warning letter, 50% a possible facility audit, 85% an interview, 100% suspension or cancellation.
The 70% line gets its own warning, because it is not one of the band edges — above it the safety rating drops to Conditional with or without an audit, and getting back up needs 60% or less.
If your collision, conviction or inspection rate reaches 100% on its own, that is called out. It carries the same consequence as the overall rate doing so, and a carrier can look calm on the headline figure while being at the limit on collisions alone.
The five safety ratings and what each turns on are listed on the screen.

Changed

We do not calculate your violation rate, and the screen says so. The point values and threshold tables are the Ministry of Transportation’s, and a rate worked out here from a second-hand copy of them would look exactly like the real one — reading 40% when the Ministry has you at 65% means you do not act.

v2.420August 25, 2026

Fleet on the front page

Added

The home page now has a section for carriers: driver files, hours of service, trip inspections and fuel tax, with the Geotab telematics integration named and a link through to the full Fleet page.
Trucking is listed alongside construction, oil and gas and the other industries at the top of the home page.

v2.419August 25, 2026

A page on the website all about Fleet

For carriers who have never heard of us, at /fleet-compliance-software.

Fixed

The phone image at the top of each landing page had no size set, so on a slow connection it arrived after the text and shoved it down the screen. It now reserves its space.

Added

A public page covering the Fleet module end to end: driver files, hours of service, trip inspections, the maintenance program, fuel tax, roadside results and the facility audit, with a free trial form on it.
Twelve of the app’s own screens run down it, in the order a carrier meets them — the register, the pre-trip, the defect criteria, the hours, the map, the driver files, the shop, the scale house and the quarter’s fuel tax.
It speaks to both kinds of carrier — federally regulated fleets running a certified device, and small provincial operations who need an electronic log book rather than a device to buy.
The telematics section says plainly that the Geotab integration only ever reads, and that we are not a certified electronic logging device.
The scrolling phone screens on the page are the same ones from the home page, running the same component, so the two pages cannot drift into looking like different products.

v2.418August 25, 2026

The Telematics buttons fit on a phone

Fixed

On Fleet → Telematics, the three buttons at the top of Matching were squeezed onto one line on a phone, breaking "Sync vehicles & drivers" mid-word down four lines. They now stack, one full-width button per line, and sit side by side again on a wider screen.

v2.417August 25, 2026

Fleet cards read properly on a phone

Changed

On the Fleet register, a unit’s number and name now run the full width of its card instead of being squeezed beside the action icons, which on a phone broke a name like "2017 Chevrolet Silverado 1500 LT" over three lines.
The QR, hold and open icons have moved to the bottom right of each card.

v2.416August 25, 2026

The knowledge base is filed the way the menu is

Help topics now match the sections in the left menu, so you look for an article where you were already looking.

Changed

The knowledge base topics are now the same as the menu sections: Safety, Actions, Operations, Fleet, Compliance, Analytics, Support and Settings, with Getting Started in front.
Fleet has its own topic. Its ten articles used to sit in Compliance alongside equipment, permits, daily reports and short service workers, which had become a list of everything nowhere else had claimed.
Operations is new, and holds daily reports, crew scheduling, equipment and maintenance.
Finding your way around has been rewritten. It was still describing five menu sections and calling Daily Reports, Equipment, Permits and COR "coming soon", all of which shipped some time ago.

Fixed

The help button on any Fleet screen opened the front of the knowledge base instead of that screen’s article. It now opens the right one, and the same for Toolbox Talks.
The picture of the menu inside Finding your way around is now drawn from the menu itself, so it cannot fall behind it again.
Corrective Actions now describes the reminder emails as they actually work: which of the three you get, when, and who an escalation goes to.
Fuel & IFTA now describes what the fleet average tile says while it is waiting for the rest of the quarter’s receipts.

v2.415August 25, 2026

One corrective action email a day, not one per action

Escalations, overdue notices and due-soon reminders now arrive as a single list.

Changed

A manager with six overdue corrective actions was getting six near-identical escalation emails. They now arrive as one email listing all six, longest overdue first.
The same for overdue notices and due-soon reminders to the person who owns the actions — one email with a list, rather than one per action.
When there is only one action, the email still names it in the subject, because that is more useful than counting to one.

Fixed

A corrective action whose title contained a character like < or & could break the layout of these emails. Titles and names are now escaped.

v2.414August 25, 2026

No more sideways scrolling on a phone

A long VIN or reference number could push a whole page wider than the screen.

Fixed

A long unbroken value — a VIN, a serial, a reference number from your fleet system — was pushing whole pages wider than the screen, so every panel scrolled sideways and text near the right edge was cut off. Those now wrap.
On Telematics, the Sync, Pull hours and Pull odometers buttons ran off the right edge instead of stacking. They now fill the width on a phone, one per row where they do not fit.
The Find box on Telematics no longer squeezes the Vehicles and Drivers tabs.
The Save and Discard buttons on a scanned receipt no longer run off the edge.

Improved

A unit no longer repeats itself in the Fleet list. A vehicle named after its own make and model was showing that name cut short in the heading and again in full on the line below, and an imported unit showed its number twice.
An equipment detail sheet now runs one item per row on a phone instead of two squeezed columns, so make, model and meter readings stop wrapping mid-value.

v2.413August 25, 2026

The fleet average now says what it is waiting for

Fixes a stray code showing where the figure belongs, and explains the wait in plain numbers.

Fixed

The Fleet average tile was showing a stray character code instead of a dash. That was our mistake in yesterday’s release and it made a working page look broken.
When the average is not ready it now reads “Not yet” and says exactly what it is waiting for — for example, only 31 L recorded against 20,000 km, so add the rest of the quarter’s receipts. A dash on its own told you nothing.

v2.412August 25, 2026

Pull hours explains itself when there is nothing to file

An operating zone record is no longer reported as a status we did not recognise.

Fixed

Your fleet system records which regulatory zone a vehicle is operating in — Canada south of 60, north of 60, or the United States — on the same feed as duty status. Pull hours was correctly leaving those out, but describing them as statuses it did not recognise, which reads like a fault when it is not one.
A pull that finds logs but no duty status now says what it did find and that there is nothing in it to file, instead of only saying that nothing could be filed.

v2.411August 25, 2026

Fuel & IFTA was totalling only the first 1,000 records

A quarter with more than a thousand distance records had every figure on the page understated.

Fixed

Fuel & IFTA loaded at most 1,000 distance records for a quarter and totalled only those. A quarter holding 1,544 was understating total distance, taxable distance, fuel burned and net litres by a third — on the page a return is filed from.
The quarter now reads every record, so the summary and the CSV are complete however many there are.
The tab counts now show the real number of records in the quarter rather than stopping at a thousand.
Long lists show the first 250 entries and say how many they stand for. That is only about how much is drawn on screen — the summary and the CSV still count every record.

v2.410August 25, 2026

Fuel & IFTA reads properly on a phone

The three tables become cards on a small screen, so nothing is clipped or scrolled off.

Improved

On a phone, each jurisdiction, distance entry and fuel purchase is now a card instead of a row in a table you had to drag sideways.
The jurisdiction summary no longer hides the province name when you scroll to reach the numbers — which meant reading a column of figures with no way to tell whose they were.
Net litres is now the headline on each jurisdiction, with a line saying whether it is tax you owe or a credit due to you, rather than leaving it to the colour alone.
Dates are no longer cut off at the left edge of the distance list, and a long unit name no longer wraps down five lines.
The quarter picker and the tables keep the full-width table layout on a tablet or a desktop, where it works.

Changed

The fleet average is held back until enough fuel is recorded to make it mean something. Distance arrives from your fleet system all at once and fuel arrives one receipt at a time, so early in a quarter it was reporting figures like 1,970 mpg — correctly worked out and of no use to anybody.

v2.409August 25, 2026

Fuel & IFTA was showing nothing it had saved

Your fuel purchases and jurisdiction distance were being recorded correctly and never displayed.

Fixed

Fuel & IFTA was showing an empty quarter no matter what was in it. Every fuel purchase and every distance record you saved was stored correctly — the screen simply could not read them back, and an empty quarter looks exactly like a quarter you bought no fuel in.
If you scanned the same receipt more than once because nothing appeared, you will now see every copy. Remove the extras with the remove button on each row — they are real records and a fuel total counts each one.
The driver list on a fuel purchase was always empty for the same reason, so purchases could only be filed against "Not recorded".
A screen that cannot load its data now says so instead of showing zero. On a tax worksheet a wrong zero is worse than an error, because nobody questions it.

v2.408August 25, 2026

Saving a scanned fuel receipt now tells you what happened

Fixes a save that could appear to do nothing, and a quarter picker that scrolled sideways on a phone.

Fixed

Saving a scanned receipt showed no sign of working while it worked — no spinner, no change to the button — so on a slower connection it looked like the button was being ignored. It now says Saving… and tells you the outcome either way.
If a save cannot reach the server at all, it now says so instead of failing silently.
A province or state read off the receipt now appears in the Bought in picker. It was being read correctly and understood correctly, but the picker showed “Choose”, which made a finished row look unfinished.
The Save button and its messages now also appear at the bottom of the list, so on a phone you can save from where you are rather than scrolling back to the top.
When nothing can be saved yet, it says why rather than leaving a disabled button with no explanation.
The quarter picker on Fuel & IFTA no longer forces the whole page to scroll sideways on a phone.

v2.407August 25, 2026

Pull odometers now tells you who did not report

A count of the units that came back with nothing, so a silent gap stops looking like success.

Added

Pull odometers now says how many of your matched units reported no odometer at all. "12 units updated" reads as success on a fleet of 40, and a unit that never reports is a unit whose distance-based services quietly stop advancing.
If the reading feed comes back full, it says so. Your fleet system returns these grouped by vehicle, so a full feed drops whole units rather than thinning everything out evenly — which is the difference between slightly stale numbers and some trucks having none.

v2.406August 25, 2026

Trips & loads, and a check before the truck goes

The trip record an auditor asks for, and what your own records say before you dispatch.

Added

Fleet → Trips & Loads records what each load was, who took it, where it went and what it weighed, with the shipping document number that ties it to the driver’s log book.
An auditor checks hours of work against trip records, so keeping these answers half of that question on its own.
Loads carrying dangerous goods are marked as such, with the UN number, class and packing group.
Before a trip is dispatched, a check reads what you already hold: the driver’s licence and medical, their dangerous goods certificate on a load that needs one, and the unit and trailer’s inspection, registration, insurance and anything overdue for service.
Credentials are judged against the day the trip ENDS, not today, so a licence that runs out while a driver is still on the road is caught before they leave rather than after.
Things that would make the trip unlawful are separated from things merely worth knowing. A blank record is never treated as a bad one — it says plainly that nothing is on file, because that is a different problem.
You can still dispatch over a problem, but the reason is written on the trip beside what the check found.
The check is kept exactly as it stood at dispatch. A licence renewed next week does not rewrite what was known this morning.

v2.405August 24, 2026

The odometer has a second place to come from

Units whose devices do not report an odometer can now get one from your IFTA records.

Fixed

Some fleet systems never publish an odometer reading at all, and until now that meant every service due at a kilometre reading sat still and never came due.
Where that happens, the odometer sync now takes the reading your fleet system records each time a vehicle crosses a provincial or state line, so kilometre-based services start coming due on their own.
It tells you when it has done this, how old the oldest reading is, and how many of them your fleet system estimated rather than read — a reading taken at the last border crossing can be a few weeks old, so a service will come due late rather than early.

Changed

The odometer check under "What is your fleet system actually sending?" no longer stops at "no odometer" — it points you at the fuel tax records as the other place to look.

v2.404August 24, 2026

Your fleet system knows your VINs too

Make, model, year, VIN and plate now come across onto the unit.

Added

Importing from telematics now fills in a unit’s make, model, year, VIN, serial number, plate and plate jurisdiction where your fleet system holds them and you have not entered them yourself. Geotab decodes the VIN, so these arrive for free.
That closes most of what a facility audit asks for in a vehicle file. Tire size is the one part it cannot supply, so that stays a gap you fill in by hand.

Changed

Only blanks are filled. A make or a plate you have already entered is left exactly as it is, even where your fleet system disagrees — the person with the vehicle in front of them is the better source than a VIN decode.
A model year that decodes to something impossible is left blank rather than recorded. A blank is reported as a gap and gets fixed; a wrong year looks answered and never does.

v2.403August 24, 2026

IFTA was reading the wrong field for the province

Every jurisdiction crossing was arriving unattributed. Found by looking at a real response.

Fixed

IFTA distance was being recorded with no province or state against it, every time. The province arrives from Geotab under a different name than the one we were reading, so the distance was correct and attributed to nowhere — which makes a return impossible to file. Now read correctly.
A crossing your fleet system marks as having no jurisdiction is no longer reported back to you as an unrecognised province name.

Changed

Every crossing is now treated as taxable. The field we were reading for exemptions does not exist, and the one that does means something else — a crossing too short to measure, not one exempt from tax. Adjust exemptions on the return itself; assuming them here would understate what you owe.
Pulling distance now tells you how many crossings rested on an odometer reading Geotab estimated rather than read. They are still included, because an estimate beats leaving real distance out — but it is worth knowing before you sign a return.

v2.402August 24, 2026

Your fleet system already knew the licence numbers

Driver licence numbers and hours of service cycles now come across on import.

Added

Importing from telematics now brings across each driver’s licence number and province where your fleet system holds them. They arrive awaiting review, so a manager still checks them against the real licence and attaches the scan — but the number no longer has to be typed in, and the driver file stops reporting it as missing.
The hours of service cycle comes across too, where your fleet system records one. Only the two Canadian cycles are used; an American rule set is left blank rather than being mapped to whichever Canadian cycle looks closest.

Fixed

The odometer check reported nothing found when it had only asked one of the three places Geotab keeps odometer readings — and the one it asked is the least likely to hold any. It now asks all three and says which one your database uses.

Changed

Nothing brought across from your fleet system ever overwrites what is already on a file. A licence you have already recorded, or a cycle you set deliberately, is left alone.

v2.401August 24, 2026

Three fixes found by looking at real data

The new telematics check paid for itself on its first run.

Fixed

Imported log book entries were showing “Manual” or “Automatic” in the location column. That field is how the record was created, not where it happened, and it is no longer written there — a duty status log from Geotab carries no place name at all, so the location stays empty for you to fill in.
Logs your fleet system had set aside were not being skipped on import. The check was reading a field that does not exist, so it never matched.

Added

Imported hours now record whether the device logged them automatically or somebody typed them in. Both are legitimate, but they are different kinds of evidence at an audit, and until now they were indistinguishable.

Changed

The telematics check now looks much further back — six months for hours, a month for odometer readings. A check that comes back empty has failed at its one job.

v2.400August 24, 2026

Periodic inspections in the audit, and a way to see what your fleet system sends

The audit now scores inspection stickers, and an empty screen can be told apart from a misread field.

Added

Audit Readiness now scores periodic inspections. A unit whose inspection has lapsed, or has none recorded, is reported as the violation it is — the dates were already on your units and on What’s Expiring, but the audit category was reporting nothing.
Both ways of recording an inspection work: the sticker expiry, or just the date it was done. Where you have only the inspection date, anything inside twelve months counts.
Telematics has a new check, for owners and admins: ask your fleet system a question and see the shape of what comes back — how many records, and what each field is called.

Changed

Nothing is reported for an inspection merely falling due soon. That is what What’s Expiring is for, and an audit asks only whether the inspection is valid today.
The new check never shows personal detail. Names, addresses and licence numbers are never printed, and any column with more than a handful of distinct values has its contents withheld regardless. Nothing it returns is saved.

v2.399August 24, 2026

Fleet map

Every unit with a device, on one map, with how long ago that was true.

Added

Fleet → Fleet Map shows every unit with a telematics device, where it last reported from. Hover a marker for the unit, the driver, the town and the speed.
Search finds a unit by number, a driver by name, or everyone near a town — the address is searchable, because “who is near Red Deer” is the question people actually ask.
Filter by country, by province or state, by whether the unit is moving, and by how fresh its position is. Only the provinces you actually have units in are offered.
Picking a unit from the list beside the map flies the map to it and opens its details.
Refresh positions asks Geotab where everything is right now. Positions also come down with the nightly sync, so the map is never empty when you open it.

Changed

Every marker is coloured by how old its position is, not by anything about the unit. A truck reporting now looks different from one that stopped reporting at breakfast, because acting on the second as though it were the first is the mistake this is built to prevent.
The fleet map is visible to owners, admins, managers and investigators. Workers and viewers do not see colleagues’ locations.

v2.398August 24, 2026

Roadside inspections

Record the CVSA reports you already receive, and the last unanswerable part of an audit starts answering.

Added

Fleet → Roadside & Collisions records every CVSA inspection your units go through: the level, where, the report number, the unit and driver, and whether either was put out of service.
Each defect can be marked with what should have caught it — your maintenance program, the driver’s trip inspection, or neither because it arose in service. More than one can apply, and an audit scores them separately.
The screen tracks how many Level I or Level V inspections you have had in the last twelve months against the number an audit expects for a fleet your size. Other levels are recorded and do not count towards that figure, which is the part most carriers have backwards.
Audit Readiness now answers on CVSA inspections rather than saying it cannot. With nothing recorded it points you here; with reports entered it reports what they show.

Changed

A Level V inspection asks whether the unit was recently driven or ready for dispatch. An out-of-service defect only counts against you once that is established, so leaving it unanswered holds the defect back rather than scoring it either way.
Falling short of the recommended inspection count is never shown as a failing. You do not choose how often you get stopped.

v2.397August 24, 2026

Convictions and accidents on the driver file

Record the two years of history a facility audit asks for, including the check that found nothing.

Added

Driver files now hold convictions and reportable accidents, with the date, what happened, where, and whether it was in a commercial vehicle.
An accident records whether it was reportable, whether there were injuries or fatalities, the unit involved, and whether you judged it preventable — which can be left undecided, because that is different from deciding it was not.
“I checked, nothing to add” records a clean check. Most drivers most years have nothing, and without this the only files that could show anyone looked were the ones with convictions in them.
Records older than two years stay on the file, greyed out, so you can still see them — they age out of what an audit counts, not out of what you know about your driver.

Security

A driver can see their own convictions and accidents but cannot add, change or remove them. Only an owner, admin or manager can.
Removing a record takes it off the file without destroying it, because an audit asks what you knew and when.

v2.396August 24, 2026

Audit readiness

Run the NSC facility audit on yourself before somebody else runs it.

Added

Audit Readiness under Fleet works out how many driver and vehicle files an auditor would pull for a fleet your size, picks that many at random, and shows you what they would find in them.
The draw stays put until you redraw it, and it lives in the web address, so you can send it to whoever is fixing the files.
A second view shows every file rather than the drawn ones, worst first, because fixing only the files that came up is not the same as being ready.
Where several files share the same gap, the screen says so — fifteen drivers missing an abstract is usually one broken process rather than fifteen problems.
Driver files now hold date of birth, hire date, and the licence status your licensing authority shows, all of which a facility audit asks for by name.
Convictions and reportable accidents for the past two years can now be recorded against a driver, along with the date you last checked. Recording that you checked matters even when there was nothing to add.
The six categories an audit is scored in are listed in the standard’s own words, including the one nobody can self-assess: roadside CVSA inspections come from the jurisdiction, not from anything we hold.

v2.395August 24, 2026

A way out of the access-paused screen

The paused screen now says which account is paused and lets you sign out of it, and Contact TruStar opens a proper form.

Fixed

You can now sign out from the access-paused screen. Every other page redirects back to it while an account is paused, so without a sign out there was no way to reach the login and use a different account.
The screen now shows which account you are actually signed in as. Being signed into a second account you had forgotten about looks exactly like the product being down, and this is usually the whole answer.

Changed

Contact TruStar opens a short form rather than your email client, so it works on a device with no mail app set up, and it reaches us with the account you are signed in as already attached.
Our contact address is info@trustarsafety.com.

v2.394August 24, 2026

The maintenance program, measured against your own schedules

Declare the maintenance schedules you actually run, and see where every unit stands against them and whether its file would hold up at an audit.

Added

A Maintenance Program screen under Fleet: the schedules you run, where each unit stands, and what is missing from its vehicle file.
Schedules you name yourself, applied to one unit or to a whole equipment type, with an interval in days, in distance, or both — falling due on whichever arrives first.
Units are listed worst first: overdue, then no schedule at all, then file gaps. That is the order an auditor finds them in.
Every file gap says what is missing, why it is asked for, and the clause it comes from.

Changed

A unit with no maintenance schedule now reads as a finding rather than as nothing to report. The file has to show the nature and due date of the maintenance to be performed, so having none is itself the problem.

v2.393August 24, 2026

Distance arrives even without a jurisdiction

Crossings pulled from Geotab are now kept when the provider names no jurisdiction, and the hours pull explains itself when a database has no duty status logs to give.

Fixed

Pulling IFTA distance no longer throws away crossings that arrive with no jurisdiction on them. They are kept and marked "Unassigned": the distance is real, it counts toward your fleet average, and it is the individual vehicle distance record an auditor asks for. It simply cannot be filed until a jurisdiction is assigned.

Changed

Total distance now shows how much of it is unassigned, and the "worth checking first" panel names it, because unassigned distance sits in every headline figure and in none of the jurisdiction lines.
When Geotab returns no duty status logs, the message now says whether it holds trips for the same period. Geotab’s Time Card Report is built from trips, so a carrier can see driving time there and nothing here — but a trip records that the vehicle moved and who was assigned to it, not what the driver was doing. It is not a duty status record and is not imported as one.

v2.392August 24, 2026

Vehicle files audited against NSC Standard 11

The maintenance records Standard 11 requires now have somewhere to live, including the ones most carriers have never been asked for.

Added

Tire size and lessor name on a unit. Both are named in the standard as part of vehicle identification, and a leased unit has to say who furnished it.
The odometer reading at the time of a service, and room for more than one invoice or work order per job — the standard asks you to retain all of them.
A lubrication record, which the standard lists as its own required item rather than as part of general maintenance.
A record of axle or suspension modifications that change a unit’s weight rating, with the rating before and after.
Maintenance schedules you name yourself — an A level monthly, a B level every 20,000 km, a C level every six months — rather than one interval per unit. Each is tracked separately, so a major service no longer resets the clock on the basic checks.

Changed

A schedule measured in distance on a unit with no meter reading now shows as "cannot tell" rather than as in date. Calling something compliant because there is nothing to measure it against is the failure this is meant to catch.

v2.391August 24, 2026

Required driver training, with the clause behind it

Every driver file now shows the training the National Safety Code expects, and says plainly which items are law and which are good practice.

Added

A Required training panel on every driver file, showing what applies to your operation and where that driver stands: on file, expiring, expired, awaiting review, or not on file at all.
Each item says where the requirement comes from. "Required" means a standard or regulation names it, and hovering shows the clause. "Safety program" means no standard mandates a certificate, but a facility audit still looks for the training record.
A one-press button that adds the applicable National Safety Code courses to your course list, with the right renewal periods already set, so they can be assigned and renewed alongside everything else.
A dangerous goods setting on the carrier profile. Transportation of Dangerous Goods is the one training certificate an auditor is told outright to verify, and only where dangerous goods are carried — so it is asked for once rather than shown as a permanent gap to carriers it does not apply to.
Training already recorded counts wherever it lives. A course sat through the training system satisfies the driver file, and a certificate uploaded to the driver file satisfies the training record, so nothing has to be entered twice.

Changed

Training that has been uploaded but not yet reviewed is shown as awaiting review rather than counted as complete. A facility audit is an audit of records somebody stands behind.

v2.390August 24, 2026

Telematics that keeps itself current

Your fleet, drivers, odometers and hours now sync overnight on their own, and a sync no longer loses the matches you made.

Fixed

Syncing vehicles and drivers no longer wipes out matches. Importing a set of drivers and then pressing Sync was clearing every link it had just made, so drivers showed as unmatched and their hours had nowhere to land. If this happened to you, press Sync vehicles & drivers once and the matches come back on their own.

Added

Vehicles, drivers, odometers and hours of service now sync automatically every night, so the register is current without anybody remembering to pull it.
Pulling IFTA distance falls back to asking one vehicle at a time when Geotab cannot answer for the whole fleet at once, so a slow database no longer means no distance.

Changed

When distance comes back for places that are not IFTA jurisdictions, the app now names what it saw and explains that IFTA covers the Canadian provinces and US states only.
Pulling hours now says when Geotab returned nothing at all, which is a different problem from hours that arrived and could not be filed.

v2.389August 23, 2026

Fuel & IFTA

Distance by jurisdiction and the fuel bought in each one, quarter by quarter, with the worksheet your return is filled in from.

Added

A Fuel & IFTA screen under Fleet, showing one quarter at a time.
Distance by jurisdiction pulls straight from Geotab for units that are matched, so you are not rebuilding a quarter from a map and a memory.
Photograph a fuel receipt and the date, quantity, cost, location and vendor are read off it for you — or drop in a whole fuel card statement as a PDF and every transaction on it comes back at once.
Everything read is shown for you to check before it is saved, with anything unreadable marked. A row with something outstanding will not save until you settle it.
Fuel purchases can also be entered by hand with the receipt attached, in litres, US gallons or imperial gallons, in Canadian or US dollars.
A summary by jurisdiction showing distance driven, fuel burned, tax-paid fuel bought, and the net litres each jurisdiction is owed tax on or owes you credit for.
Your fleet average is worked out for the quarter in both L/100km and miles per gallon.
A "worth checking first" panel that names the things which make a return wrong while every total still looks right — a unit that drove but bought no fuel, a fuel receipt that is missing, an average that has come out impossibly high or low.
The whole quarter downloads as a CSV, and distance can be entered by hand for a unit with no telematics device.

Changed

The quarter you are looking at is in the page address, so a worksheet can be sent to whoever does your filing as a link.

Fixed

Drivers with no hours recorded yet no longer show as being over a limit. A day with nothing logged is a day with no record, not a day without rest, and every driver in a newly connected fleet was being flagged before anybody had driven anywhere.
Pulling odometers from Geotab now finds readings it was missing. It asks for each of the odometer measurements Geotab can hold rather than only one, works out whether the reading is in kilometres or metres from the fleet as a whole, and tells you which measurement answered and what the first reading came through as, so you can check it against MyGeotab.

v2.388August 23, 2026

Odometers that keep themselves current

Unit readings come from the telematics device, so a service due at 250,000 km no longer depends on somebody typing a number in.

Added

Pull odometers, on the Telematics screen: brings each matched unit’s reading from Geotab and updates the register.
A unit now shows where its reading came from and when it was taken, so a figure kept current by a device reads differently from one somebody typed in March.

Changed

On a unit with a telematics device, the device is the reading of record — it is taken off the engine rather than squinted at through a windscreen. A unit without one keeps whatever was last entered by hand, which is the only way its reading was ever going to arrive.
An inspection on a unit with a device now opens with the odometer already filled in, and says where the number came from. It stays editable, because a driver looking at the dash is entitled to disagree with it.
A unit metered in hours is left alone, because an odometer is not an hour meter and writing one into the other would move every maintenance interval measured against it. A unit metered in miles gets the reading converted.

v2.387August 23, 2026

Import your fleet from Geotab

Vehicles and drivers that match nothing in TruStar can now be created from what Geotab already knows.

Added

Tick the unmatched vehicles on the Telematics screen and create them as units in one step. They are matched at the same time, so the list gets shorter rather than longer.
Do the same for drivers: each becomes a driver file with no login needed, ready to hold their hours and documents. Give any of them a login later and the file follows.
Select all takes every unmatched row on the tab, for a fleet that has never been entered here before.

Changed

Importing vehicles asks what kind of equipment the batch is. Geotab cannot tell us — its device type describes the box under the dash, not the vehicle it is fitted to — so it asks once per batch rather than guessing per vehicle.

v2.386August 23, 2026

Hours of service from a certified device

Federal carriers can now supervise their drivers’ hours in TruStar, pulled from the device those hours are already recorded on.

Added

Pull hours, on the Telematics screen: brings the last fourteen days of duty status from Geotab and files it against each matched driver.
Fleet → Hours of Service now works for a federally regulated carrier once a device is connected. Every driver on one screen, with anyone over a limit or with unsigned days first, exactly as it works for a provincial carrier.
A federal driver can read their own hours under My Log Book. Entries from the device are marked and cannot be changed here — corrections are made on the device, which is what makes the record one an officer accepts.

Security

An entry that came from a certified device cannot be edited or removed by anybody in TruStar, including an owner. The database refuses it rather than the screen hiding a button, so no future screen can undo that by accident.