TruStar Safety
Log inFree trial

Release Notes

What is new in TruStar Connect, newest first.

v2.466August 27, 2026

The app around every screen reads in your language

Navigation, banners, error screens, offline files, Today’s Paperwork and the last of the Fleet wording.

Added
  • The navigation, the phone tab bar and its sheets, the help button, the footer, the sign-out button and the trial and subscription banners all read in your language.
  • Today’s Paperwork reads in your language throughout: the kind of each entry, its type, and every badge on it.
  • Your offline files, the log book’s certification wording, and the screens explaining why a log book or driver file is not available to you now read in your language.
Fixed
  • On a phone, a tab could read « Créer » while the panel it opened was still titled “Create”.
  • Entries in Today’s Paperwork showed their internal values — an incident’s severity read “Lost Time” rather than the words used everywhere else in the app.
  • Counts in Today’s Paperwork now read correctly in the singular and plural instead of always using the plural form.
  • The date on an offline file followed your browser’s setting rather than the language you chose here.
v2.465August 27, 2026

Signing in reads in your language — including when it goes wrong

The whole way into the app, plus every page somebody reaches by scanning a QR code without an account.

Added
  • Signing in, creating an account, accepting an invitation, setting or resetting a password, confirming your email and two-step verification all read in your language.
  • Pages opened by scanning a QR code without signing in — an observation, an inspection, and the subcontractor portal — now read in the language the scanner’s own device asks for, joining the equipment tag, permit and training card that already did.
  • The subcontractor portal reads in your language throughout: requested documents and their review status, your trades, your workers, the training their projects require, and the dates on all of it.
Fixed
  • A failed sign-in showed a message written by the sign-in service, which only writes English — so “Invalid login credentials” appeared on an otherwise French page, on the one screen where you cannot reach your settings to change the language. Twenty-five of these now read in your language, and anything unrecognized shows a plain explanation with the original underneath for support.
  • Dates in the subcontractor portal printed as 2026-05-06 rather than as a date written the way your language writes one.
  • The review status on a submitted document, and the state of a worker’s required training, printed their internal values instead of words.
v2.464August 27, 2026

Page titles no longer get squeezed by their own buttons

Every page header now moves its buttons onto their own line instead of crushing the title, at whatever width that happens, in whatever language.

Fixed
  • On a tablet, the Training page title was crushed to a few pixels wide by the row of buttons beside it, so it broke mid-word and its description printed a few characters per line. Every page header in the app is fixed the same way.
  • The same squeeze was present on Documents, Forms, the hazard register, permits, the toolbox, reports, users, analytics, observations, investigations, subcontractor evidence and the COR pages, and showed up mostly in French, where the button labels are longer.
  • A page header now drops its buttons onto their own line the moment they and the title cannot both fit, rather than at a fixed screen width, so it adapts to how long the words actually are.
v2.463August 27, 2026

COR and SECOR read in your language — and so does the binder you hand your auditor

The readiness score, the assessment, eligibility, evidence and the action plan — plus the evidence binder, written once in the language you exported it in, down to the folder names inside the zip.

Added
  • The COR / SECOR section reads in your language: your readiness score and what each element is worth, your programme details, the SECOR eligibility check, the assessment, linking evidence to a requirement, and the action plan.
  • Exporting the evidence binder now produces the whole archive in your language — the readiness summary, every element index, and the names of the folders and files inside the zip.
  • Notes that auto-credit writes onto a requirement, and the recommendations the action plan generates, are written in the language of whoever pressed the button and kept that way, because they are records people work from months later.
  • A message telling you a button is not available to you now reads in your language, so you can tell a permissions question from something being broken.
Changed
  • Element names, requirement wording and question numbers stay in the language the audit instrument was published in, because your assessor scores against the document in their hand. The assessment page now says so, and our own one-line summary of each element follows your language.
  • COR and SECOR are named the same way everywhere. The binder used to call the programme something slightly different from the rest of the app.
Fixed
  • The first page of the evidence binder ended with an English paragraph even in a French binder, and it named the records folder as fixed text rather than the folder the export actually creates.
  • Due dates on the action plan and dates on your uploaded records printed as 2026-10-01 rather than as a date written the way your language writes one.
  • Counts in generated notes hedged with “record(s)” instead of reading correctly in the singular and the plural.
v2.462August 27, 2026

Training reads in your language, and so does the card in your wallet

Your certificates, the review queue, the training matrix and crew readiness — plus the Excel export and the printed training card, each written in the language of whoever produced it.

Added
  • The training section reads in your language: your certificates, what your role and your current project require, adding a ticket by photo or file, the bulk scanner that splits a page of tickets, and the queue where a supervisor approves them.
  • The training matrix and crew readiness read in your language, down to the status on every cell and every crew row.
  • The training card reads in your language, and the wallet-sized card prints in the language of whoever printed it.
  • Exporting the matrix to Excel now produces the whole workbook in your language — sheet name, column headings, legend and the note under the title.
  • Scanning the QR code on a training card opens the public verification page in the language the scanner’s own phone asks for, which is what an inspector at a gate needs.
