A Practical Checklist for Preparing a Data Access Complaint

When a reader wants to raise a concern about access to personal information, a clear and organised record can make the issue easier to explain. The aim is not to assume what happened, but to identify the request, the information sought, and the response that needs clarification.

Record the original request

Start by noting what information was requested and how the request was made. Keep a copy of the wording used, along with any reference details that appeared at the time. A precise record helps separate the original question from later follow-up messages.

Readers can check whether the request clearly identifies the relevant account or interaction without adding unnecessary personal information. They can also confirm that the wording explains whether they are seeking a copy of particular records, an explanation of how information was handled, or both.

Organise the supporting material

Create a simple list of the material connected with the complaint. This may include:

• the original request and any follow-up messages;
• replies or notices received in response;
• dates shown on correspondence, without assuming that a date proves an action occurred;
• the specific categories of information that remain unclear; and
• questions that still need a direct answer.

Readers should remove unrelated sensitive details before sharing a copy with another party. Keeping the original material unchanged, while preparing a separate redacted copy, can help preserve an accurate record.

Describe the issue neutrally

A useful complaint focuses on observable details rather than conclusions. For example, readers can state that a request was sent, identify the information sought, and explain which part of the response appears incomplete, unclear, or unrelated to the request. They can then ask for the matter to be reviewed and for the relevant records or explanation to be identified.

Avoid presenting assumptions about a person, organisation, system, or outcome as established facts. If the concern involves an export file, readers can compare the file with the categories they requested and list any apparent gaps as questions for clarification.

Check before submitting

Before sending a complaint, readers can review the text for accuracy, remove duplicate points, and confirm that contact details are current. They can keep a private copy of everything submitted and note any reference information provided in a reply. The complaint should remain focused on data access and should not include unrelated accusations or confidential information belonging to someone else.

For a focused starting point, readers can review the data access complaint and export-file guide and use its headings to structure their own checklist. The guide should be treated as a prompt for organising questions, not as confirmation of any particular event or result.