Briefpoint

Other Similar Incidents Discovery: A Defense Guide

 In Practice Pointers

Other Similar Incidents Discovery: A Defense Guide

Legal content overseen by Nathan Walter, Esq., attorney licensed in California (State Bar No. 313299).

A manufacturer is served with a request for production seeking every complaint, incident report and investigation file for a product family.

Other similar incidents discovery in federal court starts with Federal Rule of Civil Procedure 26(b)(1): are the records relevant to a claim or defense, and is the demand proportional to the needs of the case?

Counsel then supports any disputed boundary with facts and produces the non-objectionable responsive material. Calling a record an “other similar incident” does not establish similarity, and trial admissibility is a separate question.

Other similar incidents discovery starts with Rule 26

Unless a court order limits it, Rule 26(b)(1) sets the scope of federal civil discovery: “Parties may obtain discovery regarding any nonprivileged matter that is relevant to any party’s claim or defense and proportional to the needs of the case.” Proportionality considers the importance of the issues at stake in the action, the amount in controversy, the parties’ relative access to relevant information, the parties’ resources, the importance of the discovery in resolving the issues, and whether the burden or expense of the proposed discovery outweighs its likely benefit.

Rule 34(a)(1) lets a party serve a request “within the scope of Rule 26(b)” for documents and electronically stored information (ESI) in the responding party’s “possession, custody, or control.”

Identify the claim or defense the records address

The complaint alleges a defect or failure mechanism. For each requested category of complaints, reports or investigations, identify the allegation or defense it bears on, if any. An allegation is not proof, and a request’s description of records as similar does not settle relevance.

Keep trial admissibility separate

Rule 26(b)(1) ends with this sentence: “Information within this scope of discovery need not be admissible in evidence to be discoverable.”

The Federal Rules of Evidence address the trial question. FRE 401 says evidence is relevant if “it has any tendency to make a fact more or less probable than it would be without the evidence” and “the fact is of consequence in determining the action.” FRE 403 says: “The court may exclude relevant evidence if its probative value is substantially outweighed by a danger of one or more of the following: unfair prejudice, confusing the issues, misleading the jury, undue delay, wasting time, or needlessly presenting cumulative evidence.”

Neither FRE 401 nor FRE 403 states a substantial-similarity test. This guide addresses discovery under Rules 26 and 34, not a case-law standard for admitting other incidents at trial.

Map each request to the product and alleged failure

A request-to-evidence matrix connects each demand to the facts that bear on scope. It is an internal aid for counsel, not a substitute for the response, the production or any privilege description. Briefpoint can assist with drafting and document citations, but the scope decisions belong to counsel.

Record the request as served

Capture the request number and text, any definitions that change scope (such as “incident” or “complaint”), the product scope, the date range and the categories requested. Request for production examples show how these demands are commonly phrased.

Rule 34(b)(1)(A) requires a request to “describe with reasonable particularity each item or category of items to be inspected.” Keep the request’s scope separate from any narrower scope counsel proposes, which remains a proposal until the parties agree or the court orders it.

Connect technical facts to proposed boundaries

Record the alleged failure mechanism, product family, component and revision, model years, use conditions, dates and geography, each with its supporting record and any open question. An unknown value stays unknown. A blank similarity field is not the same as coding a record “not similar,” and it is not a basis for exclusion.

Record the production decision

Record the custodians and repositories, the responsive subset, the objection and its factual support, whether anything is withheld, the production date and status, and document and page citations. These fields track Rule 34(b)(2)(B) and (C), quoted below.

Identify incident records and document the burden

Map repositories and custodians

Possible sources include customer complaint systems, warranty and service records, engineering investigations and claims files. These are examples, not required categories. For each, record the custodian, system, date coverage and whether the records are within the party’s possession, custody, or control.

One event can appear in several systems, so note duplicates. Guidance on how to organize discovery documents for production covers sorting what is collected.

Explain retrieval limits with facts

Document searchable fields, legacy systems, manual review steps and export options. Label any time or cost figure as an estimate and state its assumptions.

Ordinary collection expense falls under the Rule 26(b)(1) factor of “whether the burden or expense of the proposed discovery outweighs its likely benefit.” ESI has a more specific provision. Rule 26(b)(2)(B) says: “A party need not provide discovery of electronically stored information from sources that the party identifies as not reasonably accessible because of undue burden or cost.” On a motion to compel or for a protective order, the responding party “must show that the information is not reasonably accessible because of undue burden or cost,” and the court “may nonetheless order discovery from such sources if the requesting party shows good cause.”

