Can worker-monitoring records support a new data use?

Identify monitoring before naming a dataset

A vehicle route export, productivity log or desktop screenshot archive may have been collected to oversee people at work. Calling it operational data does not remove that history. Start by identifying the monitoring practice and the people affected, including private communications, customers or household members who may appear incidentally.

The ICO's worker-monitoring guidance connects fair monitoring with reasonable expectations, an explained purpose, accessible information, minimisation and retention. It warns that a blanket policy does not make excessive monitoring fair. The page currently carries a notice that guidance is under review following the Data (Use and Access) Act 2025. Use it as a bounded practical reference, with current UK legal review for the proposed reuse.

The business question is whether a specifically defined archive and purpose can progress to review. It is not whether every employment record can be sold once names are removed. A recipient's ability to recognize a route, shift or writing pattern belongs in the facts, alongside the original collection conditions.

Worked example: notices did not cover the same archive

In this hypothetical UK employer, facilities records contain equipment events, technician GPS points, productivity flags and occasional screen captures from a dispatch tool. A proposed recipient wants examples of delay resolution. The inventory owner initially groups all four as service histories. HR then finds that different collection systems used different notices and retention practices.

The completed matrix below records the actual gaps in this fictional review. It deliberately distinguishes a missing document from an adverse conclusion. A missing historical notice is not proof that collection was unlawful, but it is a reason to stop asserting that the proposed reuse is already supported.

Reconstruct what was actually collected

For the hypothetical GPS archive, a current notice is available but the oldest retained data predates that version. The reviewer records the period governed by each located notice, the device configuration changes and whether monitoring continued outside work. The current policy is not silently applied to every historical row.

For screen captures, the owner examines actual capture boundaries rather than a marketing description of the tool. The fictional inspection finds customer messages beside job status. Cropping a screenshot for one illustration does not establish that the full screenshot archive is suitable for the same use. The team excludes captures and builds a structured event description instead.

Keep a source-evidence register with system, collection setting, notice version, affected group, original purpose, retention rule and missing evidence. Make the evidence location available to the internal reviewer without forwarding personnel files to a prospective recipient. A metadata description can identify that a channel is held without disclosing the held material.

Compare the proposed use with workers' actual context

The hypothetical recipient explains that it wants to classify delay-resolution steps, not rank technicians. The employer asks why GPS detail and productivity flags are needed for that task. The recipient cannot give a task-specific reason. The redesigned proposal retains equipment event order and resolution categories while excluding person-level performance and location history.

That redesign reduces the proposal's scope; it does not establish a legal basis or eliminate identification risk. The privacy lead still reviews whether remaining job narratives reveal workers, whether the new purpose is supportable, and what information or other measures the affected people may need. HR checks that the operational description matches actual practice.

Retention needs a concrete explanation. In this hypothetical review, an unreviewed backlog was kept because someone might someday buy it. The owner stops treating that possibility as a retention decision and asks for the current business and legal basis for each period. Records whose retention position is unresolved stay outside the candidate package.

The ICO’s separate employment-records guidance recommends category-specific retention related to purpose and other obligations, rather than one period for every record. That page also warns it is under review. Keep this practical documentation approach distinct from a legal conclusion about the particular archive or new use.

Close the gap before making a representation

The hypothetical completed decision permits only an event-only proposal to progress to further rights and privacy review. GPS, individual productivity and screenshots are excluded. The source record identifies which historical notices remain missing and who will investigate. The employer does not promise that a future notice update resolves those historical gaps.

Use inventory to keep the four channels distinct and rights review to attach the unresolved origin and purpose questions. If the recipient changes its objective to workforce scoring, open a new review of that purpose; do not stretch the delay-resolution decision. A structured, useful event package may be preferable to an archive whose most sensitive fields add no demonstrated task value.

VOID can describe the narrowed opportunity through approved metadata for a named receiving program. Any referral compensation is conditional on that program's terms and is disclosed; there is no upfront seller referral fee. This introduction step does not authorize worker-record samples, a new processing purpose or a license.