Who is the CIRO compliance documentation guide for?
This Guide Is for You
Who This Is For
This guide is written for individual advisors at CIRO-regulated dealers. Not for compliance teams. Not for supervisors. For you.
Whether you work at an investment dealer or mutual fund dealer, the documentation obligations covered here apply to your daily practice. The Client Focused Reforms shifted significant responsibility to individual registered representatives. Understanding exactly what that means for your documentation practices is no longer optional.
Audience Clarification
This guide addresses individual registered representatives and investment advisors at CIRO-regulated investment dealers and mutual fund dealers. Compliance officers, supervisors, and firm-level obligations are outside scope. If you hold client relationships and make recommendations, this guide is for you.
What This Covers
This guide addresses six areas of documentation practice:
- Why documentation protects you personally under the Client Focused Reforms
- Specific KYC documentation requirements, including the risk tolerance versus risk capacity distinction
- How to document suitability determinations in audit-ready format
- What counts as "books and records" and how long you must keep them
- Evaluating AI tools for documentation without creating compliance risk
- Practical first steps to improve your documentation system
When CIRO, PIPEDA, or Law 25 changes, the Dispatch explains what it means.
Once a month: what is changing across CIRO, PIPEDA, and Quebec Law 25, and what it means for advisors using AI tools. A five-minute read.
Subscribe, freeWhat This Doesn't Cover
This guide does not address supervisor-level obligations, trading conduct rules, registration requirements, or deep analysis of PIPEDA and Quebec Law 25 (those are covered in separate resources).
How to Use This Guide
Read straight through for complete understanding, or jump to specific chapters using the table of contents. Each chapter delivers standalone value. The full read takes 15-20 minutes; scanning the key frameworks takes 5 minutes.
Documentation requirements can feel like bureaucratic overhead. Before diving into specifics, it helps to understand why these requirements exist and what they protect.