Home / How a request moves
From the first email to a closed file
Seven stages, an indicative timetable for a standard one-month response, and the one question each stage must answer.
The day ranges below are a typical internal plan for a straightforward request with a one-month deadline. Complex requests move differently, and the legal timescale is set by the law and guidance, not by this outline.
-
1
Day 0–2
Recognise and log
Confirm the communication is a request for the person’s own information. Record the date of receipt, the channel, exactly what was asked for and any preferred format. Open a request log entry and record the response date confirmed by your DPO or adviser.
-
2
Day 1–5
Verify, proportionately
Decide whether you already know who the person is. Ask for identity information only where there is genuine doubt, and only what is reasonable. If you ask, confirm with your DPO or adviser and current ICO guidance how this affects the start of the time limit.
-
3
Day 1–7
Clarify if needed
Where you process a large amount of information about the person, you may ask them to specify what they want. Record the request for clarification and the reply; confirm with your DPO or adviser whether, and how, this affects timing.
-
4
Day 3–12
Plan and run searches
Write the search plan: systems, mailboxes, shared drives, paper files, chat tools, date ranges, search terms and who runs each search. Collect returns into one controlled location.
-
5
Day 10–24
Review and decide
Remove duplicates, read for relevance, flag third-party information and possible exemptions. Decision-maker rules on each flagged category; decisions are logged with reasons.
-
6
Day 22–28
Assemble and send
Apply approved redactions, index the disclosure, draft the covering letter with supplementary information, obtain sign-off and send securely in an agreed format.
-
7
After sending
Close the file
Record what was sent, when and how. Set a review date for follow-up questions. Delete working copies in line with the agreement.
Who does what
| Task | Your organisation | Just DSARs |
|---|---|---|
| Owning the request as controller | Yes | No |
| Keeping the log and timetable | Approves | Maintains |
| Running searches in systems | Runs or authorises | Plans and records |
| Reading and flagging material | Spot-checks | Does the bulk of the reading |
| Deciding exemptions and third-party balance | Decides, with adviser if needed | Records and applies |
| Signing and sending the response | Yes | Prepares |
When the timetable slips
It happens: a key colleague is on leave, a system export takes a week, the volume is four times the estimate. The useful response is early and honest. If an extension may be justified, take advice from your DPO or adviser promptly and check current ICO guidance on when and how the person must be told. If it is not justified, the remaining options are to add reviewers, narrow by agreement, or send what is ready with a clear explanation and a firm date for the rest — recognising that a late remainder is still late.
Our timetable has an internal checkpoint around day ten for exactly this reason: it is the last comfortable moment to change course. Sketch an internal checkpoint.