On 11 November 2026, the ICO published guidance on handling subject access requests drafted with AI. A subject access request is a request for access to someone’s own personal information. The ICO says to handle an AI-assisted request in the same way as any other under the existing UK GDPR rules. ICO guidance on AI-assisted requests
If you run a small business, imagine a long email arriving in your customer service inbox. It mixes a complaint about a missed appointment with a request for the notes and calls you hold about the sender. The employee reading it has to decide who should see it and what needs doing first.
I’d give them a short procedure they can follow while the customer is still waiting for an answer. Start with what the person is asking for, then give the colleague handling the request enough information to work out where to look.
Give the inbox team a clear handover
Train staff to recognise a request in everyday language. “Please send me the notes you have about my appointment” is the sort of sentence I would use in training. The ICO says a person can make a valid request without using legal terms or citing the right law. ICO guidance on recognising a valid request
I’d give staff a named contact and a deputy. Ask them to pass the original message and its receipt date to that contact through an approved route. If the email also contains a service complaint, agree who will follow it up and let the person know who is dealing with each part. Avoid forwarding the full message to everyone who might have a record.
Give the person handling the request a restricted place to log it and track the response date. The ICO says to respond as soon as possible and generally within one month. Its guidance explains how to calculate the deadline when, for example, you need proof of identity or authority. ICO guidance on response times
Work out where the information is likely to be
Read for the information the person wants. In the appointment example, I would ask the service team where it records booking changes and whether it keeps notes or recordings of calls. A search of the shared inbox may find the confirmation email while leaving the booking history untouched.
If the message asks for call records and you cannot tell whether the person means recordings or a log of calls, ask a specific question. Explain what your business actually holds so they can describe what they want. The ICO says you can ask for clarification where reasonably needed, and the requester can choose whether to narrow the request. ICO guidance on clarification and searches
Ask your IT provider or system administrator what each likely source can return. Give them the relevant identifiers and date range if established, and ask what their search will cover. I would record which systems and teams were checked and why, including any source you considered and left out. The ICO calls for a reasonable and proportionate search and recommends recording the reasons for its scope. ICO guidance on documenting searches
I would keep these checks with the case so the person preparing the reply can see the decisions already made.
Checks to record on the request
- Information requestedRecord what the person wants and any clarification you received.
- Scope of the searchRecord the locations covered and the reasons for including or excluding them.
- Correspondence detailsRecord how you checked where the response should go.
- Identity or authorityRecord any verification needed before releasing the information.
Check who will receive the reply
Look at the address supplied for the response, especially if it differs from the one you already hold. The ICO advises checking correspondence details and confirming them when there is doubt. If a representative is involved, establish their authority where needed before releasing anything. ICO guidance on contact details and authority
I would have the person handling the request review the proposed response and the delivery method together. A call recording or email thread may include information about other people. Ask whoever leads on data protection to review what can be shared before anyone sends the collected material. Keep working copies in the restricted case location and use your approved method for sending the response.
Walk through a request before one arrives
During November, put a dummy appointment request in front of the people who cover your shared inbox and ask them to show what they would do. Use fictional details and check that someone picks it up, knows who can search the booking system and can explain how they would verify a different reply address.
If the exercise stops at a system nobody knows how to search, ask its owner to demonstrate how they would retrieve the records. If it stops at a colleague who is on leave, put the deputy’s name where the inbox team can find it. The useful test is whether the people on duty can get from the original email to a checked response using the tools they already have.