Guide
Subject access request to an employer: what to expect
Updated
An employer is the controller most likely to hold a decade of your information across a dozen systems, and to be in dispute with you. Both change the framing.
Question 1
Whose personal data are you asking for?
The right of access belongs to the data subject. Who is asking changes what the organisation may reasonably want before it starts.
Email me this result
We will send you these figures and a link back to them. One email, nothing else unless you tick the box.
Where the data actually is
The personnel file is the smallest part of it. There is also the HR system, payroll, the email archive, the messaging platform and recruitment records. Then occupational health, expense and travel systems, building access logs, and any performance or case management tool.
A request for everything is lawful and will reach all of it, eventually. One naming systems and a date range gets a faster answer. It also leaves far less room to reasonably require further information under Article 12A(5), which since 5 February 2026 pauses your deadline.
The two exemptions you will meet
Confidential references, under Schedule 2 paragraph 24 of the Data Protection Act 2018. If the point of the request is a reference, expect it to be withheld and aim at the decision record instead.
Legal professional privilege, where the employer has taken legal advice about you. That is a genuine exemption and it is applied properly far more often than not. What it does not cover is everything an employment lawyer has been copied into: privilege attaches to the advice, not to the recipient list.
Identity, and why it rarely bites here
Article 12(6) lets a controller ask for more information where it has reasonable doubts about your identity, and delay dealing with the request until identity is confirmed. Article 12A(2)(b) then restarts the month from the day it receives that information.
An employer holding your payroll record, contract and work email has little room for reasonable doubt about who you are. A former employee writing from a personal email address is different. Answer that question immediately rather than argue about whether it should be asked.
Keeping it separate from the dispute
A subject access request is not a disclosure exercise and it is not part of a grievance, even when the same facts are behind both. Running them together tends to produce a response that answers the grievance and treats the request as rhetoric.
It also matters for the deadline. A request buried in the fourth paragraph of a grievance letter can genuinely be missed. You would rather not argue about when the relevant time began.
A SAR for HR: how the request lands with the employer
In most employers a subject access request lands with HR, even when addressed to a data protection officer. The duty sits with the employer as controller, not HR as a team. A request in the wrong inbox invites the argument about when the month began, described above.
The systems listed above are the ones HR has to search. Name them and a date range, and HR can answer in full inside the month rather than come back to you.