The duty is already in force
The new complaints-handling requirements took effect on 19 June 2026. Organisations must provide a way for people to raise data protection complaints, acknowledge them within 30 days, investigate appropriately and communicate the outcome. This is no longer simply a future implementation project.
The 30-day acknowledgement period is not a universal deadline for completing every investigation. Nor is it permission to leave a complaint untouched until day thirty. The investigation, progress information and outcome must be handled without undue delay. A straightforward issue should not wait merely because an internal timetable allows longer.
Make the route easy to find
Put a clear contact route where people would reasonably look, including the privacy notice. An accessible email address or another workable method is more useful than a polished policy that leads to an unattended inbox. Consider people who cannot use a particular online form and ensure staff can pass on concerns received elsewhere.
A practical design test is to ask a colleague unfamiliar with the process to find the complaint route from the website homepage. Then send a test message and check where it lands. Record who monitors it, who covers absences and how a complaint received by sales, reception or a personal staff inbox reaches the responsible person.
Acknowledge the substance, not just the ticket
An acknowledgement should show that the business understands what has been raised. Identify the main concern, say who is looking into it and explain what information is needed. Do not require unnecessary identity documents simply because the word privacy appears; the level of verification should reflect what will be disclosed or changed.
Keep the initial record factual. Capture when the concern arrived, the issues raised, relevant systems and any immediate protective action. Separate what the complainant says from what has already been established. This prevents an early assumption becoming the accepted account before the records have been checked.
Run related duties alongside the complaint
A complaint may also reveal a personal data breach or contain a subject access request. Those issues have their own tests and timescales. The complaints acknowledgement period does not replace the breach-reporting assessment or extend a rights-request deadline.
Our recommended triage asks three questions: is someone requesting a right, is information currently at risk, and what evidence needs preserving? Allocate each workstream explicitly. For example, securing an incorrectly shared folder should not wait for the final complaint letter, while supplying requested personal information should not be lost inside a broader service dispute.
Explain the outcome in useful terms
After investigating, explain what was considered, what the business found and what it will do. If the evidence does not establish the allegation, say why without dismissing the person’s concern. Where something went wrong, distinguish an immediate correction from longer-term prevention.
The ICO's guidance supports clear outcomes and appropriate information about further complaint routes. Avoid saying an issue is closed simply because an internal ticket has been marked resolved. The person should be able to understand the decision and what options remain if they disagree.
Make ownership explicit
Assign a named owner and a deputy to each open complaint. A shared inbox can be an effective entry point, but it is not an accountable decision-maker. Someone must know what is outstanding and be able to explain the next step.
Use complaints as operational evidence
Keep a proportionate record of the complaint, investigation and outcome with controlled access. Complaints can themselves contain sensitive details, so a shared spreadsheet open to everyone may create a fresh problem. Set a retention approach that reflects the purpose and relevant obligations rather than keeping the entire file indefinitely by default.
Review recurring themes. Several complaints about unexpected marketing may point to a collection-form problem; repeated access concerns may indicate permissions are too broad. A small monthly review of patterns, owners and completed actions can be more valuable than a lengthy policy rewritten annually. The aim is a process that improves the underlying activity, not merely a compliant-looking response template.
Sources and further reading
Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.
This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.