Canada: Preparing Your Organization For CASL's Commercial Electronic Message Requirements

The world's toughest anti-spam and malware law, commonly known as Canada's Anti-Spam Legislation (CASL), will come into force in Canada on July 1, 2014.  Organizations must act now to comply with CASL by this fast-approaching deadline.  This article sets out the steps organizations should be taking to achieve compliance with CASL's anti-spam provisions. 

CASL also contains provisions regarding the installation of computer programs on third-party computers.  These anti-malware provisions will come into force on January 15, 2015.  Additional procedures should be taken by organizations that install computer programs on other persons' computers to comply with CASL's malware provisions.  These additional procedures will be the subject of a separate article. 

1. CASL Commercial Electronic Message Compliance Program Objectives

Key objectives of an organization's CASL compliance program should include:

(a)        instilling an understanding of CASL and its requirements within the organization;

(b)        forming the organization's CASL team;

(c)        gaining a thorough understanding of the organization's Commercial Electronic Message (CEM)  practices;

(d)       building data buckets within the organization's information systems for the categorization of CEM consents required and received;

(e)        applying CASL's consent and content exceptions and implied consent scenarios to the organization and its systems and procedures;

(f)        establishing information mechanisms within the organization to track and record information necessary for CASL's content exceptions and implied consent scenarios to apply and to facilitate recipient unsubscribe requests;

(g)        establishing policies and procedures to ensure CASL's content requirements will be followed within the organization;

(h)        ensuring appropriate contracts are in place where the organization shares consents with third parties;

(i)         building a CASL-compliant corporate culture within the organization; and

(j)         establishing the basis for a due diligence defence against future CASL contraventions.

2. What You Need to Know Before Starting

Informed planning will be key to developing an effective CASL compliance program for your organization.  Here are some important aspects of CASL you should consider when planning and carrying out a CASL compliance program.

(a)        Penalties for Non-Compliance, the Due Diligence Defence and the Burden of Proof

Your organization should understand CASL's penalty provisions before commencing its CASL compliance program.  Understanding the potentially significant penalties for contravening CASL will help ensure sufficient internal support and resources are allocated to your compliance program and enable the program to be carried out more effectively.

Non-compliance with CASL may give rise to significant penalties.  Organizations will face administrative monetary penalties of up to $10,000,000 for an offence under CASL.  In addition, a private right of action will come into force as of July 1, 2017 to give persons who have been affected by a contravention of CASL a right to bring an action for damages and a statutory penalty of $200 per offence.  This raises the potential for class actions suits for CASL contraventions.

Liability for CASL contraventions may extend beyond the corporate veil.  CASL specifically extends liability to the officers, directors and agents of a corporation that contravenes CASL if they directed, authorized, assented to, acquiesced in or participated in the contravention1

Fortunately for those individuals, however, CASL provides a due diligence defence.  No person is liable for a violation under CASL where they establish that they exercised due diligence to prevent the commission of the violation2.  The organization's CASL compliance program should therefore be well planned, executed and documented to provide the basis for a future due diligence defence, if one ever becomes necessary.

Under CASL, organizations that claim they have the consents required by CASL bear the burden of proving this.3  As a result, obtaining and recording the necessary consents and keeping track of them in up-to-date information systems will be crucial elements of CASL compliance.

 (b)       What is a Commercial Electronic Message (CEM)?

CASL defines a CEM as an electronic message that has, as one of its purposes, the encouragement of participation in a commercial activity4.  CEMs specifically include electronic messages that are sent to promote a person as being someone who conducts a commercial activity.  It is not necessary that the commercial activity have the expectation of profit.  Two-way voice communications, facsimile messages and voicemail messages sent to telephone accounts are excluded from CASL's anti-spam provisions5.

(c)        CASL's commercial electronic message requirements

CASL's anti-spam provisions can be summed up as follows.  After July 1, 2014, persons that send CEM's to electronic addresses in Canada must ensure the CEM's contain prescribed content identifying the sender and permitting the recipient to unsubscribe from further messages in a manner prescribed by CASL.  The senders must have the recipient's express, opt-in consent before sending the CEM.  The aforementioned content and consent requirements will not apply in a limited number of circumstances where exceptions are specified in CASL and its regulations.  In addition, the required consent will be implied in a limited number of circumstances specified in CASL.  Where consent is implied, however, the CEM content requirements will still apply.

For example, CASL provides that consent to receive a CEM is implied where an existing business relationship, as prescribed by CASL, exists between the sender and recipient6  Where this prescribed relationship exists, consent to receive the CEM is implied, but the sender must nevertheless ensure the CEM meets CASL's content requirements, including the prescribed form of unsubscribe mechanism.

