Decisions that documents are “non-relevant” often disappear quietly from view. When those decisions are undocumented, they can become one of the most difficult aspects of a disclosure response to defend later.
A decision that a document is “non-relevant” to a disclosure is still a disclosure decision — and if it is not recorded, it is often the hardest part of a DSAR or FOI response to defend later. This matters to any team filtering large document sets before review, whether under Article 15 of the UK GDPR or the Freedom of Information Act 2000. Disclosed documents leave a trail. Excluded ones usually leave nothing.
In many disclosure processes, the most significant decisions are the least visible. Documents that are disclosed are reviewed, redacted, and delivered. Documents that are deemed non-relevant disappear quietly from view. This disappearance creates a false sense of safety.
Why is “non-relevant” a decision, not an absence of one?
A non-relevance determination sets the scope of what the data subject receives and shapes the narrative of compliance. Yet in many organisations, non-relevance is treated as an absence of decision rather than a decision in its own right. That is the silent risk.
Non-relevant determinations are often made early in the process, sometimes rapidly, and frequently without a consistent framework. Reviewers may rely on informal judgement, contextual knowledge, or pragmatic filtering to manage volume. In the moment, this feels necessary and proportionate. The problem arises later, when those decisions are questioned.
Where do undocumented exclusions come back to bite?
When a data subject challenges the completeness of a response, or when the ICO asks how relevance was assessed, organisations are often unable to point to a clear record. The ICO’s right of access guidance expects controllers to be able to explain the searches they made and how scope was determined. They may know that documents were reviewed and excluded in good faith, but without structured records, they cannot easily show how that conclusion was reached. This is the same failure mode explored in why most DSAR redaction processes fail under scrutiny.
Why is relevance rarely binary?
Documents may be partially relevant, contextually relevant, or relevant only in combination with other material. Without a system that allows reviewers to capture nuance, non-relevant decisions tend to collapse into a single, unexamined category.
There is also a tendency to conflate non-relevance with low risk. In practice, non-relevant documents can carry significant risk if their exclusion cannot be justified later. A document that was never disclosed is often more contentious than one that was disclosed with appropriate redaction. The absence of explanation invites suspicion, even where none is warranted.
Informal filtering mechanisms exacerbate this problem. Email inbox rules, folder-level exclusions, keyword searches, and spreadsheet notes may help teams manage workload, but they do not create a durable audit trail. When challenged, organisations are left explaining processes that no longer exist in a verifiable form.
How do you make exclusion decisions defensible?
Disclosure obligations do not require organisations to disclose everything, but they do require them to be able to explain how decisions were made. Non-relevance is not an escape from accountability; it is an accountability trigger under the accountability principle in Article 5(2) UK GDPR.
Organisations that manage this risk effectively treat non-relevant decisions explicitly. They record them, they associate them with documents, and they preserve the reasoning applied at the time. This does not slow down disclosure. On the contrary, it reduces downstream risk by preventing the need for retrospective justification.
Structured disclosure platforms that allow non-relevant decisions to be recorded alongside review activity change the nature of the exercise — it is a core part of Redaktr’s approach to defensibility. They transform non-relevance from an invisible filter into a documented judgement, making the disclosure process more resilient under challenge without requiring organisations to disclose more than they are obliged to.
Non-relevance is not the absence of a decision. It is a decision that deserves structure.
Frequently asked questions
Yes, if challenged. The ICO or a court can ask how the scope of the search was determined and why material was treated as out of scope. An organisation that cannot explain its exclusions is in a much weaker position than one that recorded the reasoning at the time.
Keyword searches are a legitimate triage tool, but the search terms used, the systems searched, and the rationale for both should be recorded. Relying on unrecorded keyword filtering leaves the organisation unable to demonstrate that its searches were reasonable and proportionate.
At minimum: the document identifier, who reviewed it, when, and a brief reason for the exclusion. The record should be created during the review, associated with the document, and preserved with the case — not reconstructed afterwards.