D
DUTYPROOF
See Single Audit
Inside DUTYPROOF

How a job description becomes a defensible NOC.

Three steps. Four engines. One paper trail you can hand to the regulator. Here is exactly what happens between the moment you paste and the moment you get a verdict.

The process

From job description to defensible NOC, in three steps.

No forms. No dropdowns. Paste what your client gave you.

Step 01

Semantic candidate search

Paste any job description, any length, any format. The engine finds the closest matching NOC codes by meaning, not keywords. Titles, duties, and employment context are all weighted independently.

516 NOC nodes · Voyage embeddings
Step 02

Targeted refinement questions

When candidates are close, the system asks precise binary questions about supervisory scope, budget authority, job titles on pay stubs. Ambiguity drops with each answer until the field narrows to one defensible code.

Entropy driven disambiguation
Step 03

Legal compliance engine

The shortlisted code runs through a deterministic rule engine that encodes principles derived from Federal Court decisions. Exclusion clauses are checked. Lead statement coverage is scored. Risk flags are raised with the precedent that motivates them cited inline.

FC precedents · NOC 2021 rules
Under the hood

Four engines. One defensible outcome.

DUTYPROOF is a layered compliance system. Not a chatbot, not a search tool. Each engine has one job and a clean audit trail.

01

Plagiarism trap

Detects when a job description copies or paraphrases the NOC definition itself, the most common red flag in IRCC audits. Real duties have to reflect real work, not the manual.

02

Exclusion scanner

Every NOC unit group lists occupations that are explicitly excluded. The engine matches your client's duties against these clauses and flags conflicts before you submit.

03

Diagnostic wizard

When top candidates are close, a structured decision process asks targeted binary questions, narrowing the field to a single defensible recommendation in three to five rounds.

04

Legal rule engine

Federal Court decisions, exclusion clauses, and lead statement checks run as deterministic rules. Every trigger is logged in your audit trail with the rule and the precedent attached.

FAQ

Questions RCICs actually ask.

The manual tells you what a code means. DUTYPROOF tells you whether your client's job description actually qualifies, and flags the exact reasons an officer might disagree, citing the specific clauses and precedents that apply.
Yes. The compliance engine is built on NOC 2021 and applies to any stream that requires a NOC code. Express Entry, LMIA based work permits, most PNP streams, and CEC. The audit report is stream agnostic.
The system flags specific gaps, missing mandatory duties, exclusion clause risks, weak lead statements, and generates targeted questions to resolve ambiguity. You will know exactly what documentation to request from your client.
No. Job descriptions you submit are processed in real time and never persisted. We do not train on client data, and we are not in a position where any third party model provider could either.
The rule engine is updated by the team when Federal Court decisions materially change how NOC exclusion clauses are interpreted. Every audit report cites the decisions it applied so you can verify them yourself.
Yes. The full audit trail, every scoring decision, every legal rule triggered, every diagnostic question asked, can be exported as PDF. It is designed to sit in your file as evidence of due diligence.
No. It is a structured second opinion that surfaces every issue an officer would surface. You still make the call. The audit trail makes that call defensible.

Run your first audit.

Start with one defensible NOC audit: paste the job description, resolve the close calls, and download the final memo when it is ready.

See Single Audit Back to home