Canada
Canada has no federal AI statute. What it has, for the institutions where AI decisions carry the most consequence, is a model risk guideline with a date on it. OSFI Guideline E-23 takes effect on 1 May 2027, and the 2025 revision brought artificial intelligence and machine learning explicitly inside its scope.
That single fact reorders most Canadian AI governance conversations. The question is not whether regulation is coming. For a federally regulated institution it has arrived, it is specific, and the transition period is already running.
What is actually in force.
Listed by what binds you rather than by what is discussed. Verified at publication; verify again before you rely on it, because these move.
Instrument by instrument. The same 24 rows Concylium returns when an assistant asks what binds AI systems in Canada, each checked against its official source on 11 Oct 2026. No federal statute specifically governing AI systems is in force. AIDA (Part 3 of Bill C-27) died when the 44th Parliament, 1st session ended on 6 Jan 2025 (LEGISinfo). Its successor, Bill C-36 (introduced 15 Jun 2026), is a privacy bill (PPCDA) with automated-decision-system transparency provisions, not an AI act. LEGISinfo shows it at second reading with no activity yet. The 'AI for All' national strategy (4 Jun 2026) says new legislation will come 'over the next five years' but names no AI bill. One nuance: Bill C-16 (Protecting Victims Act, S.C. 2026, c. 19) now names 'artificial intelligence software' in the Criminal Code's intimate-image definition. That is a criminal offence about content, not a regime governing AI systems.
| Instrument | Applies to | Status | Official source |
|---|---|---|---|
| Guideline E-23 - Model Risk Management (2027) Office of the Superintendent of Financial Institutions (OSFI) | Banking | Developing effective 1 May 2027 | osfi-bsif.gc.ca |
| Guideline B-13 - Technology and Cyber Risk Management Office of the Superintendent of Financial Institutions (OSFI) | Banking | In force since 1 Jan 2024 | osfi-bsif.gc.ca |
| Guideline B-10 - Third-Party Risk Management Office of the Superintendent of Financial Institutions (OSFI) | Banking | In force since 1 May 2024 | osfi-bsif.gc.ca |
| Personal Information Protection and Electronic Documents Act (PIPEDA), S.C. 2000, c. 5 Office of the Privacy Commissioner of Canada (OPC) | Data | In force since 1 Jan 2001 | laws-lois.justice.gc.ca |
| Principles for responsible, trustworthy and privacy-protective generative AI technologies (December 2023) Office of the Privacy Commissioner of Canada with all provincial and territorial privacy commissioners | Data | Guidance since 7 Dec 2023 | priv.gc.ca |
| Bill C-27 (44-1), Digital Charter Implementation Act, 2022 (CPPA, Personal Information and Data Protection Tribunal Act, Artificial Intelligence and Data Act) Parliament of Canada (sponsor: Minister of Innovation, Science and Industry) | Cross-sector | Lapsed | parl.ca |
| Bill C-36 (45-1), An Act to enact the Protecting Privacy and Consumer Data Act, to amend the Personal Information Protection and Electronic Documents Act and to make amendments to other Acts Parliament of Canada (sponsor: Minister of Artificial Intelligence and Digital Innovation) | Data | Developing | parl.ca |
| Directive on Automated Decision-Making (amended 24 June 2025), with the mandatory Algorithmic Impact Assessment tool Treasury Board of Canada Secretariat | Public sector | In force since 24 Jun 2025 | tbs-sct.canada.ca |
| Guide on the use of generative artificial intelligence (second version) Treasury Board of Canada Secretariat | Public sector | Guidance | canada.ca |
| Guide on the Use of Agentic Artificial Intelligence (May 2026) Treasury Board of Canada Secretariat | Public sector | Guidance since 22 May 2026 | canada.ca |
| Voluntary Code of Conduct on the Responsible Development and Management of Advanced Generative AI Systems (September 2023) Innovation, Science and Economic Development Canada (ISED) | Cross-sector | Guidance | ised-isde.canada.ca |
| Have your say on advancing AI transparency in Canada (public consultation, 2026) Innovation, Science and Economic Development Canada (ISED) | Cross-sector | Developing | ised-isde.canada.ca |
| CSA Staff Notice and Consultation 11-348 - Applicability of Canadian Securities Laws and the Use of Artificial Intelligence Systems in Capital Markets Canadian Securities Administrators (CSA) | Securities | Guidance since 5 Dec 2024 | osc.ca |
| Pre-market guidance for machine learning-enabled medical devices Health Canada | Health | Guidance since 1 Apr 2026 | canada.ca |
| Act respecting the protection of personal information in the private sector (CQLR c. P-39.1), ss. 12.1 and 8.1, as amended by S.Q. 2021, c. 25 (Law 25 / Bill 64) Commission d'accès à l'information du Québec · Quebec | Data | In force since 22 Sept 2023 | legisquebec.gouv.qc.ca |
| Guideline for the Use of Artificial Intelligence (March 2026) Autorité des marchés financiers (AMF) · Quebec | Banking | Developing effective 1 May 2027 | lautorite.qc.ca |
| Model Risk Management Guideline (June 2025) Autorité des marchés financiers (AMF) · Quebec | Banking | In force | lautorite.qc.ca |
| Enhancing Digital Security and Trust Act, 2024, S.O. 2024, c. 24, Sched. 1 (Bill 194), ss. 5-8 Government of Ontario (Minister of Public and Business Service Delivery and Procurement) · Ontario | Public sector | Developing | ontario.ca |
| Employment Standards Act, 2000, S.O. 2000, c. 41, s. 8.4 (added by Working for Workers Four Act, 2024, S.O. 2024, c. 3, Sched. 2) Government of Ontario (Ministry of Labour, Immigration, Training and Skills Development) · Ontario | Employment | In force since 1 Jan 2026 | ontario.ca |
| Responsible Use of Artificial Intelligence Directive Management Board of Cabinet (Ontario) · Ontario | Public sector | In force since 1 Dec 2024 | ontario.ca |
| The Public Sector Artificial Intelligence and Cybersecurity Governance Act, S.M. 2026, c. 43 (Bill 51, 43-3) Legislative Assembly of Manitoba (sponsor: Minister Moroz) · Manitoba | Public sector | Developing | web2.gov.mb.ca |
| The Business Practices Amendment Act, S.M. 2026, c. 41 (Bill 49, 43-3) Legislative Assembly of Manitoba (sponsor: Minister Sandhu) · Manitoba | Cross-sector | In force since 1 Jul 2026 | web2.gov.mb.ca |
| Policy on the use of generative AI Government of British Columbia (BC Public Service) · British Columbia | Public sector | In force | digital.gov.bc.ca |
| Responsible Artificial Intelligence Policy Framework for the B.C. Health Sector British Columbia Ministry of Health · British Columbia | Health | Guidance | www2.gov.bc.ca |
The inventory is the hard part.
Most institutions read E-23 and plan a validation programme. The validation is tractable. What catches people is the inventory standard underneath it, because an inventory is only as good as its ability to answer a question after the fact.
An inventory that lists models is not an inventory. It has to carry the risk rating, the owner, the validation status, the approval and its date, and enough lineage to answer what changed and when. For AI systems that last requirement is where conventional model risk management breaks: the model is not the only thing that varies. The prompt changes, the retrieval corpus changes, the routing policy changes, and none of those is a deployment. An inventory blind to them is describing a system that no longer exists.
That is an architecture problem rather than a documentation problem, which is why the two halves of this practice are the same job. Governance the platform emits as it runs will still be true in May 2027. Governance maintained by hand will be stale by the second validation cycle.
Where to start.
Canada, answered.
When does OSFI Guideline E-23 take effect, and who does it apply to?
OSFI released the 2027 version of Guideline E-23 on 11 September 2025 and it takes effect on 1 May 2027, after an eighteen-month transition. It applies to federally regulated deposit-taking institutions and insurers, including branches. It does not apply to federally regulated pension plans. The date matters more than it looks: eighteen months is enough time to build a model inventory and not enough to build one twice, so the sequencing decision you make now is the one you live with.
Does E-23 cover AI and machine-learning models, or only traditional ones?
Both, and the 2025 revision is largely about making that explicit. The scope is all models that carry risk to the institution, which is deliberately broader than a list of model types, and the guideline adds context specifically for AI and machine learning. The practical consequence is that a model whose behaviour is learned rather than specified still has to be inventoried, risk-rated, validated and monitored, and the fact that nobody can read its logic is your problem to solve rather than an exemption.
Is AIDA law in Canada?
No, and this is worth being exact about because a great deal of advice assumes otherwise. The Artificial Intelligence and Data Act formed part of Bill C-27, which died on the Order Paper in January 2025 when Parliament was prorogued. It was never voted on. There are no AIDA obligations, no AIDA fines, and no AIDA compliance deadline, and Canada has no federal AI statute of any kind. Anyone selling AIDA readiness is selling a bill that does not exist. The exposure that is real comes from OSFI E-23, privacy law, and the extraterritorial reach of the EU AI Act.
What actually applies to a Canadian organisation today?
It depends which one you are. A federally regulated financial institution has OSFI E-23 from May 2027, alongside the existing operational-risk and third-party guidelines. Any private-sector organisation has PIPEDA, and provincially, Quebec Law 25. A federal government institution has the Treasury Board Directive on Automated Decision-Making, which has applied for years and is the closest thing Canada has to an AI-specific rule. An Ontario public-sector institution has Bill 194, in force since 1 July 2025. And any organisation whose output reaches the European Union is inside the EU AI Act regardless of where it sits.
What does a model inventory have to show?
E-23 sets a minimum standard for it, which is the part most institutions underestimate. An inventory that lists models is not an inventory; it has to carry the risk rating, the owner, the validation status, the approval and its date, and enough lineage that you can answer what changed and when. For AI systems the hard part is usually that the model is not the only thing that varies: the prompt, the retrieval corpus and the routing policy change without a deployment, and an inventory blind to those describes a system that no longer exists.
Where do you fit into this?
Independent assessment and architecture rather than a compliance filing. The Teardown scores the estate against the four MESA layers and produces a board-ready reading of where you actually are, which is the input to an E-23 programme rather than a substitute for one. The architecture work is the other half: governance that the platform enforces at runtime rather than a policy document describing one, because an inventory maintained by hand goes stale between validations.
What this page cannot do.
- This is architecture and governance advisory. It is not legal advice, and it does not substitute for your counsel or your relationship with your regulator.
- Regulatory dates and obligations here were verified at publication and they move. OSFI E-23 in particular is a 2027 guideline with a transition period; check the current text at OSFI before you rely on anything above.
- Meeting E-23 is a supervisory judgement made by OSFI, not a certification anyone sells. No engagement described here delivers compliance, and nobody honest offers one that does.
- Engagements are delivered personally, through iSystematic Inc.
- The reference architectures in the published series are set in a deliberately fictional institution so the method can be shown in full. They are not deployed client products, and client engagements are confidential.
Eighteen months is not long.
The transition period is enough time to build a model inventory once. It is not enough to build one, discover it cannot answer a lineage question, and build it again. The sequencing decision is the one that matters, and it is cheapest now.
The Fit Call is thirty minutes and free, and it qualifies the work in both directions. If what you need is a validation vendor rather than an architect, you will be told that on the call.
Ask your AI assistant instead.
This page is a snapshot, accurate at the release it cites. The same corpus is callable, publicly and without a key, so an assistant can query it live and return an answer carrying the source it came from. For this page that is lookup_regulation, which returns the instruments actually in force for a jurisdiction, with the release they were extracted from (for Canada, the official source each was checked against and the date). It answers “None issued” where a regulator has issued nothing, which is the case for a banking AI directive in Saudi Arabia and for an AI regulation in Bahrain. That is the specific claim general models tend to get wrong, so it is worth checking against rather than paraphrasing this page.
claude mcp add --transport http concylium https://mcp.nabeelkhan.com/api/mcp
Claude Desktop, ChatGPT, Cursor, VS Code and Gemini CLI take the endpoint on its own: https://mcp.nabeelkhan.com/api/mcp. No key, no account, nothing to sign. Setup for every client and every tool, in its own words; each call is logged by tool, outcome and duration only, never with what you asked.
“Using Concylium, list what actually binds an AI system deployed in Canada today, and separate what is in force from what is only guidance.”
In force and guidance are different obligations, and most summaries flatten them. Where a regulator has issued nothing, the answer says so rather than naming something plausible.