Changed
  • A certificate’s status now uses the same words wherever it appears — your own list, a matrix cell, a crew row — instead of a slightly different set on each screen.
  • On crew readiness, French now reads « Apte » and « Non apte », the standing term for cleared to work, which does not change depending on who the worker is.
  • The letter on a matrix cell saying why a course is required is an initial, so it follows your language: R and P in English, P and PJ in French, with the legend and the exported note spelling it out.
Fixed
  • Dates on the training card were written in Canadian English no matter what language you read the app in.
  • Dates elsewhere in training followed your browser’s setting rather than the language you chose here.
  • The “not available offline yet” notice built its sentence from a phrase and read badly — “the today’s paperwork” in English, and worse in French. It names the screen properly now, on every section that shows it.
v2.461August 27, 2026

The document library reads in your language

Folders, uploads, read acknowledgements, version history, the controlled-document editor and the AI SDS search — and the COR starter folders are now created in your language.

Added
  • The Documents section follows your language: folders and their permissions, searching, uploading one document or a batch, and moving or deleting one.
  • The controlled-document editor follows your language, including the approval and signature flow and the AI drafting panel.
  • Read acknowledgements, version history and the AI SDS search read in your language.
  • A folder that shows live records — investigations, training, inspections, meeting minutes — reads in your language, down to the status beside each row.
  • The COR starter folders are created in the language of whoever adds them, so a French account gets French folder names and descriptions.
Changed
  • Document categories show in your language while the category stored on the document stays the same, so a sheet filed under SDS reads « FDS » in French and still matches when you filter for it.
  • File formats keep their own names — PDF, Word, Excel and PowerPoint are a format and three products rather than words to translate. Image, Text and File are ours and follow your language.
  • A live record’s own title stays as it was entered: an investigation you named, a form your crew filled in, and a person’s name.
Fixed
  • Adding the COR starter folders is now matched by each folder’s short code rather than by its name, so adding them from two different languages no longer creates a second copy of every folder.
  • Four dates were written in English whichever language you read in: on the folder list, on training rows inside a linked folder, in a document’s revision history, and on the COR re-signing reminder.
  • A signature with no recorded date read as “Signed by … on .”
v2.460August 27, 2026

The rest of Fleet reads in your language

Fuel tax, the receipt scanner, telematics, the live map, trips and the log book review — and numbers, lists and times written the way your language writes them.

Added
  • The fuel tax worksheet follows your language: the quarter summary, the jurisdiction table, the distance and fuel lists, and everything worth checking before you file.
  • The receipt scanner follows your language — reading a receipt or a card statement, and every reason a row is not ready to save.
  • Connecting a fleet system, matching its vehicles and drivers to yours, and the diagnostic that says what your fleet system is actually sending, all read in your language.
  • The live map follows your language, including the filters, the marker popups and how long ago each unit reported.
  • Trips and loads follows your language, including every finding the pre-dispatch check raises about a driver, a unit or a trailer.
  • The carrier profile and the log book review read in your language.
Changed
  • Numbers are written the way your language writes them across all of Fleet, so 1,234.5 km in English reads 1 234,5 km in French.
  • Lists of places are joined with the right word for your language rather than with a comma.
  • Times like “two hours ago” on the map are written the way your language writes them.
  • What the receipt scanner could not read, and any error from your fleet system, are passed through in the words they arrived in rather than translated.
  • American state names on the fuel tax screens stay as an IFTA return prints them, because the receipt scanner matches what it reads against those names.
Fixed
  • Every figure on the fuel tax worksheet was formatted for your browser rather than for the language you chose here.
  • The same was true of the times on the telematics screen and the planned and actual windows on a trip.
  • The log book showed English zone names and cycle limits on a French screen, from a copy of those words that nothing else read.
v2.459August 26, 2026

The NSC audit screens read in your language

Audit readiness, roadside inspections, the CVOR record and the maintenance program — including the warning that the CVOR estimate is an estimate.

Added
  • Audit readiness follows your language, including every finding on a vehicle or driver file and the sentence explaining why each one is being asked for.
  • Roadside inspections follow your language: what an inspection means for your audit, recording one, and attributing a defect to maintenance or to a missed trip inspection.
  • The CVOR screen follows your language — your rate against the intervention ladder, the plain-language notes under it, the five safety ratings and what each one turns on, and the form for entering an abstract.
  • The warning that the estimated CVOR rate rests on an unverified points schedule, and that the printed figure is the one that counts, now reads in your language.
  • The maintenance program follows your language: where each unit stands against your own schedules, and declaring a new one.
Changed
  • CVSA inspection level names and Ontario’s safety ratings stay as they are printed, because they are the words on the paper you are handed. What each one means reads in your language.
  • The six categories a facility audit scores are quoted from NSC Standard 15, which is published separately in French. The screen now says so where they appear.
  • Rates and percentages are written the way your language writes a number, so 41.2% in English reads 41,2 % in French.
Fixed
  • The province list when recording a roadside inspection showed English province names whichever language you read in.
  • A distance shown against an overdue service was formatted for your browser rather than for the language you chose here.
  • A failed query behind the maintenance schedule list would have shown as a carrier with no schedules at all, which is itself an audit finding. It now reports the failure.