A database with no entry for an event does not show the event never happened. Record the system’s known coverage limits.

State specific objections and produce the rest

For each item or category, Rule 34(b)(2)(B) requires the response either to state that inspection will be permitted as requested or to “state with specificity the grounds for objecting to the request, including the reasons.”

Explain the disputed portion and the reason

“Overbroad, burdensome and irrelevant” gives the other side nothing to evaluate. A specific objection ties its grounds to the request and the matrix: which definition sweeps too widely, which repository is hard to search and why, or which product versions the alleged mechanism does not involve. A sample response to a request for production shows typical formatting.

Say whether responsive material is withheld

Rule 34(b)(2)(C) provides: “An objection must state whether any responsive materials are being withheld on the basis of that objection. An objection to part of a request must specify the part and permit inspection of the rest.”

Withholding material on an objection differs from a search that found no responsive records, and the response should say which applies.

Describe what will be produced and when

If a party produces copies instead of permitting inspection, Rule 34(b)(2)(B) says the production “must then be completed no later than the time for inspection specified in the request or another reasonable time specified in the response.” For a partial objection, Rule 34(b)(2)(C) requires inspection of the rest; Rule 34(b)(2)(B) supplies the completion timing when copies are produced instead.

Use this checklist to prepare a partial response:

  • the disputed scope, identified by request language;
  • the specific grounds and reasons;
  • whether responsive material is withheld on that objection;
  • the scope produced without objection;
  • the completion date or other reasonable time; and
  • production references, when available.

Adapt these elements to each request. A boundary counsel describes is a proposal and does not amend the request.

Work through an automotive request-to-evidence example

The following scenario and records are invented to illustrate the workflow.

A complaint alleges that a seat-belt retractor failed to lock in a collision. Request 7 asks for all complaints, incident reports and investigation files involving the “restraint system” in any vehicle the company has made.

A different model with a shared component

Record OSI-014 is a warranty complaint about the Model Y, which uses retractor revision C, the same revision as the vehicle in the complaint. Whether OSI-014 involves the alleged mechanism is an open question.

The model name alone does not remove the record from review under Rule 26(b)(1). Counsel records the component evidence and the alleged failure, then makes the scope judgment.

The same model with an unresolved failure mechanism

Record OSI-022 is a service entry for the same model. It carries a broad code, “RESTRAINT – GENERAL,” and no narrative. The matrix marks the mechanism unknown and lists the next review step: locate the technician’s narrative and any linked engineering record.

The code neither shows nor excludes a retractor failure. The legal assessment stays with counsel.

A partly disputed demand with an available responsive subset

Counsel disagrees with part of Request 7: it reaches vehicles that never used the retractor family at issue, and older models sit in a legacy system with manual retrieval steps.

The response states the disputed part (records for vehicles with no retractor in that family), the reasons, and that responsive records about those vehicles are withheld on this objection. It also produces the incident records for models and revisions that use the family, FICTIONAL-000101 to FICTIONAL-000240. This illustrates Rule 34(b)(2)(C)’s requirements to identify the disputed part, state whether responsive material is withheld on the objection and permit inspection of the rest; it does not establish that the objection is valid.

The record IDs and Bates range are traceability aids, and Rule 34 requires no particular numbering system. Under Rule 34(b)(2)(E)(i), “[a] party must produce documents as they are kept in the usual course of business or must organize and label them to correspond to the categories in the request,” unless stipulated or ordered otherwise.

Resolve remaining scope issues and check the production

Discuss concrete scope proposals

The matrix lets counsel discuss repositories, technical definitions and any agreed staging with specifics.

Address confidentiality and privilege separately

Rule 26(c)(1) allows a party or person from whom discovery is sought to move for a protective order. The motion “must include a certification that the movant has in good faith conferred or attempted to confer,” and the court may act “for good cause.” Subsection (G) covers “requiring that a trade secret or other confidential research, development, or commercial information not be revealed or be revealed only in a specified way.”

Rule 26(b)(5)(A) governs how a party claims privilege or trial-preparation protection when withholding otherwise discoverable information. The party must “expressly make the claim” and “describe the nature of the documents, communications, or tangible things not produced or disclosed” so that other parties can assess the claim without revealing protected information. The rule does not itself establish that an incident investigation is privileged, and this guide prescribes no log format.

