CASL compliance for real estate brokerages

BF

The BrokerFold Team — Product + Engineering

Last reviewed

On this page

Reviewed against primary sources (CRTC CASL guidance, including the Compliance and Enforcement Bulletin on liability for third-party and employee violations, crtc.gc.ca, accessed 2026-08-14 / ISED consent guidance, Canada's Anti-Spam Legislation, accessed 2026-08-14) — last reviewed August 14, 2026. This page is general information, not legal advice.

Working late at an office desk reviewing email and records on screen

CASL turns a brokerage into the compliance perimeter for every commercial email and text its people send: organizations are vicariously liable for violations by employees and agents acting within the scope of their authority, and officers who direct or acquiesce in a violation carry personal exposure on top. Forty agents each running their own follow-up habits is therefore not forty separate risks — it is one organizational risk with forty inputs, and it is managed the way regulators say it must be: with a real, documented, actively run compliance program.

The rules your agents are operating under

The sender-level law is unchanged by scale, and it is covered in depth in can I email leads under CASL: consent before sending — express, which endures, or implied, which expires on a clock (roughly six months from an inquiry, roughly two years from an existing business relationship); identification of the sender including the brokerage; and a working unsubscribe honoured within ten business days. The burden of proving consent sits with the sender. The brokerage-level problem is that “the sender” is functionally you, across every database your agents have accumulated — including the ones they imported from sources nobody can reconstruct. The definitional groundwork lives in the CASL glossary entry.

The due-diligence defence is the whole game

CASL’s section 33 defence excuses an organization that exercised due diligence to prevent the violation — and CRTC guidance is blunt that a set-it-and-forget-it program does not qualify. What counts is a program proportionate to your risk, actually operated: a written policy agents acknowledge, training that happens on a cycle rather than once at onboarding, consent recorded at the moment of capture, monitoring that would notice a rogue campaign, and a record of all of it. The defence is built before the complaint, from artifacts with dates on them. A brokerage that cannot produce its program on request effectively does not have one.

Where brokerage programs actually fail

Three recurring holes. Imported lists: an agent joins with a spreadsheet of two thousand “contacts” whose consent history is folklore, and it flows into the shared database untagged — tag-or-quarantine at import is the fix. Fragmented tooling: consent captured in one system, sends fired from three others, unsubscribes honoured in some — consent state must travel with the contact, not with the tool. And silent automation: sequences configured years ago that keep mailing implied-consent contacts long after the window lapsed, because no clock was ever wired to the send.

What centralized machinery looks like

This is the strongest operational argument for one brokerage-wide platform, and it is why we built the sending path the way we did. BrokerFold’s CRM records consent per contact — source, date, and type — checks a gate before any automated message leaves, treats unsubscribes and suppressions as permanent and senior to every other signal, tracks implied-consent expiry, and prompts for re-permission before a window closes. Nurture sequences are review-gated: nothing sends until a human has looked at the plan and turned it on. Compliance footers ride every message by construction. The category criteria are laid out in CASL-compliant CRM, and the org-level visibility questions — who can see and mail what, across seats — in brokerage CRM.

A brokerage starting from zero

Sequence it: write the one-page policy; pick the system of record and consolidate sending into it; import databases through a consent triage rather than around it; turn on suppression checking everywhere; train the roster; put a semi-annual review on the calendar and log it. CASL also covers SMS, so the texting your agents do from personal phones belongs inside the same program, not outside it. This is education rather than legal advice — the CRTC’s guidance and your counsel govern the specifics — but the direction is settled: consent-tracked, centrally gated sending is both the defence and the better marketing practice.

Frequently asked questions

Are agents 'employees' for CASL liability if they're independent contractors?

The vicarious-liability language reaches employees and agents acting within the scope of their authority, so contractor status is not the shield brokerages hope it is. An agent emailing prospects under your brokerage's name, on databases your systems hold, is squarely the scenario the provision contemplates. Plan as if every agent's send is your send.

Does one CRM unsubscribe cover all the brokerage's sending?

It should, and building it that way is the point: an unsubscribe is a withdrawal of consent from the recipient, and honouring it only in the tool that captured it while another sequence keeps mailing is exactly how complaints arise. A shared suppression layer that every automated send checks is the defensible architecture.

What penalties are actually on the table?

Administrative monetary penalties run to $1 million per violation for individuals and $10 million for organizations, and the CRTC has issued real penalties for consent and unsubscribe failures. Directors and officers who authorized or acquiesced in a violation can be personally liable. Enforcement typically begins with complaints to the Spam Reporting Centre.

Keep reading

Fold your stack into one.

14 days free. No credit card. Your data stays yours.