v2.458August 26, 2026

Users and your profile read in your language

The Users page, your own profile, and the six role names and descriptions wherever they appear.

Added
  • The Users page follows your language: inviting someone, the role and supervisor you give them, their projects, positions and hire date, and the whole panel for managing one person.
  • Your own profile follows your language — your details, your projects, the training your position requires, and the certificates on your file.
  • The six roles and the description of what each one can do read in your language everywhere they appear, including your profile and the document library.
Fixed
  • Dates on your profile followed your browser’s setting rather than the language you chose in the app.
  • Four labels across permits and organization settings showed an internal code instead of their wording. The build now refuses a screen that would do that.
v2.457August 26, 2026

The menu reads in your language

Every section and every item in the navigation, on every screen — plus a fix for permit search coming up empty in French.

Added
  • The navigation follows your language: the sidebar, the bar along the bottom of a phone, and the menu behind it. Every section and every item.
  • The create menu and the quick-create links beside Investigations, Observations and Toolbox Talks follow your language too.
Fixed
  • Searching the permit register in French found nothing when you typed a work type as it appeared on your screen — the search was matching against the English wording.
  • Work type chips on the permit register printed in English whichever language you read.
v2.456August 26, 2026

Settings reads in your language

The whole Organization page, your clients, sites and projects, the training program, and the sentence a permit signatory attests to.

Added
  • The Organization settings page follows your language: the business profile, default time zone, two-step verification, company logo, approvals, effectiveness reviews and the Fleet switch.
  • Your clients, sites and projects follow your language, including every field on the forms that create them.
  • The training program follows your language — courses, positions, the courses each position requires, and the extra training a project asks for.
  • Permit authorization follows your language: the steps, who can cover each role, and which work types a step applies to.
  • Province and territory names use the official French forms published by the Government of Canada rather than a translation of ours.
Fixed
  • Permit signing roles and the sentence each signatory attests to were in English throughout the permits section whichever language you read — including the screen an outside signatory opens to sign.
  • Time zone names on the settings page and on a project were in English whichever language you read.
  • A role name recorded on a permit still keeps the wording it was signed under, so a signed permit does not change after the fact.
v2.455August 26, 2026

Analytics reads in your language

The dashboard, all thirty-three tiles, the AI read-out, and the charts — with the rule that our words follow you and the names you typed do not.

Added
  • The Analytics dashboard follows your language: the page, every tile you can add and the question it answers, the customize panel, the reporting window and the AI Insights read-out.
  • Chart labels follow your language where the words are ours — severity, risk rating, control tier, defence layer, part of the day — while a site, project, client, person or form you named prints exactly as you entered it.
  • The x-axis on the trend charts is written the way your language writes a month. It was fixed to English regardless of who was reading.
Fixed
  • The annual safety review printed severity classifications, risk ratings, control tiers and times of day in English on a French document.
  • Choosing "30 days" on the Analytics window showed 90 days of figures under a 30-day heading.
  • The period covering the dashboard — "Last 12 months" and the like — was in English whichever language you read.
  • Leading causes on the annual report dropped a different set of rows in French than in English, so the two languages could show different top causes from the same data.
Removed
  • The old Trends page, which has redirected to Analytics since August and had no way to reach it.
v2.454August 26, 2026

The AI writes in your language

Everything the AI drafts for you — forms, toolbox talks, hazards, policies, causal analysis, corrective actions, investigation summaries — now comes back in the language you read the app in.

Added
  • Ask the AI to design a form, write a toolbox talk, build a hazard register, suggest controls for a hazard, or propose the fields for a new equipment type, and it answers in your language.
  • Drafting a safety policy or suggesting what your document library is missing follows your language.
  • The full investigation analysis follows your language: the timeline it assembles, the causes, the impartial assessment, the defence audit, the corrective actions and their peer review, and the summary that goes into the report.
  • Effectiveness review questions, the COR readiness assessment and the analytics dashboard read-out follow your language.
Changed
  • What the AI READS stays in the language of the document it read. A certificate, a fuel receipt, a photo of a paper form, an uploaded procedure, or a permit filed as evidence comes back saying what the document says — summarizing an English permit into French would read as though the permit said it.
  • A document uploaded to the library is still named after the document rather than after whoever uploaded it, so the library agrees with the files it holds and everyone sees the same name.
  • The AI is told to leave names, equipment models, regulation names and citations exactly as they are, and to use the health and safety vocabulary actually used on Quebec worksites rather than a literal translation.
  • AI text is written once and saved, like anything a person typed: a summary drafted in French stays French for an English reader. Run the generator again from an account set to the other language if you need it there.
Fixed
  • The failure themes on the safety review report printed in English on a French report. Four of the nine had no French wording at all.
v2.453August 26, 2026

The whole permit flow reads in French

Requesting a permit, the signature chain, setting the window, close-out and revalidation, and the entry and gas logs a crew fills in from a phone.

