Identify the request before looking for an exemption

Establish whether the person is seeking their own personal information, correction, deletion, an explanation of processing or ordinary business documents. A subject access request concerns personal data and related information; it is not the same as litigation disclosure or a general right to inspect every document. Several legal routes can operate at once without becoming interchangeable.

Log the request, preserve relevant records and route it to an appropriate decision-maker. Do not allow a commercial dispute to delay recognition of a privacy request. A litigation timetable does not automatically replace a data protection deadline. If clarification, identity checks or an extension are justified, apply the relevant rules and explain them rather than leaving the individual without a response.

Use an exemption only for the provisions it covers

The Data Protection Act 2018 contains specific exemptions and restrictions, many with detailed conditions. They do not generally make an organisation or entire database exempt from UK GDPR. Identify the provision that would otherwise apply, the exemption relied on and the information to which it relates. Some exemptions depend on likely prejudice; others have a different statutory test.

Our recommended review sheet has four fields: information affected, legal provision, factual reason and decision. “Commercially sensitive” or “confidential” alone is not an adequate analysis. Separate the issue of whether information must be disclosed from whether it may be retained or used. A justification for withholding a particular communication does not automatically justify keeping unrelated personal data indefinitely.

Distinguish legal advice from ordinary business discussion

Legal professional privilege can protect qualifying confidential legal-advice communications and qualifying litigation material. The tests are specific. Copying a lawyer into an ordinary management email does not automatically make it privileged, and calling a document “privileged” does not create the protection. Confidentiality is important but is not synonymous with privilege.

Seek a lawyer’s assessment where the distinction matters. Identify the purpose of the communication, the people involved and the circumstances in which it was created. A consultant’s commercial or compliance advice should not be assumed to carry legal advice privilege merely because it discusses legislation. Scottish rules and terminology concerning confidentiality of communications require appropriate attention rather than an unqualified English-law explanation.

Review mixed documents rather than rejecting whole files

A file can contain ordinary correspondence, personal data about several people and privileged communications. Review the relevant components. Consider whether non-exempt personal data can be supplied without revealing protected material, and use redaction where appropriate. Keep an unaltered controlled original and a record of what was removed; do not overwrite the evidence while preparing the response.

For third-party information, assess the applicable rules on disclosure and reasonableness rather than assuming every other person’s name must always be hidden. Context matters: identifying a routine business contact is different from revealing a confidential allegation about a colleague. Record the decision consistently, and check that redaction cannot be reversed through comments, document layers or copied text.

Do not confuse proceedings with a blanket refusal right

A person may make a subject access request because they are considering litigation. That motivation does not, by itself, remove the right. Equally, the right does not override genuinely applicable exemptions. A business should assess the request on its merits instead of adopting a rule that all requests from a dissatisfied customer or former employee are abusive.

Where a request is said to be manifestly unfounded or excessive, apply the current legal threshold and supporting guidance, with evidence. Inconvenience or a large volume is not a substitute for the test. Use reasonable search planning and documented scoping to manage the work. Difficult cases involving repeated requests, settlement discussions or an active court order warrant specialist advice.

Handle crime-related information with precision

An investigation can create legitimate concerns about prejudicing crime prevention or detection. The relevant exemption must still be examined against its conditions and the particular disclosure; it is not enough to write “fraud” on a file. Record why complying with the relevant requirement would create the specified prejudice, where that is the applicable test, and revisit the position when circumstances change.

A normal business investigating suspected fraud does not automatically become a competent authority processing under the separate DPA Part 3 law-enforcement regime. Nor should it import freedom-of-information exemptions into a UK GDPR response. Different statutes can use similar words for different tests. Establish which framework actually applies before relying on a familiar-looking guidance page.

Explain the outcome without giving away protected material

Respond to the parts of the request that can be fulfilled. Where rights are restricted, provide the explanation and complaint or judicial-remedy information required by the applicable rules, subject to any lawful restriction on the explanation itself. Avoid a formulaic refusal that tells the individual nothing about what has been considered.

Internally, retain enough reasoning to demonstrate the decision if challenged. Keep the detailed exemption assessment appropriately restricted, especially where it contains legal advice. A response should be checked by someone who understands both the request and the proposed withholding, rather than approved solely because a template looks familiar. Record the version sent and the secure delivery method.

Make this a controlled exception process

Set an escalation route for requests involving privilege, criminal allegations, regulatory restrictions or conflicting legal duties. Use a review log to identify inconsistent treatment across teams and to revisit temporary restrictions. Preserve records needed for a genuine dispute under a documented hold, but define who will review the hold and when normal retention rules resume.

This guide is a framework for organising decisions, not a determination that a particular file is exempt. Privilege can be lost or misunderstood, and litigation, professional duties and national procedural rules require qualified advice. The strongest approach is neither disclosure of everything nor refusal of everything: it is a defensible, item-specific decision with the unaffected parts handled properly.

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.