A comprehensive review of the various exclusions from CASL's consent and content requirements, and CASL's implied consent scenarios, is outside the scope of this article.  However a high-level summary of these provisions, in decision tree flow chart form, can be downloaded here: ' Canada's Anti-Spam Law: Commercial Electronic Message (C.E.M.) Process Chart' for your everyday reference.Reference to CASL and its regulations or the specific advice of experienced legal counsel will of course be necessary for your organization to ensure it takes full advantage of these provisions. 

 (d)      Privacy consent requirements vs. CASL

It is important for your organization to recognize that the consent requirements under applicable privacy law are different than the consent requirements under CASL.  For example, private sector organizations carrying on commercial activity in Ontario are subject to PIPEDA7.  PIPEDA already requires those organizations to obtain the consent of individuals before using their e-mail addresses or other personal information for commercial activity.  Consent under PIPEDA may be express or implied, depending on the circumstances. 

CASL, on the other hand, will require express consent to send a CEM, subject only to certain prescribed exemptions and prescribed situations where consent is implied, as briefly mentioned above.  Organizations that currently rely on implied consent to send CEMs in compliance with privacy law may find those consents to be insufficient for CASL purposes on and after July 1, 2014. 

(e)        The need to obtain consents before July 1, 2014

Email solicitations for consents to send CEMs will themselves be considered to be CEMs under CASL on and after July 1, 2014.  As such, email consent solicitations sent on or after July 1, 2014 will be subject to CASL's consent and content requirements (and certain content requirements that are unique to solicitations for CASL consent8).  If your organization does not have sufficient consent to send a CEM as required by CASL by July 1, 2014, it will be prohibited from sending CEMs to solicit those consents on or after July 1, 2014 unless one of CASLs prescribed exemptions or implied consent scenarios apply.

3. Key Steps Towards CASL Compliance

(a)        Build Your CASL Team

CASL compliance programs should involve multiple functional areas of the subject organization.  In many cases representatives of your organization's marketing, information technology and human resources functions should be part of the CASL implementation team.  In addition, your organization's legal counsel and chief privacy officer should play a leading role in the CASL preparation process.  In many cases a CASL implementation team should be formed to facilitate participation of each of these functional areas throughout the CASL compliance process.

(b)        Audit Your Current Practices and Consents

The first objective of your CASL compliance team should be to obtain an understanding of, and to document, your organizations' current practices and information systems regarding CEMs.  Specifically, you should determine the following:

(i)         For what purpose does your organization send CEMs?

(ii)        In what form are these CEMs sent?

(iii)       Who sends your organization's CEMs?

(iv)       What procedures do your organization's personnel carry out when sending CEMs?

(v)        Who does your organization send CEMs to?  How are the recipient address databases structured and populated?  How does your organization collect names and electronic addresses for purposes of delivering CEMs?

(vi)       How does your organization currently obtain and track consents and withdrawals of consents for the use of electronic addresses? 

(vii)      Are the consents your organization currently relies on when sending CEMs express or implied?  Does your organization identify and distinguish these categories of consents in its database?

(iix)      Does your organization rely on third parties to have and hold consent to send CEM's on its behalf?  Does your organization send CEMs on behalf of third parties?  If so, does your organization identify the arrangements and agreements with these third parties that support these activities?

(c)        Build Data Buckets

After the audit process is completed, your organization should know which recipients have provided express consent, implied consent, or have withdrawn or otherwise not consented to receive CEMs.  These "data buckets" should be readily identifiable in your information systems. 

Your organization should obtain express consent from each CEM recipient in the implied consent category prior to July 1, 2014, where an exception or implied consent scenario does not apply under CASL. 

Your organization should ensure each express consent it will rely on to send a CEM is sufficiently documented so your organization can discharge the burden of proving it has such consent, if necessary.

Your organization may send CEMs to the recipients in the "implied consent" data bucket after July 1, 2014 as long as an exception or implied consent is valid under CASL at the time the CEM is sent and the recipient has not "unsubscribed" from receiving your organization's CEMs.  To take advantage of this, your organization should establish more specific data buckets delineating the recipients to whom CASL's particular consent exceptions and implied consent provisions apply. 

(d)       Apply CASL's Exceptions and Implied Consent scenarios to your organization

If your organization wishes to send CEMs to recipients under CASL without express consent, it will have to be able to prove an exception or implied consent scenario applies.  The exceptions and implied consent provisions of CASL and its regulations should be applied to the knowledge you gained during your CASL compliance audit to determine when your organization may send a CEM without express consent.  The outcome of this analysis will inform the creation of the CASL exception and implied consent "data buckets" outlined above.

It is recommended that the outcome of this analysis be reflected in a CASL procedures policy.  Your organization's CASL procedures policy should reference the CASL exceptions and implied consent scenarios that may apply to your organization, when they will be considered to apply and how the information necessary to support them is collected and tracked. 