Added
  • Requesting a permit follows your language: picking what kind of work it is, what the permit will include, and the draft it keeps while you decide.
  • The signature chain follows your language — who signs, in what order, adding a signatory inside or outside your organization, signing, and sending a permit back with comments.
  • The screen an outside signatory opens from their email reads in your language, including what they are attesting to and what is recorded with their signature.
  • Setting the permit window follows your language: single shift or blanket, who has to revalidate it each day, and what happens if nobody can.
  • Closing a permit out and revalidating a suspended one follow your language, including everything you confirm before either goes through.
  • The entry log and the gas readings a crew records from a phone follow your language, along with the confined-space screen and the permit controls for extending, suspending or cancelling.
Changed
  • Confined space classifications stay in the language they were published in. They are summaries of your province’s own legislation, and a translation of ours would read like the regulation without being it — the same call already made for defect criteria and standard citations.
  • A maintenance date on a monitoring update now prints the way your language writes dates.
v2.452August 26, 2026

Permits read in French, and so do the page headings

All eleven permit types and everything they ask for, the permit register and the public permit tag — plus a fix to page headings across every section already translated.

Added
  • All eleven permit types read in your language — hot work, confined space entry, ground disturbance and the rest — along with every section, question, hint and answer option each one asks for.
  • The permit register reads in your language, including the active, suspended and closed tabs and how long each permit is valid.
  • The permit tag a crew scans in the field reads in your language: the status, the validity window, the history and the authorization list.
Fixed
  • Page headings and the description under them were still in English on screens whose contents already read in French — the first thing you see on a page. Fixed across Fleet, Forms, Investigations, Equipment and Permits.
Changed
  • A permit that has already been issued keeps the exact wording it was signed under. Translating the permit types changes what a new permit asks, never what an old one says — a signed permit is a record of what somebody put their name to.
  • Permit types you did not get from us are unaffected: a form your organization built is yours and prints exactly as you wrote it, in either language.
v2.451August 26, 2026

Everything an equipment type asks for reads in French

The fields, hints and answer options behind all forty-eight built-in equipment types, the QR tag a machine wears, and a fix to what the compliance list was calling your own wording.

Added
  • Every field the built-in equipment types ask for now reads in your language — 219 of them, from a crane’s rated capacity to a harness’s end of service life — along with the notes explaining why each one matters and every answer you can pick from a list.
  • The QR tag on a machine reads in your language for whoever scans it, including its status, its type, its details and the button that starts an inspection. A guest with no account gets it in the language their phone asks for.
  • The printable QR label sheets, marking a maintenance item complete, and the document viewer for a registration or insurance paper all follow your language.
Fixed
  • The compliance list was showing an English field name to French readers and treating it as though you had typed it. It now knows which of its own fields an expiry came from and names it in your language. Equipment types you added yourself are unaffected — your wording was, and stays, exactly as you wrote it.
Changed
  • Picking an answer from a list on an equipment record stores the same value it always has, whichever language you picked it in. Two identical trailers still match in a filter, an export and a report even when one was entered in French and the other in English.
  • The wording on an equipment type you created yourself is never translated. Only the types built into TruStar Connect are, and the difference is now enforced field by field rather than type by type.
v2.450August 26, 2026

The equipment register reads in French

The register, an asset’s page and its editor, the maintenance queue and the type manager all follow your language, along with the forty-eight built-in equipment types.

Added
  • The equipment register follows your language: the filters, the columns, the warnings about registration, insurance and service coming due, and the spreadsheet you export.
  • An asset’s page and its editor follow your language, including its status, meter units, fuel type and service interval, the commercial-vehicle details, and the documents you attach.
  • The maintenance queue follows your language: every repair, deficiency, service and renewal, where each one came from, and marking one complete.
  • The type manager follows your language, and so do all forty-eight built-in equipment types — what each one is called, what it covers, and the inspection cadence it suggests.
  • Costs and dates on a maintenance record now print the way your language writes them.
Changed
  • An equipment type you added yourself keeps the name you gave it. Only the types built into TruStar Connect are translated; anything you typed in prints exactly as you wrote it, in either language.
  • Nothing about what gets stored changed. An asset’s status and a maintenance record’s type and state are recorded exactly as before, so every filter, export and report keeps counting them the same way.
  • The fuel type filled into an inspection from a linked asset now follows the language of whoever fills the form in, the same rule the rest of a submission already followed.
Removed
  • An unused copy of the equipment type editor that no screen could reach.
v2.449August 26, 2026

The rest of the investigation reads in French

Causes, the defence audit, corrective actions, sign-off and approval now follow your language, which completes the investigation flow.

Added
  • The causal analysis screen follows your language: each factor’s strength, the reasoning behind it, and adding or editing a factor by hand.
  • The defence audit follows your language: how each barrier performed and what that means, the five layers of protection and what each covers, running or re-running the audit, and adding a barrier yourself.
  • Corrective actions follow your language: the hierarchy of controls chart and every tier on it, the AI’s peer-review notes, coverage gaps, the warning about actions with no owner, and the whole edit form.
  • Finalizing follows your language, including the pre-flight check, the AI summary and the executive summary, narrative, key findings and lessons learned you edit before signing.
  • Signing a report and approving one follow your language, including what you are attesting to, who it goes to next, the review history, and sending a report back with a note.
  • The progress panel shown while the AI is working reads in your language on every long step.
