# What Are Responsive Records? Scoping Explained | Kodex Source: https://www.kodexglobal.com/glossary/responsive-records > Responsive records are the data that genuinely falls within a request’s scope. Learn how scoping errors cause over-disclosure and non-compliance. Request Operations ## Responsive Records Responsive records are the documents and data that actually fall within the scope of a specific request. Determining what is responsive is a scoping judgement, and getting it wrong in either direction means either failing to comply or disclosing more of a user’s data than the law required. Also known as responsive data, responsive documents Scoping is the least glamorous step in request handling and the one where most avoidable harm occurs. The legal analysis is usually settled by the time you get here. What remains is a careful reading. ### What makes a record responsive A record is responsive when it falls within the request’s defined scope, which is normally bounded on several axes at once: - Identifier: the specific account, user, device, or address named - Time: the date range specified - Data type: subscriber information, transactional records, or content - Legal ceiling: what the instrument is actually capable of compelling That last axis is the one most often forgotten. A request may ask for content while attaching a subpoena. The content is within the request’s stated scope and outside the instrument’s authority, which means it is not responsive in any sense that matters. ### The two failure modes Under-productionOver-production What happened Responsive records withheld Non-responsive records disclosed Who is harmed The investigation The user Detected when Agency follows up, or in litigation Often never Consequence Non-compliance, possible contempt Unauthorised disclosure of user data The asymmetry in the “detected when” row is why over-production persists. Nobody complains. The agency received more than it asked for and has no reason to object; the user does not know. A programme that only corrects the errors somebody notices will drift steadily toward over-disclosure. ### How to scope well - Read the instrument before the cover letter. The instrument sets the ceiling. - Write the scope down explicitly before searching: identifiers, date range, data types. - Search to that scope, rather than searching broadly and filtering afterwards. Broad retrieval followed by filtering makes over-production a slip rather than a decision. - Resolve ambiguity in writing with the agency, and keep the reply. - Record what was produced and why. A production log is the only way to answer questions about a request months later. ### Why this matters beyond compliance Every unnecessary record disclosed is a user’s data that left the company without legal compulsion. Users cannot audit this. They generally do not know a request occurred, and where a non-disclosure order applies they are not permitted to. The discipline of tight scoping is one of the few protections that operates entirely on the user’s behalf, exercised by a company they will never discuss it with. FAQ ### Frequently asked questions Who decides what is responsive? The recipient does, reading the request’s scope against what it actually holds. The requesting agency defines the scope; the company determines which of its records fall inside it. That judgement sits with the company, which is also why it carries the consequences of getting it wrong. What if a request is ambiguous about scope? Ask the issuing agency to clarify in writing, and produce against the clarified scope. Resolving ambiguity by producing generously is the wrong default. It discloses user data that was never properly compelled, and the written clarification is also the record protecting the decision. Is it acceptable to produce more than was asked for? No. Over-production discloses data the requester had no authority to obtain and that the user did not have to surrender. It is not a neutral act of helpfulness; it is an unauthorised disclosure, even though the underlying request was legitimate. Glossary ### Related terms #### Redaction Redaction is the permanent removal of information from records before they are produced, typically to withhold data about third parties or material outside a request’s scope. Effective redaction removes the underlying data rather than obscuring it visually, and failures here are usually technical rather than editorial. #### Chain of Custody Chain of custody is the documented record of who handled a piece of evidence, when, and what they did with it, from collection through to presentation. An unbroken chain supports the claim that evidence is what it purports to be and has not been altered; gaps invite challenges to its admissibility. #### Court Order A court order is any directive issued by a judge that compels a party to act. In data request work the term usually refers to an order compelling disclosure of records, but it also covers non-disclosure orders and preservation directives, so the label alone does not tell you what an order requires. See how Kodex structures review and production. Learn more