AEVOMIND INSIGHTS — CUSTOMER SUPPORT & DATA
Subject access requests and data protection complaints: two legal clocks, and how software tracks them

A subject access request must be answered within one month, and the ICO says organisations must now give people a clear way to complain and acknowledge it within 30 days. Both arrive as ordinary emails and look like everything else until someone notices the date. Software does not decide what to disclose; it makes sure the request is recognised and the clock is tracked.
The short answer
Two legal clocks now run through the inbox of almost every organisation. A subject access request must be answered “without undue delay and at the latest within one month” of receipt. And the ICO’s announcement of 23 June 2026 says all organisations must now give people a clear way to make a data protection complaint and acknowledge it within 30 days. Neither clock cares how busy the office is.
Both arrive as ordinary emails, in ordinary inboxes, and look like everything else until someone notices the date. Software does not decide what to disclose. It makes sure the request is recognised, the clock is running from the right moment, and nobody finds out on day 29.

The two clocks, in the ICO’s own words
For subject access requests, the ICO’s guide to subject access sets out the rules that drive the administration:
- One month. The deadline is “without undue delay and at the latest within one month of receiving the request”.
- The clock can start later. If you need information confirming the person’s identity, evidence that a third party is authorised to act for them, or a fee, the timescale runs from when you receive it.
- Clarification pauses it. If you ask for clarification, the time limit “pauses on the day you request it and resumes the day after you receive it”.
- Up to two more months, with notice. You can extend “up to a further two months, where necessary” for a complex request or several from the same person, but you must tell the requester and explain why within one month of receiving the request.
- A reasonable and proportionate search. You “must make a reasonable and proportionate search”, and in most cases you cannot charge a fee.
The ICO’s June 2026 announcement adds a second clock. “All organisations must now give people a clear way to raise a data protection complaint”, and must acknowledge it within 30 days, investigate appropriately and communicate the outcome. The announcement does not define “appropriately” or set a deadline for the investigation, so we do not invent one. These are separate duties with separate clocks: one month for a request, 30 days for acknowledging a complaint.
It is a growing workload
The regulator’s own figures show where this is heading. The ICO received 33,753 data protection complaints in 2022/23 and 42,315 in 2024/25, an increase of 25.4%, and its January 2026 impact assessment says complaints about the right of access “account for the majority of the ICO’s data protection complaints work”.
Read that carefully. These are complaints that reached the regulator, not requests made to organisations, and the document gives no exact share for access complaints, so we give none. What it shows is that people are using their rights, and that the largest category of complaint is about the right of access, in other words about how organisations handled someone’s request for their own information. Every organisation holding personal data should expect to receive such requests.

Where the clock goes wrong
The deadline is simple to state and easy to lose track of, because it does not start and stop at obvious moments. This list is our own reasoning about how it slips, not data:
- The request is not recognised. It arrives in a general inbox, or with a member of staff who does not know it is a subject access request, and sits there while the one month runs.
- Identity is checked, but nobody records when the answer came, so nobody can say when the clock actually started.
- A clarification is asked for and the pause is never logged. The ICO says the limit pauses on the day you ask and resumes the day after you receive the answer, so both dates matter.
- An extension is needed but the notice is missed. You must tell the requester, with reasons, within the first month.
- A complaint reaches an inbox nobody monitors, and the 30-day acknowledgement is missed. In our reading, that is the same failure as a request that is not recognised.
The admin, measured
Take an illustrative organisation handling about four subject access requests and two complaints a month.
Illustrative inputs, not client data. Totals: 38 hours a month by hand against 17.5 with a system. Reviewing and redacting barely falls, on purpose: a person still has to judge what to disclose. A system removes the tracking and searching drag, not the judgement. Substitute hours you have measured.
Show the data
| By hand | With a system | |
|---|---|---|
| Logging requests and checking identity | 4.0 hrs | 1.0 hrs |
| Searching across systems and inboxes | 14.0 hrs | 6.0 hrs |
| Reviewing and redacting before disclosure | 12.0 hrs | 8.0 hrs |
| Tracking the deadlines and chasing | 4.0 hrs | 1.0 hrs |
| Replying and recording what was done | 4.0 hrs | 1.5 hrs |
That is 38 hours a month by hand against 17.5 with a system: about 20 hours back a month, or around 246 hours across a year, roughly a month and a half of one person at 162.5 hours, using the ONS median full-time week of 37.5 paid hours. Look at the third row, because it is the honest one. Reviewing and redacting barely falls, and it should not: a person has to judge what to disclose. The saving is in the tracking and the searching. The method is the one in how many hours automation can save.

