Skip to main content

CVG Solutions

Hand holding a tablet with a cloud, padlock and data security icons above it

Received a subject access request? A practical workflow for a small business

November 12, 2026

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.

  • A request does not need to use any special wording or go to a particular person.
  • You normally have one month. You can extend by up to two further months only if the request is complex or you have had several requests from the same person, and you must say so within the first month.
  • In most cases you cannot charge a fee.
  • You must make a reasonable and proportionate search, not an endless one.
  • Most small business requests can be handled in-house with a simple process. Get help early if the request is linked to a dispute, involves a lot of information about other people, or you are thinking of withholding anything.

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:

  • Choose one person to own subject access requests, with a back-up for holidays and sickness. The ICO recommends a designated person and contact point.
  • Tell everyone who answers the phone, the shared inbox or social media accounts to pass any request for personal information to that person the same day.
  • If someone asks on another person’s behalf, such as a solicitor or a relative, check they have the authority to act for them before you release anything.

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:

  • the date it was received and how it arrived
  • who made it, and who it is about if that is a different person
  • exactly what they asked for, in their words
  • who is handling it
  • the response deadline, and any later change to it with the reason

You must respond without undue delay and at the latest within one month of receiving the request. The ICO explains how to count it:

  • Start from the day the request arrives, even if that is a weekend or bank holiday, and run to the same date in the following month.
  • If the following month has no matching date, use its last day. A request received on 31 January is due by 28 February (29 in a leap year).
  • If the deadline falls on a weekend or bank holiday, you have until the end of the next working day.
  • Some organisations use a fixed 28 days to keep things simple. The ICO says that is an option for day-to-day purposes.

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:

  • If you already know the person, for example a current member of staff writing from their usual email address or a regular customer, you are unlikely to need more proof.
  • Ask for ID only where it is necessary, and ask as soon as possible. You can use checks you already have in place, such as a customer account login.
  • Think about the harm a wrong disclosure could cause. More sensitive information can justify a closer check.
  • If you do need ID, the one-month clock starts when you receive it.

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:

  • Do not ask on a blanket basis. Only ask where it is reasonably needed, for example where the request is vague.
  • The clock pauses on the day you ask and starts again the day after you receive their answer. Your deadline moves back by the number of days it was paused.
  • Asking about something other than the information they want, such as the format of the response, does not stop the clock.
  • You cannot force someone to narrow their request. If they decline, carry out reasonable searches for everything they asked for.

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:

  • email accounts, including the deleted items folder, which the ICO says still counts because the emails are easy to retrieve
  • shared drives and cloud storage
  • your CRM, booking, accounting, payroll and HR systems
  • messaging apps such as Teams, WhatsApp or Slack used for work
  • paper files kept in a filing system
  • CCTV and call recordings, if you keep them
  • staff personal devices or accounts, where you have good reason to think work information about the person is held there
  • archives and backups, using the same effort you would use to find information there for your own purposes

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:

  • the type of information you would be disclosing
  • any duty of confidentiality you owe to the other person
  • any steps you have taken to ask for their consent
  • whether they are able to give consent

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

  • On paper, check that nothing can be read through the black marker, or copy the relevant parts into a separate document.
  • On screen, use a proper redaction tool or copy the relevant sections into a new document. Save the redacted version as a new file.
  • Before sending, search the redacted file for a name you removed to make sure it has really gone. Covering text with a black box in a word processor does not remove it.
  • CCTV usually needs blurring or blocking of other people. Your CCTV supplier may be able to help with this.

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:

  • why you use their information
  • the categories of personal information you hold
  • who you have shared it with or will share it with, including anyone outside the UK
  • how long you will keep it, or how you decide that
  • their rights to ask for it to be corrected, deleted or restricted, and to object
  • their right to complain to you and to the ICO
  • where you got the information, if not from them
  • whether you use automated decision-making, including profiling, and what that involves
  • the safeguards in place if you transfer their information outside the UK

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:

  • the original request and any clarification
  • a note of the identity check (not copies of ID)
  • your deadline calculation and any extension notice
  • your search log
  • your reasons for any redactions, exemptions or refusals
  • a copy of what you sent, and when and how you sent it

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”.

  1. Recognise and log. The practice manager logs it the same day and records a deadline of 10 April.
  2. Identity. The email comes from the personal address she used throughout her employment and refers to details only she would know. The manager decides no further ID is needed and notes why.
  3. Clarify. The practice holds four years of her emails, so on 11 March the manager asks whether she wants anything in particular. She replies on 13 March that she wants everything about her disciplinary meeting and her final pay. The clock was paused from 11 to 13 March, so the deadline moves to 13 April.
  4. Search. The manager searches the partners’ and her own mailboxes (including deleted items), the HR folder, the payroll system and the team chat, using her name, initials and staff number. The search log records each source and date.
  5. Review. The disciplinary notes include statements from two colleagues. One colleague agrees to their name being shared. The other does not, and the manager decides it would not be reasonable to disclose that colleague’s identity, so their name and identifying details are redacted. The redacted files are saved as new PDFs and checked.
  6. Respond. On 9 April the manager sends an encrypted file with the password by text message, plus a covering letter with the supplementary information, an explanation of the redactions, and her right to complain to the practice and to the ICO.
  7. Record. The log is completed and filed with the redaction reasons and a copy of the response.

When to get professional support

Many requests are straightforward. It is worth getting advice early when:

  • the request is linked to a grievance, dispute, tribunal claim or complaint
  • the information is spread across several systems or years of email
  • a lot of the material involves other people, such as witness statements or CCTV
  • you are thinking about extending the deadline, using an exemption or refusing the request
  • the deadline is close and the work is not done
  • you do not yet have a written process

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

  • Request passed to the person responsible on the day it arrived
  • Logged with date received, requester, what they asked for and handler
  • Deadline calculated (one month, adjusted for weekends and bank holidays)
  • Authority checked if someone is acting for another person
  • Identity checked only if needed, and the check recorded
  • Clarification asked only if reasonably needed, with pause dates recorded
  • Extension decided and notified within the first month, if used
  • All relevant systems searched, with a search log
  • Information reviewed: own data identified, other people’s data assessed
  • Redactions applied, saved as new files and checked
  • Any exemption decisions documented with reasons
  • Supplementary information included
  • Response sent securely in a suitable format
  • Reasons and complaint rights given for anything withheld
  • Log completed and records kept in line with your retention schedule

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.