Changed
  • Analysis methods still keep their own names. Where the framework is the TruStar Method or 5 Whys the category names are ours and read in your language; SCAT, ICAM, HFACS and Bowtie keep their published category names on the screen and in the report alike.
  • A corrective action’s due date now prints the way your language writes dates, as do the times on a signature and on the approval history.
  • Nothing about what gets stored changed. A barrier’s status, a factor’s strength and an action’s tier of control are recorded exactly as before, so every report, chart and trend keeps counting them the same way.
v2.448August 26, 2026

Evidence and the timeline read in French

Added
  • Capturing what an investigation runs on follows your language: uploading and naming evidence documents, the reference material you attach beside them, scene photos and witness statements, and the progress the app reports while it reads them.
  • The kinds of document you can file — incident report, witness statement, FLHA, permit, sign-in sheet, radio log, training record and the rest — read in your language, on both the evidence list and the reference list.
  • Reviewing what the app pulled out of a document reads in your language, including how sure it is of each item and the buttons for keeping, editing or discarding what it found.
  • The timeline reads in your language: every event and its stage of the story, adding and editing an event by hand, reordering the sequence, and the evidence panel with the notes you attach to an event.
  • Marking up a scene photo reads in your language, and the date on a scene photo now prints the way your language writes dates.
v2.447August 26, 2026

Starting an investigation reads in French

Added
  • The investigations list and its filters, the form for recording a new incident, and the edit and delete screens follow your language.
  • Classifying an incident follows your language: the categories and what each one covers, the outcome scale and the full explanation of every level, and the detail panels for a vehicle, a spill, property damage or a security event.
  • The 5×5 risk matrix reads in your language — every severity level, the descriptors that change with the incident type, the likelihood scale and the guidance for each risk band.
Changed
  • Analysis methods keep their own names. SCAT, ICAM, HFACS and Bowtie are other people’s published methods, so their names and their standard descriptions stay as published — a translated report would be out of step with the method’s own literature. The TruStar Method and 5 Whys are ours and do read in your language.
  • What an incident is recorded as does not change. Choosing a category or an outcome stores the same value as before, so every report and trend keeps counting it the same way.
Removed
  • An unused copy of the vehicle details panel that no screen could reach.
v2.446August 26, 2026

The form builder reads in French

Added
  • The form builder follows your language: the field palette and every field type in it, the settings on each field, the conditional rules, the COR categories, the sections explainer and the live preview.
Changed
  • A form you build in French starts out in French. A new section, a new field and its first options are named in the language you are working in — and once you save, those words are yours and stay exactly as they are.
  • Choosing a COR category files submissions into the same Documents folder as before. Only the wording on screen changed.
v2.445August 26, 2026

The whole Forms section reads in French

Added
  • The forms list, its folders, and the Hidden and Deleted tabs follow your language.
  • A submission you open reads in your language too — every answer, the revision history, the conditions on site, and the permit monitoring panel.
  • Scanning a paper form, generating one with AI, browsing submissions, the QR page, and the guest sign-in screen all follow your language.
  • The example prompts on the form generator are written in your language, so a form you generate comes back in your language as well.
Changed
  • The weather recorded with a submission, the permit type and every status now read in your language on screen, matching what the printed record already did.
  • The defect criteria behind an inspection item stay in the words the schedule publishes them in. The explanation around them is translated; the criteria themselves are not, because they are what an officer reads.
v2.444August 26, 2026

Two crashes fixed

Fixed
  • Some dashboard tiles could take the page down and show an error screen. A tile that started empty and then received data was the trigger, so it hit hardest right after opening the app.
  • The dashboard could fail to open with a time-related error for anyone who had used it before the previous update. Its saved copy on the device was from the older version and no longer matched what the page expected.
Changed
  • Anything the app saves on your device to work offline is now tied to the version that saved it. After an update the app fetches fresh data once rather than reading back a copy an older version wrote, which is what caused the problem above.
v2.443August 26, 2026

Filling in a form reads in French

Added
  • The screen you fill a form, inspection or permit in follows your language — every prompt, warning and button, including the hazard assessment, the crew signatures and the permit sign-off.
  • The pass, fail and defect buttons on an inspection read in your language, and so do the ten energy sources on a hazard assessment.
  • The out-of-service warning shown when a vehicle has no current registration or insurance now reads in your language.
Changed
  • Your own form is still yours. Section titles, field names, help text and the answer options you wrote print exactly as you typed them, even when one of them happens to say the same word as one of ours.
  • What an answer is worth is unchanged. A major defect is still recorded the same way and still takes a unit out of service, whichever language the button was read in.
  • A permit starts with its three signing roles written in the language of the person filling it in. Permits issued before this keep the wording they were signed with.
Fixed
  • The count of required items still to fill in, and the warning about subcontractors on a project, used to pick between singular and plural the way English does. Both now read correctly in French as well.
v2.442August 26, 2026

The driver file reads in French

