Under UK GDPR an organisation has one month to respond to a subject access request. The month runs from the latest of three days: the day the request is received, the day any identity information the organisation asked for arrives, and the day any fee it was entitled to charge is paid. It can be paused while the organisation waits for a clarification it reasonably needs, and extended by two further months for a complex request. The calculator below applies those rules with the UK bank holidays.
Deadline calculator
Enter the date the request was received.
The calculator runs in your browser and sends nothing anywhere. It applies UK GDPR Articles 12 and 12A as the regulator's guidance counts them, with the GOV.UK bank holiday lists for 2025 to 2028. Check the result against your own facts; it is not legal advice.
Video guide. The same rules worked through with one example request, about ten minutes.
The rule
Article 12(3) of UK GDPR requires a response without undue delay and in any event before the end of the applicable time period. Since 5 February 2026 that period has been defined in Article 12A, which section 76 of the Data (Use and Access) Act 2025 inserted into UK GDPR. The applicable time period is one month beginning with the relevant time, and the relevant time is the latest of the three days above. The commencement regulations do not apply Article 12A to requests received before 5 February 2026.
The month is the limit. A response that is ready in two weeks should go in two weeks.
When a request counts as received
A request counts as received when it reaches any part of the organisation, by any channel, including a conversation or a social media message. The regulator's guidance says the person does not have to use the words subject access request or mention Article 15; it only needs to be clear that they are asking for their own personal information. Staff who might receive one need to recognise it and pass it on the same day, because the clock starts when it arrives.
Counting the month
Count from the day the request is received, whether or not it is a working day, to the same date in the following month. A request received on Tuesday 3 November 2026 is due by Thursday 3 December 2026.
Where the following month has no matching date, the deadline is the last day of that month. Where the deadline falls on a weekend or a bank holiday, it moves to the next working day. A request received on Sunday 31 January 2027 runs to Sunday 28 February 2027, so the response is due on Monday 1 March 2027.
Christmas shows both rules at once. A request received on Wednesday 25 November 2026 would be due on Friday 25 December. The next two days are a weekend and Monday 28 December is the Boxing Day bank holiday, so the response is due on Tuesday 29 December 2026.
| Received | Same date next month | Response due |
|---|---|---|
| Tuesday 3 November 2026 | Thursday 3 December 2026 | Thursday 3 December 2026 |
| Wednesday 25 November 2026 | Friday 25 December 2026 (bank holiday) | Tuesday 29 December 2026 |
| Sunday 31 January 2027 | No 31 February: Sunday 28 February 2027 | Monday 1 March 2027 |
Bank holidays differ between England and Wales, Scotland and Northern Ireland, so the calculator asks which apply. Because the length of a month varies, the regulator's guidance says a fixed 28-day period can help for operational purposes. A response sent within 28 days of the start is always inside the month.
Identity and fees
Where the organisation has reasonable doubts about who is asking, it can ask for information to confirm the requester's identity, and the month then starts on the day that information arrives. If the organisation had asked on 3 November and received the information on Tuesday 10 November 2026, the response would be due on Thursday 10 December 2026. The request for identity information should go out promptly and ask only for what is needed.
Most requests are free. A fee can be charged only where a request is manifestly unfounded or excessive, or for further copies of the same information, and the month then starts when the fee is paid.
Stopping the clock for clarification
Where the organisation reasonably needs more information to identify the information or processing activities a request relates to, it can ask the requester and stop the clock. Article 12A gives the example of an organisation that processes a large amount of information about the person. The regulator's guidance has allowed this pause since October 2020, and since 5 February 2026 it has been written into the law.
The pause runs from the day the organisation asks to the day it receives the answer, both days included, and the count resumes the next day. If the organisation had asked on Thursday 5 November 2026 and received the answer on Monday 9 November, five days are paused and the deadline moves from Thursday 3 December to Tuesday 8 December. The date for any extension notice moves by the same five days.
The regulator sets limits. Clarification should not be asked for as a matter of routine, and it is unlikely to be reasonable where the information can be found and provided quickly. The clock does not stop for questions about other things, such as the format of the response. A requester cannot be made to narrow a request, and if they decline, the organisation still carries out reasonable and proportionate searches and responds.
Extending by two months
Where a request is complex, or the person has made a number of requests, the organisation can extend the period by two further months. It has to tell the requester before the end of the first month and give its reasons. The regulator counts the extended deadline as three months from the start, so a request received on 3 November 2026 can be extended to Wednesday 3 February 2027, with the notice sent by Thursday 3 December 2026. The response letter template includes an extension letter.
Complexity depends on the organisation and the request. The regulator's examples include technical difficulty retrieving archived information, applying exemptions across large volumes of sensitive information, needing specialist work, and needing specialist legal advice. A large amount of information does not make a request complex by itself, and neither does relying on a processor. The organisation has to be able to show why the request was complex.
Planning the month
Working out the date is the easy part. The month has to hold three pieces of work: finding the information, reviewing it, and writing the response. For an employee's request, finding usually means an export from email, chat and shared files, which is the IT team's part. Reviewing means removing other people's personal data and applying any exemptions. In the regulator's research with organisations handling care records, redaction was the most time-consuming part of the job.
The useful dates are working dates. Request the export in the first few days, plan to finish the review with a week to spare, and have a second person check the response before it goes. A request logged on the day it arrives keeps those dates honest. For employee requests, the employee DSAR guide covers the review itself.
If the deadline is missed
A late response is a breach of Article 12, and the regulator acts on it. In October 2025 it issued an enforcement notice to South Wales Police after finding that only 29 per cent of its subject access requests between April 2023 and March 2024 had been answered within the statutory time limit. Since 19 June 2026 a person can also complain to the organisation itself, which has to acknowledge the complaint within 30 days and investigate it. The complaints procedure guide covers that duty.
The regulator has been the Information Commission since 30 September 2026. A complaint about a late response is answered from the organisation's own record: when the request arrived, when any clock stopped and why, when an extension was notified and why, and when the response went.
Frequently asked questions
How long do we have to respond to a subject access request?
The time limit is one month under UK GDPR, counted from the latest of three days: the day the request is received, the day any identity information the organisation asked for arrives, and the day any fee it was entitled to charge is paid. The period can be paused while the organisation waits for a clarification it reasonably needs, and extended by two further months for a complex request or a number of requests.
Is the time limit 30 days or one month?
It is one month, counted by date. A request received on 3 November is due on 3 December, which is 30 days later. A request received on 31 January is due on the last day of February, which is 28 days later in a normal year. Some teams use a fixed 28-day period as an internal target because it always falls inside the month.
Does the day the request arrives count?
Yes, the count starts on the day the request is received, whether or not that is a working day, and runs to the same date in the following month.
What if the deadline falls on a weekend or a bank holiday?
The deadline moves to the next working day. Bank holidays differ between England and Wales, Scotland and Northern Ireland, so the date can differ by nation.
When can we stop the clock?
The clock stops only while the organisation waits for a clarification it reasonably needs to identify the information or processing the request relates to, for example where it holds a large amount of information about the person. The pause runs from the day it asks to the day it receives the answer, and the count resumes the next day. The clock does not stop for other questions, such as the format of the response.
How do we extend the deadline?
Where the request is complex, or the person has made a number of requests, tell the requester before the end of the first month that the period is being extended by two further months, and give the reasons. The extended deadline is three months from the start.
How SafeRedact Fits
SafeRedact is browser-based redaction software for data subject access requests. Files never leave your browser: documents are processed client-side, only extracted text and the case's data subject details are sent for AI detection, and no documents are stored on servers. Detection text is never used for training and is deleted within 30 days. You name the data subject whose information should be preserved, and other individuals' personal information is flagged for redaction across every file in the case, including ZIP and Purview PST exports. Every detection is reviewed by a human before anything is exported, and the export package includes the redacted files, a processing summary, an audit trail and a review decision log. Supported formats: PST, PDF, DOCX, XLSX, EML, MSG, HTML, TXT, CSV, JSON, ZIP. A Data Processing Agreement is available and enterprise cases are priced per case, with the price set with you and shown before you download.
Make Every Redaction Decision Once
AI detection flags every identifier in the case. You decide whose it is, with the requester's data preserved and every decision recorded in the exported audit trail. Cases are priced per case, with a Data Processing Agreement available.
Set up your organisation