Most immigration software is built by people who've never sat across the table from a Pre-Removal Risk Assessment client. Meridian was built inside a working RCIC practice in Abbotsford, BC - by people who file IMM 5710s every week.
Built by a working RCIC, in a working RCIC's office.
Founder & CEO, Nova System Inc. · Managing Partner, Waymark Immigration · RCIC R1034253 · Abbotsford, BC
"Every feature went through one filter: would I use this on a real case before lunch tomorrow? If the answer was no, it didn't ship."
Three moments every working RCIC recognizes - and what Meridian does in each one.
It's 11 pm. A client calls - their work permit expires in three days and they're outside Canada. You haven't pulled the file in two months and can't remember which provincial program they were on.
Aurora surfaces the case summary on your phone with one tap; the timeline shows exactly where things stand - no laptop. (Today: case summary + push. Click-to-call is on the roadmap.)
It's 7 am. IRCC quietly updated a checklist overnight - a new supporting document is required and a form revision date changed. Three active cases were preparing the old version.
Meridian's stale-form watcher checks IRCC forms on a schedule and flags cases referencing an old revision. (Live cron worker; email digests today, instant paging on the roadmap.)
An H&C file. The client needs physical presence in Canada to the day over five years - a stack of stamped passports, an old CBSA printout, and a client unsure about a 2022 trip.
Drop the CBSA traveller-history PDF into the case file - the document classifier files it and surfaces it in the timeline. (Full presence calculator on the Polaris roadmap.)
If any of these is missing, the tool isn't ready for RCIC work. We were stubborn about all four from day one.
Sukhveer is a working consultant at Waymark Immigration; Arshdeep is the supervising RCIC. Every feature came out of a real case - including the ones that took weeks to file because the existing tool couldn't handle them.
Audit trail on every record, tenant data isolation, retainer scaffolding, and conflict-of-interest detection on the lead-to-case path. We built around the CICC Code of Professional Conduct, not as an afterthought.
190+ IRCC forms, each field tied to the exact IMM line it maps to. A stale-form watcher checks revision dates automatically; the filler completes the fields it can verify and asks for the ones it can't.
Cloudflare infrastructure with Canadian data residency where the underlying service supports it. PIPEDA, BC PIPA, and provincial privacy obligations baked into the data model. SOC 2 is on the roadmap, not yet certified - we say so on the security page.
If the tool you're evaluating can't tick every item below, it isn't ready for RCIC work - full stop. We held ourselves to the same list.
Firm A can never see Firm B's data. Enforced on every database query - not "in the dashboard layer". The single biggest CICC liability if it's wrong.
Tools that nudge you toward unauthorized practice are a regulatory problem. Your software should know which surfaces are RCIC-only.
If a complaint is filed, can the tool produce a tamper-evident log of who did what, when, to which file? Required, not optional.
Your retainer agreement needs to name every sub-processor. The vendor must give you a current list - not redirect you to "ask sales".
Vendors that claim "SOC 2 compliant" without a Type II report are dressing up. We're on the roadmap, not certified yet - and we say so.
When a new lead comes in, the tool screens for prior files referencing the same employer, sponsor, or address - before you take retainer.
If retainer funds touch the platform, it needs trust-account separation, reconciliation, and reporting that satisfies your provincial rules.
If a feature is on the roadmap, the site should say so. If a screenshot is a mockup, it should be labelled. Anything else is a misrepresentation you'll inherit.
Every box ticked - no asterisks. If you find an item we don't pass, tell Sukhveer directly: [email protected]
Three surfaces. One product. Built for the daily reality of an immigration practice.
Where you spend your day. Cases stream in as IRCC updates land. A Next-Best-Action rail sits beside every file so the obvious next move is one click away. Built for a 6-hour day, not a 6-day onboarding.
Your practice, in your pocket. Today, deadlines, pending docs, ask-the-AI - the four things you need before a coffee runs cold. The phone is for triage; the laptop is for the paperwork.
The widget on your firm site. A floating pill with entry-points - AI chat, booking, radar, news, forecast, and WhatsApp (coming soon) - all wired to the same case backend as the CRM. Visitors talk to your firm, not a generic widget.
Founder & CEO, Nova System Inc. · Managing Partner, Waymark Immigration · RCIC R1034253 · Abbotsford, BC
"I built Meridian because I needed it for my own practice. I file IMM forms every week. Every feature went through one filter: would I use this on a real case before lunch tomorrow? If no, it didn't ship."
RCIC · Testing & Advisory · Member, CICC
"I tested every legal-reasoning AI surface against real refusal letters and Procedural Fairness Letters from cases I've handled. If the AI gets something wrong on a regulated surface, I want to know first - and we built the review queue so I do."
A direct setup line to Sukhveer, migration assistance from your current tool, and a standing 30-minute monthly check-in for your first quarter. Monthly billing, cancel anytime.
Honest answers. If we don't pass on something, we say so.
Every database query is scoped to your firm's tenant ID - Firm A literally cannot read Firm B's rows because the query won't return them. Every privileged action lands in an audit log you can export. For the technical details - SSL Labs A+, Mozilla Observatory A+, and the multi-tenant query enforcement - see the security page.
Yes. Every tenant can export the full set of records (cases, clients, documents, notes, audit log) at any time as a structured archive. There's no lock-in clause in the MSA. If Nova ceases operating, the agreement requires a final export window before any data is destroyed.
GCMS notes: yes - drop the ATIP-returned PDF into the case file and the document classifier files it under the GCMS-notes slot. IRCC PR Portal: no direct integration (the portal exposes no public API). We structure your case data so the form fields are ready to copy when you sit down at the portal. Direct portal automation isn't on the near roadmap because IRCC doesn't currently sanction it.
The current sub-processor list is published at sub-processors and referenced by the Data Processing Addendum. Both are linked from the footer of every page.