Added
  • The driver list, each driver’s file and the two-year history of convictions and reportable accidents all follow your language.
  • The Fleet home page and the page showing what lapses next follow your language, including the reason a unit is being held off the road.
  • Document names, licence statuses, conviction types and hours of service cycles are worded on the screen you are reading rather than fixed in English behind it.
Changed
  • Anything you named yourself stays as you typed it. If you called a document something in particular on an equipment type or a driver’s file, the compliance list shows your words rather than a translation of them.
  • “How long is left” on the compliance list is now written the way each language writes it, so a single day reads correctly in French as well as English.
Fixed
  • A driver’s licence status used to be printed by tidying up the stored code, which meant it stayed English whichever language you read. It now reads from the same wording as the rest of the file.
v2.441August 26, 2026

The dashboard reads in French, and so does every document

Added
  • The dashboard follows your language: the welcome line, every attention card, your tasks, feature requests, recent investigations and the whole safety program panel with its charts and figures.
  • Controlled documents and the COR evidence binder print in French. That was the last of them — every PDF the app produces now follows your language.
Changed
  • Dates and month names on the dashboard are written the way your language writes them, rather than always in English.
  • The body of a controlled document is never translated, and never will be. It is your document, and rendering it into another language would make it a different document under the same number.
Fixed
  • An investigation’s status on the dashboard used to be built as English before it reached the screen, so it stayed English whichever language you read. The same was true of the safety program’s month heading and its severity chart. All three now arrive as data and are worded on the screen.
v2.440August 26, 2026

Permits, inspection records and posters read in French

Added
  • Downloading a completed inspection or a work permit now gives you the document in your own language: the heading, the permit details, gas readings, the confined space entry log, the permit history and the authorization block.
  • Permit categories, permit types and statuses are translated — hot work, confined space entry, energy isolation and the rest — so a French permit says what it covers.
  • The inspection poster can be printed in either language from the QR page, the same as the safety observation poster. A poster is read by whoever walks past it, so a bilingual site prints both.
Changed
  • Your form is yours. Section titles, field names and the answer options you chose print exactly as you wrote them, in both languages — a French permit does not rename your fields.
  • Times on a permit stay in the time zone of the site the work happened on, and are written the way your language writes them. The zone is about where the work was; the wording is about who is reading.
  • Gas names on a confined space permit stay as they are. A gas tester reads a meter that says LEL and O2, and a permit that disagreed with the instrument would be worse than one in English.
Fixed
  • A role somebody signed under is printed exactly as it was recorded at the time of signing, never re-worded. The sentence around it translates; the role does not.
v2.439August 26, 2026

The investigation report reads in French

Added
  • The full investigation report now downloads in your own language: the cover and incident details, the narrative, the verified timeline, scene photos, the defence audit, the causal analysis, corrective actions, lessons learned, the evidence index and the sign-off block.
  • Risk ratings, severity levels and likelihood read in French too, so a potential risk rating says what it means rather than half of it.
Changed
  • Reports keep the category names of whichever analysis method the investigation used. The TruStar Method categories are translated because they are ours; ICAM, HFACS, SCAT and Bowtie keep their published English names, because those are the terminology of somebody else’s method and a French version of ours would read like the method without being it. An investigator comparing your report to ICAM’s own material needs the words that material uses.
  • The time of the incident stays exactly as it was entered, in both languages — it is a value on a legal record, not a moment to be converted. French writes it the Canadian way (18 h 00) and English as 18:00.
Fixed
  • Everything a person typed is printed exactly as typed: the report title and number, sites, projects, people, vehicle details, evidence notes and the names of defences.
v2.438August 26, 2026

Every scheduled report now reads in French

Added
  • All eleven report types built from the Reports page are translated — inspection completion, training and certificates, subcontractor compliance, equipment and assets, short service workers, corrective actions, leading vs lagging, COR and SECOR readiness, and the safety review. Set your organization’s report language to French and that is what arrives, headings, columns, notes and all.
  • Counts read properly in both languages. “0 completed”, “1 element sits below the minimum”, “3 elements sit below the minimum” — French and English disagree about how to write zero and one, and each report now follows its own language’s rule rather than a translation of the other’s.
Changed
  • Anything you typed is printed exactly as you typed it: form names, site and project names, people, notes. A report never renames something real.
  • Dates inside report tables stay in year-month-day form in both languages, because those columns get scanned and sorted rather than read. Dates in sentences are written the way each language writes them.
Fixed
  • The note on the report language setting no longer warns that some reports are still English, because they are not. Investigation reports, form submissions and document packages are the ones still to come, and those are downloads rather than scheduled sends.
v2.437August 26, 2026

Choose the language your organization’s reports go out in

Added
  • Settings now carries a language for the reports your organization sends. It starts as English, and an owner or admin can switch it to French. Everything emailed on a schedule then goes out in that language — the report and the covering email both.
  • The safety review is now translated, including its charts: the failure themes, severity classifications, risk ratings and hierarchy-of-controls tiers all read in the language of the document. Site, client and project names are printed exactly as you typed them, in either language.
Changed
  • Reports you download yourself are unaffected and always come out in your own language, set on your profile. That split is deliberate: when you click Download we know who is reading, and when the app emails a schedule to a list of addresses we do not — so the organization answers that one once.
  • Report dates and times now use your organization’s time zone rather than the server’s, so a period heading matches the days people actually worked.
