The UK DSAR deadline: one month, extensions and stopping the clock
General information, not legal advice. Check the ICO's guidance for your own circumstances. Last checked against ICO guidance on 16 November 2026.
The time limit for a subject access request (SAR or DSAR) is short, and finding documents often uses much of it. That leaves less time than expected for reading, redacting and building the response. This guide explains how the UK clock works, using the ICO's own wording and examples.
The basic rule: without undue delay, and within one month
The ICO says you must comply with a SAR without undue delay and at the latest within one month of receiving it (ICO: A guide to subject access).
The clock can start later than the day the request arrives. The ICO says the month runs from receipt of the request, or from receipt of any of these if you need them (ICO: How long do we have to comply?):
- information you asked for to confirm the requester's identity;
- information showing a third party is authorised to act for the requester; or
- a fee, in the limited cases where one can be charged.
The ICO also says you should ask for ID as soon as possible and only where it is necessary.
How to count the month
The ICO's method is to start from the actual date you receive the request and count to the same date in the following month (ICO: How do we calculate a month?). Its examples include:
- A request received on 1 January (a bank holiday) is due by the end of 1 February. You start from the date of receipt even if it is not a working day.
- If the due date falls on a weekend or public holiday, the deadline moves to the end of the next working day.
- If the same date does not exist in the next month, use the last day of that month. A request received on 31 January is due by 28 February (29 in a leap year).
Extending by up to two more months
The ICO says you can extend the time to respond by up to a further two months if the request is complex, or if you have received a number of requests from the same person (ICO: Can we extend the time for a response?). A number of requests can include other rights requests, such as erasure.
Three conditions matter in practice:
- You must tell the person within the first month, and explain why you are extending.
- The extension is counted as three months from the original start date. The ICO's example: a complex request received on 7 August is due by the end of 7 November.
- You must be able to show why the request is complex.
What counts as "complex"?
The ICO says this depends on your organisation and the request, and gives examples of factors that may add complexity, including technical difficulty retrieving archived information, applying an exemption to large volumes of particularly sensitive information, and needing specialist legal advice (unless you routinely take it) (ICO: When is a request complex?).
The same guidance says a request is not automatically complex because it involves a large amount of information, and not complex just because you rely on a processor. Outside help with redaction does not, by itself, buy more time.
Asking for clarification: "stopping the clock"
The ICO says you may ask the requester to clarify what they want if it is reasonably required, for example because the request is vague or you hold a lot of information about them. If you do, the time limit pauses on the day you ask and resumes the day after you receive the answer (ICO: Can we clarify the request?).
Limits the ICO sets out:
- Do not ask for clarification on a blanket basis.
- The clock only stops for clarification about the information requested, not about other matters such as format.
- You cannot force someone to narrow their request. If they repeat it, you need to carry out a reasonable search.
The ICO's worked example: a request received on 14 May is due on 14 June. If you ask for clarification on 15 May and get it on 18 May, the clock was stopped for four days, so the response is due by 18 June.
What this means for the redaction stage
The law does not set separate deadlines for searching, reviewing and redacting. All of it has to fit inside the same month (or the extended period). Some practical points that follow from the ICO's guidance:
- Log the date of receipt, any ID or authority requests, and any clarification dates so the deadline can be shown later.
- Decide early whether an extension is justified. The notice has to go out within the first month.
- Keep a record of your search. You must make a reasonable and proportionate search (ICO: How do we find and retrieve the relevant information?), and a record helps you show it.
- Leave room for review before release.
Where Fairleaf fits
Fairleaf Disclosure prepares the redacted disclosure pack, including a search record and an exemption log, so your team can spend its time on review and sign-off. You stay the controller, you set the deadline and you make every disclosure decision. See how outsourcing a DSAR works.
Frequently asked questions
Is the DSAR deadline 30 days?
No. The ICO describes it as one month, counted from the date of receipt to the same date in the next month. The number of days varies by month. Some organisations use 28 days internally to stay inside the limit.
Can we extend a DSAR because it involves a lot of emails?
Not on volume alone. The ICO says a large volume may add to complexity, but a request is not automatically complex because it involves a lot of information. You must be able to show why it is complex.
Does asking for clarification restart the month?
No. It pauses the clock from the day you ask, and it resumes the day after you receive the clarification. The days already used still count.