Employee Monitoring Notice Template for Remote Teams

An employee monitoring notice has one job before tracking starts: let a worker predict what the company will collect and what a manager may do with it. “We may monitor activity” does neither. It leaves the capture method, work boundary, viewers, and consequences to guesswork.

For a remote service team, those details matter twice. A screenshot can contain a client's work and a worker's personal information at the same time. The UK Information Commissioner's Office (ICO) says home monitoring carries a higher risk of capturing private and family life. The notice below is an operating draft for an agency or BPO owner to complete with HR and local counsel. It is not a jurisdiction-wide legal form or a substitute for deciding whether each method is necessary.

Set the boundaries before filling the notice

Write down the actual configuration, not every switch a vendor offers. If the team tracks time but does not capture screens, remove the screenshot clauses. If it captures screens, test the notice against the configured capture window and what a real viewer can open.

A notice cannot rescue an overbroad setup. The ICO's monitoring guidance calls for a clear purpose, a less intrusive option where one can achieve it, limited access, justified retention, and a way for workers to explain or challenge results. For UK employers, it also calls for a lawful basis and a risk assessment where required. Apply the rules of each worker's location with qualified local advice. Do not paste a UK legal basis into a notice for a team working elsewhere.

Employee monitoring notice template

Replace every bracketed field. Delete methods you do not use. Keep the final version available to workers before the stated start date, and update it when the practice changes. The UK Acas guidance recommends consulting employees and representatives before introducing monitoring and telling workers the arrangement and its reason.

[Company name] employee monitoring notice
Effective date: [date]
Applies to: [workers, teams, locations, and devices]
Owner and contact: [role and contact route]

Why we collect these records. We use [specific records] to [specific work decision]. We will not treat an activity score or one screenshot as a complete account of work. [Named role] reviews context and hears a worker's explanation before [specified consequential decision].

What we collect. During [defined work window or tracked tasks], [tool name] records [exact time, attendance, project, app or site, screenshot, or recording fields enabled]. Screenshots may contain visible client material or personal information on the captured screen. [Describe any blur, exclusions, pause control, and employee access as actually configured.] We do not use [methods specifically disabled, after configuration is checked].

When and where. Collection starts [trigger] and stops [trigger]. It applies to [company devices, personal devices, or both] and [approved work apps or screens]. [State breaks, off-hours, shared spaces, and personal-use boundaries.] The team will be told before any material change to the method or scope.

Who can see and share it. [Named roles] can view [specific record types] for [purpose]. [Role] can export [specific records]. [Explain any client, processor, or other recipient and why sharing is needed.] Access is limited to the people who need it for the stated task. A forwarded export has its own handling rules: [storage, recipient, and deletion procedure].

Protection and retention. [Name actual storage and transit protections, permission checks, link expiry, and blur behavior for the chosen tool.] Time records are kept for [period and reason]; screenshots for [period and reason]; recordings for [period and reason]. [Named role] handles scheduled deletion and any documented legal hold.

Questions and corrections. Workers can ask [contact] what a record means, request access or correction where applicable, and explain a missing or misleading record before it is used in [payroll, performance, or client review]. [State response route and deadline that your team can actually meet.] The applicable privacy notice and local rights information are at [link].

Do not leave the example's “we do not use” sentence in place until an administrator has checked the actual configuration. An acknowledgment can record delivery of the notice; it does not by itself establish a lawful basis or make disproportionate monitoring fair. The ICO explains why consent is difficult to rely on in many employment relationships and why monitoring must be assessed for its own purpose and effect.

Show what the protection words mean

“Encrypted and private” is too broad for a notice. State each layer and the record it protects. Cloudflare's R2 documentation says R2 encrypts stored objects and metadata with AES-256. That is encryption at rest for stored media. It also supports TLS for transfers, which protects data while it travels. Neither fact decides which manager is allowed to open a screenshot.

KordanoTime's December 1, 2026 first release carries time tracking and screenshot review into Early Access. Its default Kordano-managed screenshot and recording media is planned for Cloudflare R2. The inspected screenshot path requires a signed-in viewer with the view-screenshots permission, checks the viewer's organization and target visibility, and gives clear images a five-minute link. When a screenshot blur policy is enabled, an authorized viewer receives a blurred image through an authenticated endpoint. Those are distinct protections: stored-media encryption, encrypted transfer, permissioned access, short clear-image links, and viewing blur. Cloudflare warns that anyone holding a signed URL can use it until expiry, so a short link is a limit on exposure, not a second login.

Early Access is planned to include 500 screenshots per month for each team. The first release is an owner-confirmed launch commitment; working-product and deployment checks remain part of launch readiness. An employer must decide its capture policy, who may view records, how long each record type should be kept, and how it will explain monitoring to workers. Verify that the chosen tool and its actual configuration can enforce those decisions, including the retention policy, before putting them in the notice. The employee screenshot privacy tests give that inspection a practical sequence, while the workforce data control questions cover export and exit decisions.

Send the notice through a real review

Have an administrator configure the test workspace, an authorized manager try the allowed view, and an unrelated manager try the denied view with harmless sample material. Have a worker read the notice and describe when capture starts, what can appear in a screenshot, who sees it, and how to dispute an error. If the actual behavior and the explanation disagree, fix the configuration or the notice before rollout. For location-specific duties, use the employee monitoring legal guide as a question map and obtain local legal review.

A notice earns trust when the boundary a worker reads matches the one the software and managers enforce. Review KordanoTime's first-release approach alongside your own completed notice, then keep the judgment about purpose, access, and retention with your team.