Fixed
  • The scheduled reports built from the Reports page still write their headings and column names in English, so switching to French gives you a French cover and English content for those. The observation report and the safety review are fully translated. This is written on the setting itself rather than left for you to discover, and the remaining reports will follow.
v2.436August 26, 2026

French reaches the printed documents

Added
  • Observation reports, safety posters and toolbox talk records now print in your language. Until now a French screen still produced an English PDF, which is the kind of thing you find out at the worst moment.
  • The safety poster can be printed in either language, from the QR panel, whichever language you read the app in. A poster is read by whoever walks past it rather than by whoever printed it, so a bilingual site prints both and puts them side by side.
  • Dates, times and numbers in these documents are now written the way each language writes them, in your organization’s time zone rather than the server’s.
Fixed
  • The weather on a toolbox talk record is now described in the language of the record, including for talks delivered years ago. The conditions were always stored as a code as well as a sentence, and the code is what the document now reads.
  • Site and project names are never translated, in either language. A report that renamed a real place would be describing somewhere that does not exist.
Changed
  • Scheduled reports — the ones emailed to a recipient list on a cadence — are still in English. They go to email addresses rather than to people with a saved language, so whose language they should be in is a question worth asking you rather than guessing at. Reports you download yourself are unaffected.
  • The remaining PDF exports (investigations, form submissions, document packages, the COR binder) are still in English and will follow in later releases.
v2.435August 26, 2026

Observations and toolbox talks now read in French

Added
  • Observations — the list, the filters, and the detail view — now follow your language setting. That includes the words on the badges: the observation type, the severity, the status, the hazard class, and the action taken.
  • The public observation form, the one a QR code opens, now reads in French for anyone whose browser asks for it. A worker filling in a card at a job site does not need an account or a setting for this to work.
  • Toolbox talks now follow your language setting throughout: the library, the history, the talks assigned to you, assigning a talk to a crew, generating one, delivering it, and signing for it.
Changed
  • The severity scale, the observation types and the status names are now kept in one place and read from there by every screen, so the French and the English can no longer drift apart without the build noticing.
Fixed
  • PDF exports are still in English. Observation reports, safety posters and toolbox talk records print in English even when the screen you started from is in French — the PDF is built outside the page and does not yet know which language you asked for. It is on the list.
v2.434August 25, 2026

Quebec classifies defects differently, and the app now says so

Added
  • Tick Quebec in your carrier profile and you now get a note of its own, not just the general one about national citations. Quebec classifies vehicle defects under its own regulation rather than under the Schedule 1 structure these trip inspection forms follow — major defects are an enumerated list by system (C-24.2, r. 32, articles 163 to 171) and a minor defect is any other deviation from the mechanical standards (article 162). What a pre-trip must cover is set by article 192.
  • The “What counts” panel on every trip inspection item now carries the same warning, for anyone whose runs take them across the Ontario–Quebec line.
Changed
  • The trip inspection article in the knowledge base says the same thing. Schedule 1 is harmonized across most of the country, but Quebec is a difference in kind rather than in wording, and treating it as a translation problem would have produced forms that read like Quebec’s regulation without being it.
v2.433August 25, 2026

The French log book now uses the regulation’s own words

Fixed
  • The French label for going off duty read “Hors service”. In the hours of service regulation that phrase means something else entirely: « mise hors service » is the out-of-service declaration an inspector issues to take a vehicle off the road. A driver tapping it to go off duty was being shown the words for their truck being ordered off the road. It now reads « Repos », which is the term the regulation uses.
Changed
  • Every hours of service term in French now matches the French column of the Commercial Vehicle Drivers Hours of Service Regulations rather than being translated by us: Activité for duty status, Repos, Couchette, Conduite and Service (sans conduite) for the four statuses, Relevé de l’odomètre, Coconducteur, and the latitude 60 headings word for word. A driver comparing our screen to a paper log or an inspector’s copy now sees the same words.
  • The violation sentences use those nouns too, so “less than 10 hours off duty” reads as hours of « repos » rather than a paraphrase.
v2.432August 25, 2026

The log book and driver training read in French

Added
  • My Log Book is translated: the duty status buttons and what each one means, the day’s totals, the correction and daily-log forms, the north-of-60 controls, and the hours of service violations themselves.
  • The Required training panel and the ticket camera on a driver’s file are translated too — the two screens a driver uses most from a phone.
Changed
  • An hours of service violation now carries the limit it broke rather than a finished English sentence, so the screen can say it in the language the driver reads. It also fixes a quieter problem: the same violation means 13 hours south of latitude 60 and 15 north, and a sentence written once could only ever be right on one side.
  • The OFF, SB, D and ON codes are deliberately NOT translated. They are what the electronic logging device standard and a paper log use, and what an officer reads at a roadside check — a French rendering would put a driver’s screen out of step with the document being inspected.
v2.431August 25, 2026

Choose the language you read the app in

