Colour theme
Book a consultation

Reviewing the need for employee monitoring

Define the purpose, legal scope and data limits of employee monitoring before choosing a tool or treating activity measures as evidence of performance.

Colleagues discussing work around a table with laptops

A manager wants to understand why a project is late. A monitoring tool offers screenshots, application usage and an activity score. Before buying it, decide whether that information would answer the question, and whether you should collect it at all.

Keyboard activity doesn’t measure a completed task, a customer conversation or the quality of a decision. Start with the work problem and consider a less intrusive way to understand it.

State a specific purpose

Time recording for client billing, security-event logging and performance assessment are different purposes. Write down which one you’re proposing, what information it needs and who will use the result.

Ask whether project milestones, workload discussions or staff-entered timesheets would be enough. Avoid collecting screenshots or keystrokes because a product includes them by default. Those records may capture personal messages, customer information or confidential advice.

Ontario’s electronic monitoring policy guidance explains the ESA requirement for employers with 25 or more Ontario employees on January 1. The written policy must address whether monitoring occurs and, if it does, how, when and for what purposes.

The policy is a requirement. It doesn’t give you permission to monitor, and other laws still apply. An employer below the threshold still has limits.

The Privacy Commissioner’s workplace privacy guidance explains how privacy law reaches employees, which depends on the province and sector. PIPEDA covers employee information only at federally regulated employers, while Alberta, British Columbia and Quebec have their own private-sector laws that cover staff. Have an employment lawyer review the plan, including any collective agreement, before you start.

Limit collection and access

Define when collection starts and stops, including breaks and work on personal devices. Turn off features you don’t need for that purpose, and test that they’re off.

Name the people allowed to see individual records, the retention period and the process for correcting an inaccurate result. Review supplier access, exports and deletion as well as the manager’s dashboard.

Explain the arrangement to staff in plain language. A broad statement that company devices may be monitored leaves practical questions unanswered.

Review whether it helps

Run a small trial only after that review and after telling staff. Ask whether the information resolves the original problem, creates misleading conclusions or collects more than intended.

Keep people involved in consequential decisions and provide a way to challenge the evidence. Set a review date and an owner who can stop unnecessary collection. IT consulting can help check what the tool collects in practice, alongside the legal and workplace review.


Featured Image Credit