Separate the reasons for keeping information

An employee file serves several purposes, and they do not all have the same legal basis. Payroll administration, statutory reporting, emergency contact arrangements and disciplinary records need to be considered on their own terms. Avoid using a broad employee consent form as a substitute for this assessment.

The ICO recognises the imbalance in an employment relationship when considering whether consent is freely given. Identify the appropriate basis for each use and explain the handling of information to workers. A practical inventory can start with the systems already in use and the decisions each record supports, rather than a lengthy theoretical list of every possible document.

Health information requires particular care

Sickness and medical information may be special category data. Processing it needs both an Article 6 lawful basis and a relevant Article 9 condition, with additional requirements where applicable. The fact that an employer has a legitimate operational concern does not remove those conditions.

Distinguish what a line manager needs from what HR or an occupational health professional needs. A manager may need information about adjustments or availability without receiving a detailed medical history. Our recommendation is to separate health records from routine personnel material and test access permissions explicitly. Do not assume a folder labelled confidential is technically restricted.

Give access according to the task

The ICO expects appropriate security and access limited to authorised people acting within their responsibilities. That includes the ability to change or delete records, not merely read them. Records also need to remain usable and recoverable when systems fail.

For a small business, a sensible starting point is individual accounts, multi-factor authentication where available, restricted folders and a clear process for leavers. Review shared mailboxes and exported spreadsheets as well as the principal HR platform. If a manager changes departments, ask whether their old access is still justified. Access should follow the current role rather than accumulate over an employee’s career.

Do not invent one retention period for everything

Different records support different obligations and claims. There is no single UK GDPR period that makes every employment document safe to keep for the same number of years. Tax, employment and other requirements may affect particular categories; the organisation should identify the relevant rules rather than copy an unrelated retention schedule.

Our practical approach is to record the category, purpose, trigger for retention, period or criteria, and deletion owner. A recruitment application, payroll record and grievance investigation should not automatically share the same rule. Where a dispute or other justified reason requires preservation, document the exception and revisit it rather than silently suspending deletion for the entire workforce.

Include suppliers, managers and informal records

Outsourcing payroll or HR administration does not remove the employer’s responsibilities. Consider the supplier’s role, contract, security, access and any overseas transfers. Workers should be able to understand relevant sharing through the information provided to them.

Informal records deserve attention too. A note in a messaging app can contain personal information even when it is not in the official personnel file. Train managers to write factual, relevant notes and to use approved systems. Avoid unnecessary speculation, casual medical descriptions or circulating a whole file when a short operational update would achieve the purpose. This also makes later retrieval more manageable.

Make the process work when someone leaves

Departures are a useful control point. Close accounts, recover devices and decide who needs access to remaining business records. Do not simply delete every file immediately, or retain a former employee’s whole mailbox forever because it might contain something useful. Apply a documented, purpose-based approach.

Test the arrangement with a sample record: can the business locate it, explain why it exists, identify authorised users and apply the retention rule? If not, adding another privacy policy will not solve the underlying problem. The goal is a workable employment-record system that respects workers while allowing the employer to meet its genuine operational and legal needs.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.