Does Your Ontario Monitoring Policy Explain AI Meeting Notes?
An Ontario electronic-monitoring policy review for AI meeting notes: employer coverage, required content, delivery deadlines, and a worked workplace example.
An Ontario employer has an electronic-monitoring policy that describes email security checks and building-access logs. Months later, project leads begin recording meetings and circulating AI summaries. The policy still describes the workplace as it existed before those tools arrived.
That is a useful point to reopen the policy. The review should establish what the employer actually monitors, how the meeting tools operate, and what the resulting information is used for. A paragraph about “company systems” may leave employees unable to understand that their spoken contributions are becoming searchable records.
Ontario’s Employment Standards Act, 2000, or ESA, contains a specific written-policy requirement. It is a disclosure framework, not a complete privacy code or an approval mechanism for recording. This article applies the framework to a fictional employer using AI meeting notes, based on official materials reviewed on November 1, 2026. The examples are suggested drafting and operating choices, not legal advice or a policy ready for adoption without review.
Establish whether the employer is covered
Start with Part XI.1 of the ESA. Section 41.1.1 generally requires an employer that employs at least 25 employees on January 1 to have a written electronic-monitoring policy in place for all employees before March 1 of that year. Ontario’s official interpretation manual explains the Ontario employee count and application of the rule.
The threshold concerns people, rather than full-time-equivalent positions or the number who use the AI tool. Part-time and casual employees count individually. Employees across the same employer’s Ontario locations are counted together. A later reduction in headcount does not remove that year’s obligation; growing past the threshold later in the year does not, by itself, trigger it for that year.
For example, our fictional consulting business employed 31 people in Ontario on January 1, 2026, split between two offices. Only eight project leads use AI notes. The policy obligation is assessed for the employer and applies to all its employees, even if particular monitoring practices apply only to some roles. Where the employer is covered, its policy must also address assignment employees working for it in Ontario, with special delivery rules discussed below.
Confirm that the Ontario ESA applies to the employment relationship and check relevant exclusions. Federally regulated employers need a different starting point. Ontario’s employer guide also explains that an existing compliant policy need not be rewritten every March 1 merely because another year has started. The practical reason to review this firm’s policy is the change in its activities.
Describe the monitoring that actually takes place
Electronic monitoring is broad enough to require examining what meeting software does, rather than relying on its label as a productivity aid. Ontario’s guide describes monitoring performed electronically and notes that it need not happen on employer-owned equipment or at the workplace. An employer should assess its actual meeting deployment, including personal devices and remote work where relevant.
In our example, project leads deliberately start capture for selected delivery meetings. The app records participants’ contributions and produces transcripts and draft summaries, which designated reviewers can read. That is the activity the policy review must confront. The fact that its stated purpose is project coordination does not make the collection invisible to employees.
The review should also ask whether another system extracts speaking time, attendance, sentiment or performance indicators; whether supervisors can search across meetings; and whether a recording continues after the main discussion ends. These are investigation questions, not allegations about a named product. A firm that does none of these things should not imply otherwise, but it needs evidence for its description.
Have the project lead and IT owner walk through an ordinary meeting together. Record when capture starts, what stops it, where the outputs appear and which roles can open them. Include the platform’s own recording or transcription features as well as third-party apps, since disabling one does not establish what another does.
Cover the statutory contents and add useful operational detail
Section 41.1.1 requires the policy to state whether the employer electronically monitors employees. If it does, the policy must describe how and in what circumstances monitoring occurs, and the purposes for which the employer may use the resulting information. It must also include the preparation date and dates of changes, together with any prescribed information.
For the consulting firm, a proposed meeting-notes section might describe the following. This table is an illustrative planning aid, not the complete policy or statutory wording.
| Subject | Proposed description for this fictional firm |
|---|---|
| Activity and circumstances | Designated project leads may start recording and transcription during scheduled delivery meetings after the required notice and recording checks; routine capture outside those meetings is not approved |
| Material captured | Microphone and meeting audio, transcripts, and draft summaries; the approved workflow excludes screenshots and screen video |
| Uses | Prepare and verify project decisions, task ownership and delivery commitments; the example excludes employee scoring and unrelated analysis across clients |
| Access and destinations | The assigned reviewer can access source material; approved project recipients receive the corrected decision record through the designated project folder |
| Working-record handling | Separate schedules govern source material and the approved record, with preservation exceptions reviewed by the records owner |
| Accountability | The policy identifies the responsible HR contact, its preparation date and the date of this change |
Access, retention and escalation detail can make the explanation more useful, but not every row above is a separate express ESA content requirement. The firm must also check whether its description is accurate. If managers actually use transcripts in performance reviews, a statement limiting use to project coordination would omit a real purpose.
The hypothetical exclusions are commitments the firm is considering, not controls that a notetaker necessarily enforces. Before promising that a feature cannot be used, IT must establish how the restriction will work. If settings remain under individual users’ control, the firm needs a workable way to manage that risk and describe the arrangement honestly.
Distribute the policy and keep the right records
Updating an internal page is only part of the task. Under section 41.1.1, an employer subject to the requirement must provide the policy to existing employees within 30 days of the date it is required to be in place, and provide changes within 30 days after they are made. A new employee must receive it within 30 days of becoming an employee or within 30 days of the date the employer must have the policy in place, whichever is later.
For an assignment employee, a covered client employer must provide a copy within 24 hours of the start of the assignment or within 30 days of the policy requirement date, whichever is later. These are statutory delivery periods; a separate legal or organisational requirement may call for notice before recording begins.
Ontario’s record-keeping guidance explains that required monitoring policies must be retained for three years after they cease to be in effect. That is a policy-retention rule. It does not require retaining every meeting recording for three years.
In the worked example, HR issues the revised policy through a channel employees can access, records which version was distributed and when, and adds it to onboarding and assignment-start procedures. A late invitation to a recorded client meeting still needs the applicable meeting notice; sending the employer policy weeks earlier is not assumed to settle recording permission for every future call.
Keep disclosure separate from permission and fairness
The interpretation manual makes an important limitation clear: section 41.1.1 does not establish a right not to be electronically monitored or create new employee privacy rights. The ESA provision also does not limit the employer’s use of monitoring information in the way a substantive privacy code might.
That does not mean other obligations disappear. Recording law, applicable privacy law, contracts, collective agreements, human-rights obligations and other employment rules need their own assessment. Nor should a policy acknowledgement be presented as consent that automatically satisfies each of those regimes. Summit’s Canadian privacy guide provides the broader jurisdictional starting point.
For our firm, the policy review uncovers a concrete problem: a project lead has started using AI summaries to assess a colleague’s reliability, even though the approved workflow concerns delivery decisions. HR pauses that use while the relevant obligations, accuracy risks and policy description are reviewed. This is a proposed response in the example, not a universal procedure dictated by Part XI.1.
The firm also establishes how someone can flag a mistaken attribution in a circulated record. A clear description of monitoring is valuable, but it does not make an incorrect summary reliable or justify a consequential decision based on it.
Explain local processing accurately
With Local Models selected and downloaded, Summit can transcribe and process meeting content on a Mac. Its security documentation explains the optional hosted-AI and sync paths, while exports and connected clients create additional destinations to review. The employer can use that information to describe its chosen configuration rather than repeating a general privacy slogan.
An employer-accessible local transcript can still be part of electronic monitoring. Local processing changes where content is handled; it does not decide whether Ontario’s policy requirement applies. Similarly, a local app does not supply the employer’s distribution records, retention governance or central enforcement of the policy.
The fictional firm’s next step is therefore a joint HR and IT review of the actual workflow, followed by an accurate policy revision and delivery process. Employees should be able to understand what their contributions become, who uses the resulting records and for what purposes, before the technology becomes an unnoticed part of everyday meetings.