What software can do here — and what it can’t
It cannot decide what is reasonable and proportionate to search for, or what to disclose or withhold. Those decisions stay with a person. AevoMind’s customer support desk is built around a shared inbox where every message becomes a tracked ticket with its history attached, and SLA rules with automatic escalation. That is the right shape for a deadline you cannot miss:
- Recognise the request. A message tagged as a subject access request or a complaint becomes a ticket with its own clock, instead of one more email.
- Start and pause the clock at the right events: receipt, identity confirmed, clarification asked, clarification received.
- Escalate before the deadline, not on it, so a request that is stuck reaches your data protection lead while there is still time to act.
- Prompt the extension notice inside the first month, when more time is genuinely needed.
- Keep the record: who did what and when, in an audit trail you can show if the response is ever questioned.
The same shared-inbox discipline is behind AI email management, and the wider data-protection duties are covered in the UK rules on AI for businesses. For the sectors that hold the most personal data, see schools, colleges and charities.

Where to start this week
- Find out where requests would actually arrive. Every inbox, form and phone number a person might use to ask for their information or to complain.
- Check you have a clear way to complain, and that the 30-day acknowledgement is a step someone owns.
- Take your last request and see whether you can say exactly when the clock started, whether it was ever paused, and when you answered.
- Check who decides what to disclose and who covers when they are away.
- Time one request honestly, including the searching, before deciding whether a system earns its place.
The test is simple: could you say right now which open request has the nearest deadline, and what it is, without searching anyone’s inbox? This is general information, not legal advice; the ICO’s guidance is the authority for any individual request.
Frequently asked questions
How long do you have to respond to a subject access request?
The ICO says without undue delay and at the latest within one month of receiving the request. The clock can start later if you are waiting for information confirming the requester's identity, evidence that a third party is authorised to act for them, or a fee. You can extend by up to a further two months where necessary, if the request is complex or you have had a number of requests from the same person, but you must tell the requester and explain why within one month of receiving the request.
Can you pause the clock on a subject access request?
Yes, in one defined case. If you ask the requester for clarification, the ICO says the one-month time limit pauses on the day you request it and resumes the day after you receive it. Separately, the clock can start later where you need information to confirm identity or authority. The ICO's guide does not say whether the clock pauses while a fee is outstanding, so we do not claim that it does.
What is the new data protection complaints requirement?
The ICO says all organisations must now give people a clear way to raise a data protection complaint, and must acknowledge it within 30 days, investigate appropriately and communicate the outcome. The ICO's announcement is dated 23 June 2026. It does not define what appropriate investigation means or set a deadline for the investigation, so the sensible reading is that the 30-day acknowledgement is the only fixed clock it names.
Can you charge for a subject access request?
In most cases, no. The ICO says you cannot usually charge a fee to comply. A reasonable fee based on administrative costs may be charged if the request is manifestly unfounded or excessive, or if the person asks for further copies of their information. You must still respond within the time limit, and the ICO says the clock can start when you receive a fee you have requested.
Can software handle subject access requests?
It can handle the tracking, not the judgement. A system can turn each request into a ticket, mark it as a subject access request, start and pause the clock at the right events, warn well before the deadline and keep a record of every step. It cannot decide what is reasonable and proportionate to search for, or what should be disclosed or withheld. Those decisions stay with a person, usually your data protection lead.