Recognise and log the request

A person can ask whether their personal information is being processed and request access to it and relevant supporting information. Staff should know how to recognise that request even when it is mixed with a complaint, employment dispute or customer-service issue.

Log the receipt date and route promptly. The ordinary response period is one month, subject to the rules on identity information, clarification and permitted extensions. Complex requests or multiple requests from the same person may justify up to two further months, but that is not an automatic allowance. Explain a justified extension within the applicable initial period.

Verify only what is necessary

Confirm identity when there are reasonable doubts, using proportionate methods. Asking an established customer to provide a passport for a routine request may collect more information than needed. On the other hand, sending an entire personnel file to an unverified new address can create an obvious disclosure risk.

Our suggested approach is to record the reason for any check, the minimum evidence needed and the secure route for receiving it. Where a representative acts for the person, establish the authority and scope. Avoid turning verification into a barrier designed to discourage the request.

Plan a reasonable and proportionate search

The ICO's current guidance requires reasonable and proportionate searches. Map likely locations: customer systems, shared drives, business messaging, email, HR platforms and relevant paper records. Identify custodians and useful search terms. Do not assume the central database contains everything or treat a broad request as automatically invalid.

Where genuine clarification is needed, ask focused questions and follow the applicable timing rules. A request to narrow scope should help locate the information, not pressure someone into abandoning their rights. Record the systems considered, searches performed and reasons for excluding a location so the response can be explained later.

Review the information, not just the documents

The right concerns personal information, not an unconditional entitlement to every document containing a name. Nevertheless, context may be needed to make the information understandable. Review the material carefully, including information about other people and any potentially applicable exemptions.

Redaction requires judgement. Removing every colleague's name automatically can be as unhelpful as disclosing every third-party detail. Where an exemption is relevant, apply it to the particular information and circumstances rather than treating a whole folder as exempt. Obtain specialist advice where privilege, complex employment issues or significant competing rights make the decision difficult.

Prepare a secure, intelligible response

The response should be usable by the person receiving it. Explain abbreviations or codes where necessary, organise the files sensibly and include the relevant supplementary information. A huge unindexed export may be technically convenient but difficult to understand.

Choose a delivery method appropriate to the sensitivity and volume. Test access without sharing the information with an unintended recipient, confirm the destination and explain any access expiry. If using a password or secure portal, consider how the person receives the credentials and what happens if they cannot use the chosen method.

Protect the working file

Limit access to the temporary review folder and keep redacted copies separate from originals. Before dispatch, have an appropriate second person check the recipient and the final files. That modest quality-control step can prevent the response itself from creating a new disclosure incident.

Close the request and improve the system

Keep a proportionate audit record of the request, decisions, searches, response and delivery. Do not retain unnecessary duplicate copies of sensitive material simply because it was assembled for a SAR. Review retention in the context of the request and the business’s wider obligations.

Afterwards, identify avoidable friction. Did staff use personal inboxes for business matters? Were old exports scattered across shared drives? Did a supplier make retrieval unexpectedly difficult? Those findings should inform access controls, retention and supplier selection. A well-run SAR process is not just a defensive legal exercise; it exposes whether the business can genuinely account for its information.

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.