Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
None
Received a subject access request? A practical workflow for a small business
The short answer
When a subject access request (often called a DSAR) arrives, log it the same day and work out your deadline. Check who is asking only if you genuinely need to, search the places you hold their information, remove other people’s details where you need to, and send a clear, secure response within one calendar month. Write down each decision as you go.
This guide sets out a practical workflow a small business can follow from the moment a request arrives to the day you close it. It is based on current ICO guidance, including the changes made by the Data (Use and Access) Act 2025. If you are still not sure whether subject access applies to your business at all, start with our article Do private companies need to respond to a DSAR?.
Step 1: Recognise the request
A subject access request is simply someone asking for their own personal information. The ICO is clear that it does not have to mention “subject access”, “DSAR” or any law, and it can be made verbally, in writing or through social media. It can also be sent to anyone in your business, not just the owner or office manager.
So a customer’s Facebook message saying “send me everything you hold about me”, or a former employee asking on the phone for copies of their personnel file and emails, can both be valid requests.
What to put in place:
Step 2: Log it and set the deadline
Start a simple log entry as soon as the request is passed on. A spreadsheet is fine. Record:
You must respond without undue delay and at the latest within one month of receiving the request. The ICO explains how to count it:
You can extend the deadline by up to two further months if the request is complex or the person has made a number of requests. You must tell them about the extension, and why, within the first month. The ICO says a large volume of information does not make a request complex on its own.
In most cases you cannot charge a fee. A reasonable fee for administrative costs is only allowed if a request is manifestly unfounded or excessive, or if the person asks for further copies.
Step 3: Check identity, but only as much as you need to
You need to be satisfied that you know who is asking and that the information relates to them. The ICO expects these checks to be reasonable and proportionate:
You do not need to keep copies of ID documents. The ICO suggests recording what was provided, when it was checked and who checked it. That note is usually enough, and it means you are not holding more personal data than you need.
Step 4: Clarify only if you really need to
If a request is unclear, or you hold a large amount of information about the person, you can ask them to clarify what they want. This is often called stopping the clock, and the Data (Use and Access) Act 2025 has now put it into law. The ICO’s guidance sets limits:
While you wait, you can often send the supplementary information described in Step 7, so part of the request is answered on time.
Step 5: Find the information
The law now states that you must make a reasonable and proportionate search. That means making real efforts to find the information, but not searches that would be unreasonable or disproportionate given the circumstances of the request, the amount of information involved, how hard it is to find and the importance of the right of access. If you decide a search would go too far, you must be able to explain why.
For most small businesses, the places to check are:
Search using the person’s name, any nicknames or initials colleagues use, their email address and any customer or staff reference number. Keep a short search log of where you looked, the search terms, who searched and the date.
Once a request arrives, carry on with routine use of the information, but do not change or delete anything you would not otherwise have changed. Amending or deleting information to stop it being disclosed is a criminal offence.
Step 6: Review it and protect other people
The person is entitled to their own personal information, not to every document that mentions them. The ICO’s advice for small businesses is to think about whether information is actually about them, or only includes their name. An office-wide email that happens to list them may not need to be provided. A note about how they performed at a meeting would.
Information about other people
Much of what you find will also identify other people, such as colleagues, customers or witnesses. You do not have to disclose information that would identify someone else unless they have agreed or it is reasonable to disclose it without their agreement. When deciding what is reasonable, the ICO lists factors including:
Where you can, redact the other person’s details and release the rest, rather than withholding a whole document. In emails, the ICO says the requester’s own name and email address should be disclosed and other people’s names redacted where appropriate.
Redacting safely
Exemptions
Some information can be withheld under specific exemptions. Those most likely to come up for a small employer include confidential references, management forecasting or planning, records of your intentions in negotiations with the person, and legal professional privilege. The ICO is clear that exemptions must be applied case by case and that you must document your reasons. A settlement agreement or an ongoing grievance does not, on its own, allow you to refuse a request.
Step 7: Send a clear and secure response
Your response should include a copy of the person’s personal information and the supplementary information the law requires. Much of this matches your privacy notice, and you can include a link to it, but you still need to provide it. The ICO lists:
If they made the request electronically, provide the information in a commonly used electronic format unless they ask for something else. Explain any codes or abbreviations they will not understand.
Send it securely. Check the email or postal address before you send anything. For sensitive information, use a secure portal or an encrypted file with the password sent separately, or special delivery for paper copies.
If you are withholding anything, or refusing the request, you must tell the person why and explain their right to complain to you, to complain to the ICO and to seek to enforce their rights through the courts. Since 19 June 2026, every organisation must also have a process for handling data protection complaints, including acknowledging a complaint within 30 days.
Step 8: Keep a record
When the response has gone, complete the log so you can show how you handled the request. Keep:
Decide how long to keep these records in your retention schedule, and review what went well. Patterns often show where your filing or email habits make requests harder than they need to be.
Worked example (hypothetical)
This is an invented scenario to show how the steps fit together. It is not based on a CVG client.
A 12-person accountancy practice receives an email on 10 March from a former bookkeeper who left after a disagreement. She asks for “all emails and notes about me”.
When to get professional support
Many requests are straightforward. It is worth getting advice early when:
If you have a data protection officer, involve them from the start. Not sure whether you need one? Our guide Does your small business need a DPO? explains the tests.
CVG Solutions’ DSAR support service can assess the request and the right level of identity checks, advise how wide your search needs to be and what can and cannot be released, carry out the redaction and prepare a final summary for the requester. If you would rather build your own process, our GDPR consultancy can help you set one up.
DSAR action checklist
Need help with a subject access request?
If a request has just landed and you are not sure where to start, or the deadline is getting close, get in touch with CVG Solutions. We can talk through the request with you and agree the right level of support.
Sources
Sources checked on 12 November 2026.
Recent Post
Received a subject access request? A practical workflow for a small business
November 12, 2026Does Your Small Business Need a DPO, or Occasional Data Protection Support?
November 7, 2026Is Your Website at Risk? The Critical PHP Security Flaws Explained
October 30, 2026