Reconcile the response, documents and later corrections

Before production, check each request’s stated exclusions, withholding position and document references against the documents selected for release. If a party objects to a requested ESI form or none was specified, Rule 34(b)(2)(D) requires it to “state the form or forms it intends to use.”

Rule 26(e)(1) imposes a conditional duty to supplement or correct a response “in a timely manner if the party learns that in some material respect the disclosure or response is incomplete or incorrect.” It applies if the information “has not otherwise been made known to the other parties during the discovery process or in writing,” or as the court orders. Briefpoint’s Supplemental Responses feature exists for that stage; the duty itself comes from Rule 26(e)(1).

Common mistakes include treating a blank similarity field as an exclusion, stating a burden figure with no documented basis, withholding responsive material without saying so, and citing Bates ranges that do not match the documents released.

Draft incident-record responses with Briefpoint

Discovery Playbooks can scope approved positions to a client, jurisdiction and case type. Before drafting, the approved objections and responses appear under each matching request. An attorney can select Use Objections, Use Response or Use and rewrite, which rewrites a prior response with the new case’s facts.

Autodoc finds responsive documents, adds page-level Bates citations and builds a Bates-numbered production package. Counsel reviews the scope decisions, factual assertions and output in Word and decides what is served. Similarity and proportionality remain legal judgments for counsel, and the request-to-evidence matrix above is counsel’s own workflow, not a product feature.

Governance implementation builds playbooks from a client’s litigation guidelines, approved positions or responses already served. For the broader workflow, see discovery drafting for defense teams.

Book a demo to see Briefpoint’s discovery drafting workflow.

See Briefpoint in this product video:

FAQs About Other Similar Incidents Discovery

Can discovery include incidents involving a different model or model year?

Potentially. A model label alone does not resolve relevance or proportionality under Rule 26(b)(1). Counsel looks at the alleged failure mechanism and at component and version information, such as whether the other model uses the same part. The rule text sets no model-year limit, and the answer turns on the facts.

How far back can a request for other incident reports reach?

The cited federal rules supply no universal lookback period. Scope depends on Rule 26(b)(1) relevance and proportionality, on the request’s description under Rule 34(b)(1)(A) and on any court order limiting discovery. A period that suits one product and claim does not carry over automatically, so no five-year default applies.

Does producing an incident report mean it is admissible at trial?

No. Under Rule 26(b)(1), information within the scope of discovery “need not be admissible in evidence to be discoverable.” Admissibility is decided under the evidence rules. FRE 401 asks whether evidence makes a fact of consequence more or less probable, and FRE 403 allows exclusion only when probative value is “substantially outweighed” by listed dangers.

Can a manufacturer withhold every record because part of an incident request is overbroad?

No. An objection to part of a request must “specify the part and permit inspection of the rest,” under Rule 34(b)(2)(C). The objection must also state whether responsive materials are being withheld on that basis, and Rule 34(b)(2)(B) requires the grounds to be stated with specificity, including the reasons.

What if an incident database has no field for the alleged failure?

Counsel documents the limitation and reviews what the system does hold, such as narratives and linked records. A missing field does not show that no responsive information exists. Under Rule 26(b)(2)(B), on a motion to compel or for a protective order, the responding party must show the ESI source is not reasonably accessible because of undue burden or cost; the court may nonetheless order discovery if the requesting party shows good cause.

The information provided on this website does not, and is not intended to, constitute legal advice; instead, all information, content, and materials available on this site are for general informational purposes only. Information on this website may not constitute the most up-to-date legal or other information. This website contains links to other third-party websites. Such links are only for the convenience of the reader, user or browser. Readers of this website should contact their attorney to obtain advice with respect to any particular legal matter. No reader, user, or browser of this site should act or refrain from acting on the basis of information on this site without first seeking legal advice from counsel in the relevant jurisdiction. Only your individual attorney can provide assurances that the information contained herein – and your interpretation of it – is applicable or appropriate to your particular situation. Use of, and access to, this website or any of the links or resources contained within the site do not create an attorney-client relationship between the reader, user, or browser and website authors, contributors, contributing law firms, or committee members and their respective employers.

Recent Posts

Leave a Comment