Added
  • Your profile now carries a language: English or French. It is saved to your account rather than to the browser, so it follows you from the office computer to the phone in the truck without being set again.
  • It is a personal choice, not an organization setting. A yard where half the drivers read French and the office runs in English is normal, and each person picks for themselves.
  • A visitor who has never chosen gets the language their browser asks for, so a francophone landing on the site reads French without hunting for a dropdown. Anything not confidently French stays English rather than guessing.
  • Dates and numbers follow the choice too — Canadian formats in both languages, never France’s.
Changed
  • This release is the mechanism, not the translation. Most screens are still English whichever language you pick, and the app is being translated in batches from here. Anything not yet translated shows its English wording rather than a blank or a code, so nothing becomes unusable in the meantime.
  • Regulatory wording is a deliberate exception and will not be machine-translated. Defect criteria, standard citations and the like will be taken from the official French publication or left in the language they were published in — a driver at a roadside check needs the inspector’s words, not our version of them.
v2.430August 25, 2026

Pull hours says when the device is reporting its operating zone

Changed
  • A pull that finds operating zone records but no duty status now says so, and says which side of latitude 60 they named. Before it reported only that nothing could be filed, which read as though the whole response were noise — when in fact the device was answering a question the log book otherwise has to be conservative about.
  • Those zone records are counted whether or not they name a driver we can attribute them to. One that cannot be attributed still cannot be applied to anybody’s entries, but it is still evidence the device reports the zone.
v2.429August 25, 2026

Hours from a device now know which side of 60 they were driven on

Fixed
  • Geotab records which operating zone a vehicle is in — Canada south of 60, north of 60, or the United States — and sends it on the same feed as the duty status. We were discarding it as “not a duty status”, which was half right: it is not an entry in the log, but it is the device saying which hours of service rules the driving after it falls under. Discarded, every day imported from a device was measured against the southern rules whatever the truck was actually doing.
  • Imported entries now carry the zone the device reported, and the day is measured against the part that applies to it. Pull hours reports how many zone changes it read; where it read none, it says so, and the entries are measured against the southern rules, which are the stricter.
  • A driver whose Geotab rule set was one of the north-of-60 pair got no hours of service cycle at all and silently fell back to the organisation default — the check was for an exact match on the southern rule set names. The northern rule sets, and the team variants of all four, are now recognised.
Added
  • A day whose hours came from a device and whose feed never said which side of the parallel it was on now says so on the screen, rather than showing a confident clean day. Only for carriers who operate somewhere that reaches above 60.
v2.428August 25, 2026

The log book knows which side of 60 you are driving on

Fixed
  • Every day in the log book was measured against the hours of service rules for driving south of the 60th parallel, whoever recorded it. A driver working north of 60 was told they were over a limit that does not apply to them at 14 hours driving, marked short of a daily off-duty total that Part III of the standard does not contain, and shown a cycle 1 ceiling of 70 hours when theirs is 80.
Added
  • If your carrier profile includes a jurisdiction reaching above the parallel, recording a duty status now asks which side you are driving on. It stays on your last answer until you change it, since a driver who has crossed is usually up there for days.
  • The day is measured against the part that applies, and the day panel says which one: 15 hours driving and 18 on duty north of 60, a 20-hour elapsed limit, an 80-hour cycle 1, and no daily off-duty total at all beyond the 8 consecutive hours both sides require.
  • A day whose driving happened on both sides is labelled Crossed 60 and measured against the southern limits, which are the stricter. The standard is written in respect of driving and does not say which part governs a mixed day, so anything flagged on one is presented as a prompt to check rather than as the standard’s answer.
Changed
  • A carrier who never operates above the parallel is not asked the question, and their log book reads exactly as before. An entry recorded before this shipped, or one where nobody said which side, is read as southern — the conservative reading, which can only ever over-report.
v2.427August 25, 2026

Photograph a ticket straight onto the requirement it answers

Added
  • Every row in a driver’s Required training panel now has its own button. Press it and a window opens for that one requirement, already named and showing the clause it comes from, and asks for the completion date, the certificate number, who ran it and a copy of the ticket — taken with the phone camera or uploaded as a file or PDF.
  • The expiry fills itself in from the renewal period that requirement is tracked on, so a dangerous goods certificate dated today is set three years out without anybody having to know that. It stays editable, and a requirement with no fixed renewal period is not asked for one at all.
  • The record is filed against the requirement it answers, so the row changes as soon as it is reviewed. Adding the same certificate through Add a document left it in the file as a paper nobody had connected to anything, and the panel went on saying the requirement was missing.
  • Drivers see the Required training panel on their own file under Fleet → My driver file, with the same buttons. A driver may add to their own file and nobody else’s, and the person holding the ticket is the one who can photograph it.
Changed
  • The knowledge base article on CVOR no longer says we do not calculate your rate. It now explains the two figures on that screen — the Ministry’s, typed off your abstract, and our estimate of where you stand between abstracts — and why they are kept apart.
  • The log book article now covers the 16-hour rule it already checks, that a driver’s cycle is switched from their own file, and what a switch costs in rest. Its note on driving north of 60 is corrected: the app holds the northern limits and the settings screen explains them, but the log book still measures a day against the southern set, so a driver running north should read their day against the northern limits themselves.