When a Quebec inspector shops for inspection management software, the first decision — before features, before price — is usually architectural: cloud-native (runs in the browser, nothing to install) or desktop-installed (lives on a specific OS, often with cloud sync running in the background). The choice looks technical, but it touches three concrete issues for an inspector: BNQ 3009-500 compliance, the mandatory archiving of the inspection file, and field mobility. With the October 1, 2027 REIBH certification deadline approaching, these aren't abstract concerns anymore.
What "cloud-native" and "desktop" actually mean here
- Cloud-native software: the application runs in the browser. No install. Data is stored on remote servers the moment it's entered. The inspector can work from any device with a modern browser — desktop, laptop, tablet, phone.
- Desktop software: the application is installed on a specific OS (usually Windows or macOS). Work happens primarily locally; data lives on the machine. Most modern desktop tools offer cloud sync, but the source of truth is still the local workstation.
- Hybrid: a variant of desktop where some work (intake forms, delivery, client portal) happens in a browser, but report editing itself stays local.
The distinction matters because it determines what happens when you change devices, when your computer crashes, when you go on vacation, and — most importantly — when the RBQ or a requester asks to review your inspection file.
At a glance: the three architectures compared
| Criterion | Cloud-native | Desktop | Hybrid |
|---|---|---|---|
| Install required | No — runs in any modern browser | Yes — OS-specific installer | Yes, plus browser surfaces for some features |
| BNQ 3009-500 file archiving | Automatic, every entry written to the file immediately | Manual discipline + working sync + intact local disk | Partial — depends on which surface the inspector used |
| Multi-device workflow | Immediate, any browser, any device | Constrained by sync timing; source of truth is the workstation | Split: browser parts mobile, desktop parts stay on the machine |
| Updates when BNQ/REIBH change | Automatic on next login | Manual download + install per workstation | Automatic for browser parts, manual for desktop |
| Internet required to work | Yes (with offline buffer on some vendors) | No — local work continues without connectivity | Yes for browser parts, no for desktop |
| Data residency responsibility | Vendor-managed (ask where servers are hosted) | Inspector-managed (on your own disk) | Mixed — depends on which component |
| Typical best fit | Solo, teams, and firms | Solo with disciplined archiving, zero-monthly-cost preference, poor field connectivity | Solo inspectors already invested in an iOS or iPad companion |
The rest of this article walks through the four issues where the architectural choice actually bites for a Quebec inspector in 2026.
Issue 1: the archiving required by BNQ 3009-500
Chapter 10 of BNQ 3009-500 requires the inspector to keep a complete file for every job. That file must contain all objective evidence gathered during the inspection — photos, notes, annotations, recordings, sketches — including evidence that never made it into the final report delivered to the requester. We cover this requirement in detail in our article on objective evidence and the inspection file.
In a cloud-native workflow, this archiving is structurally hard to miss: every photo taken in the field, every typed note, every annotation is written to the file the moment it's created. No manual action required.
In a classic desktop workflow, archiving rests on three stacked conditions: (1) files are correctly placed in the project structure, (2) cloud sync is turned on and working, and (3) the local machine doesn't fail before sync has run. If any of those three conditions breaks — a photo left in the "Downloads" folder, a dead SSD, a lagging sync — the file is incomplete. And an incomplete file in front of an RBQ inquiry is a concrete risk.
Issue 2: mobility and multi-device work
A modern inspection day often looks like this: client intake on a desktop Monday, field inspection with a phone Tuesday, report writing on a laptop Tuesday evening, a quick review from the living-room tablet Wednesday morning before delivery. This is a frequent reality, not an edge case.
A cloud-native tool handles this day without friction: the file state is the same across every device within seconds. A desktop tool forces a detour: sync has to propagate, or the inspector has to stay on the same machine throughout.
The cost isn't just ergonomic. A report stuck because "the file is on the other machine" is a report delivered late — and BNQ 3009-500 (article 9.1) requires the report to be delivered within the window set in the service contract. Vacations, hardware failures, device swaps are normal events the tool should absorb without slowing the practice down.
Issue 3: backup and data residency
One aspect often glossed over: where your data is stored and who carries the hosting responsibility.
- Desktop: your data is at your place. Apparent advantage (total control) and real risk (your hard drive is the file). Automatic backups exist, but depend on your own configuration. A ransomware attack on a Windows workstation can lock up months of files.
- Cloud-native: data lives in a managed data center, with redundant backups and infrastructure-grade protection (encryption at rest, firewalls, access control, SOC 2 auditing). Downside: you depend on the vendor for service continuity and data residency.
For a Quebec inspector, the question to ask the cloud vendor is where the data is hosted. Loi 25 (Quebec's personal-information protection law) regulates transfers of personal information out of Quebec and adds obligations when data leaves the province. Hosting in Quebec or Canada limits that complexity.
Issue 4: updates and living compliance
BNQ 3009-500 isn't a frozen document. Article 1 of REIBH provides that modifications published after October 1, 2024 take effect six months after bilingual publication. When the standard evolves — new signs to watch for, new writing requirements — the tool has to follow.
- Cloud-native: the inspector gets the update automatically, next login. No download, no install, no "outdated version."
- Desktop: a new version must be downloaded, installed, and checked against in-progress projects for compatibility. Some inspectors run several versions behind — especially those with multiple workstations.
This isn't theoretical: an inspector producing a report on version 2022 R1 when version 2027 R2 is in force is producing a non-compliant report.
What cloud doesn't solve
Let's be honest. Cloud isn't a universal answer:
- Requires internet in the field — a deep basement or a rural home without cell signal can slow entry. Good cloud tools have a local-buffer mode that syncs on reconnect, but capability varies.
- Vendor dependency — if the vendor's service is down, you're not working. Serious vendors publish uptime SLAs and an incident history; ask for them.
- Recurring cost — cloud is a subscription model by nature. Desktop software may carry a higher upfront cost but no monthly fee. Total-cost-of-ownership math is worth doing honestly on a 5-year horizon.
An inspector whose practice is concentrated in poorly covered areas, or who insists on zero monthly cost, can legitimately prefer desktop — provided they rigorously manage archiving and backups.
What often tips the scale: solo vs team
For a solo inspector working with one or two devices: both architectures are viable when configured properly. The cloud advantage is mostly in reduced archiving risk and fewer multi-device frictions.
For a small team (two or three inspectors sharing client intake, writing, and delivery): cloud becomes the default. Desktop with sync forces you to coordinate who edits which file when — a friction that doesn't pay off in 2026.
For a firm (more than three inspectors, or coordination with admin staff): cloud is the only architecture that holds up without dedicated IT.
The options on the Quebec market
Axiom³ and its three main Quebec competitors sit differently on this axis:
- Axiom³ — 100% cloud-native. No install, hosting in Montreal. The full workflow (client intake, digitally signed agreement, report writing, client portal, delivery) lives in the browser.
- Vesta — hybrid architecture anchored on desktop (Windows, macOS) with a Vesta Go iOS companion for field capture. Some functions — notably report writing — remain tied to the workstation.
- UDATA — web platform for intake and management, with a tablet app for field data capture. Partially cloud.
- Enzo Solution — a web application that produces inspection PDFs through a questionnaire-based workflow, with integrated invoicing.
We've published a detailed comparison of these four options, including the differences around BNQ 3009-500, APCHQ/AIBQ agreements, and pricing.
How Axiom³ addresses the issues above
Axiom³'s architecture was designed around the cloud-native assumption from day one:
- No install — everything happens in a modern browser, on any device, without admin rights.
- Automatic archiving — every photo, note, and annotation is written to the inspection file the moment it's created, as required by BNQ 3009-500 chapter 10.
- Hosted in Montreal — SOC 2 Type II infrastructure, aligned with Quebec's Loi 25.
- Transparent updates — when BNQ 3009-500 evolves, the editor is updated without any action from the inspector.
- APCHQ and AIBQ service agreements generated and digitally signed before the inspection, accessible from any device.
Try Axiom³ for free — 10 inspections, no credit card.
Common questions
Can I work offline with a cloud-native tool?
Some cloud tools offer an offline mode that caches forms and syncs on reconnect. That capability varies by vendor; check specifically how photos and annotations are handled in offline mode.
Is desktop software less BNQ 3009-500 compliant?
Desktop software can be fully compliant — if archiving and backups are rigorously managed. The non-compliance risk is higher because it rests on the inspector's discipline rather than on the architecture itself.
Where is my data hosted if I use cloud software?
That depends on the vendor. In Quebec, Loi 25 governs out-of-province data transfers. Ask the vendor explicitly where their servers are — ideally Quebec or Canada.
Is cloud more secure than desktop?
Both can be secure. Cloud benefits from infrastructure-grade security (encryption, monitoring, SOC 2 compliance) that a lone inspector would struggle to replicate on their own workstation. Desktop is more vulnerable to ransomware and physical device loss, but is protected against vendor outages.
Sources & references
- BNQ 3009-500 standard (free download): bnq.qc.ca
- REIBH — regulation (chapter B-1.1, r. 3.1): LégisQuébec
- Loi 25 — Act to modernize legislative provisions as regards the protection of personal information: Commission d'accès à l'information du Québec
Last verified: April 22, 2026.