When a Rights Request Looks Frivolous: How to Evaluate It Fairly
Section 15 bars Data Principals from registering false or frivolous complaints, but leaning on that provision too quickly is its own risk. Here is how to evaluate a request without prejudging it.
The legal basis for pushing back, and its limits
Section 15 sets out duties for Data Principals, including a requirement not to register a false or frivolous grievance or complaint. That gives a Data Fiduciary genuine legal footing to push back on requests made in bad faith, but the provision is narrow - it covers requests that are false or frivolous, not requests that are merely inconvenient, repetitive, or oddly worded.
The risk of leaning on this provision too eagerly is real. Dismissing a legitimate request as frivolous, even in good faith, can itself become the subject of a grievance escalation, and a pattern of quick dismissals will not look good if the Board ever reviews how your organization handles rights requests generally.
What actually distinguishes frivolous from merely unusual
A request that is repetitive because the underlying issue was never actually resolved the first time is not frivolous - it is evidence of a process failure on your side. A request that asks for something outside the scope of the Act entirely, or that is submitted using clearly fabricated identity details, is a stronger candidate for the frivolous label.
Look for objective signals rather than a gut reaction: does the request correspond to a real account or relationship, is it asking for something the Act actually provides, and has it already been fully answered in a prior cycle. If those checks come back clean, treat the request as genuine even if the tone or framing seems combative.
Documenting the evaluation either way
Whichever way you land, write down the reasoning. If you conclude a request is frivolous and decline to act on it, that written rationale is what protects the organization if the requester escalates through the grievance mechanism or to the Board. If you conclude it is genuine despite looking unusual, that documentation shows the evaluation was not skipped.
It is worth having a second reviewer sign off on any decision to label a request frivolous, precisely because the stakes of getting that call wrong run in both directions - unnecessary internal cost on one side, and unresolved obligations on the other.
Where to go next
The Checklist Generator can produce a structured evaluation checklist for exactly this kind of judgment call, and the Evidence Tracker keeps the resulting decision and its reasoning on file for later reference.