This policy may require some interpretation of CASL's provisions beyond what CASL provides on its face.  For example, consider CASL's consent and content exception for CEMs sent between employees of different organizations concerning activities of the recipient organization9.  This exception applies to CEM's sent by an organization's employee to an employee of another organization, where the two organizations have a "relationship".  CASL does not provide a definition of this "relationship".  Your organization's CASL policy should set out when such a relationship will be considered to exist if your organization plans to rely on this exemption in practice.  

Of course, your policy should be regularly reviewed and updated as case law develops under CASL.

(e)        Establish Information Support Mechanisms

Your organization's information systems will require some particular features for your organization to be considered CASL compliant.  Mechanisms and processes should be created to move electronic addresses between the applicable data buckets to keep them up to date over time.  Most importantly, recipients who withdraw their consent will have to be moved promptly to the "no consent" data bucket.

Where your organization creates data buckets to reflect CASL's consent exceptions and implied consent scenarios, methods of tracking, collecting and organizing the data required to establish that the applicable exception or scenario applies will have to be established and reflected in your organization's information systems.  "Sun setting" features should be maintained to move electronic addresses out of these data buckets when the applicable exception or implied consent expires pursuant to CASL. 

Your organization's sun setting protocols should flag expiring implied consent scenarios in advance, where applicable, to trigger the sending of consent requests to convert an implied consent into an express consent before the implied consent expires.

Finally, the procedures your organization follows when sending CEMs should be coordinated to your organization's data buckets of recipient addresses and CASL compliance policy requirements. 

(f)        Establish policies and procedures to ensure CASL's content requirements will be followed

Your organization should establish policies and procedures to ensure CASL's CEM content requirements are complied with.  Your organization's CEM templates should be reviewed and updated to satisfy these requirements.

After July 1, 2004, CEMs will have to contain CASL's prescribed "unsubscribe mechanism" to effectively and promptly enable recipients to opt-out of receiving CEMs.  Your information technology systems and procedures will have to align to and facilitate this mechanism in a manner that satisfies CASL's requirements.  Your organization should ensure its unsubscribe mechanisms are effective and easy to use.

Your CEM content policies and procedures should account for the different content requirements that pertain to solicitations your organization makes for CASL consents.  In the case of consent solicitations your organization makes by way of electronic message, the CEM content requirements applicable to other forms of CEM will apply.  However, where CEM consent is solicited by CEM, a statement that withdrawal of consent may be made at any time is also required.

CASL's content requirements are not limited to consent solicitations that are made via electronic message.  Solicitations for CEM consent that are made on paper or orally will also be subject to content requirements.  Such paper forms should be reviewed to ensure they satisfy CASL's content requirements.  Where CASL consent will be solicited orally, telephone scripts may be useful.  Your organization should determine how it will discharge its onus to prove consent where consents are collected orally.

(g)        Establish appropriate inter-corporate contracts where consents are shared

CASL requires persons who share consents with respect to CEMs10 to ensure their counterparts comply with CASL.  Where your organization shares CEM consents with other organizations, such as affiliates, service providers or customer organizations, CASL-compliant information technology protocols and contractual protections will have to be established or revised. 

 (h)       Building a CASL-compliant corporate culture

Your organizations' personnel should receive CASL training and information to ensure they understand and facilitate your organization's CASL policies and procedures.  This training should include CASL consent collection procedures, CEM content requirements and related procedures for interacting with your organization's information technology systems.  Your organization's CASL procedures policy should of course be covered during this training.  CASL training should be carefully documented as it may prove to be a valuable part of a future due diligence defence against any charges of CASL contravention.  After training is completed, CASL refreshers and policy updates should be circulated to staff from time to time to ensure knowledge of CASL compliance requirements is retained and is up to date, and to help further instil CASL compliance as part of your organization's corporate culture. 


1 CASL section 52.

2 CASL section 33.

3 CASL, section 13.

4 CASL, section 1(2).

5 CASL, section 6(8).

6 CASL, section 10(9)(a).

7 The Personal Information Protection and Electronic Documents Act (Canada)

8 Electronic Commerce Protection Regulations (CRTC), section 4.

9 Reg. 81000-2-175 (SOR/DOR), section 3(a)(ii).

10 Reg. 81000-2-175 (SOR/DOR) section 5.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Events from this Firm
8 Nov 2016, Seminar, Ottawa, Canada

The prospect of an internal investigation raises many thorny issues. This presentation will canvass some of the potential triggering events, and discuss how to structure an investigation, retain forensic assistance and manage the inevitable ethical issues that will arise.

22 Nov 2016, Seminar, Ottawa, Canada

From the boardroom to the shop floor, effective organizations recognize the value of having a diverse workplace. This presentation will explore effective strategies to promote diversity, defeat bias and encourage a broader community outlook.

7 Dec 2016, Seminar, Ottawa, Canada

Staying local but going global presents its challenges. Gowling WLG lawyers offer an international roundtable on doing business in the U.K., France, Germany, China and Russia. This three-hour session will videoconference in lawyers from around the world to discuss business and intellectual property hurdles.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.