The Discovery Objections Series · Part 1 · Checklist · July 2026

Surviving “Irrelevant”

The relevance objection is won at the drafting stage, not the hearing. These are the moves — from the complaint you file to the reply brief you sign — that leave “irrelevant” and “fishing expedition” nothing to attach to.

The Part 1 overview explains why relevance is the objection insurers assert most and win least; the case study shows what happens when the moves below are skipped — a sophisticated policyholder that lost its discovery before serving a request. This page is the reach-for-it version: the sequence, none of the citations. Every reported loss on this objection traces to a handful of avoidable mistakes, and each is fixable at the drafting stage — none at the hearing.

Before you draft anything — the complaint

  1. Plead the pattern as a pattern. Allege the practice: the systematic retention of outcome-oriented experts, the frequency prong of the unfair-practices statute, this denial as the product of the scheme. Pattern discovery follows pattern pleading, not the reverse — the single highest-leverage sentence in the case.
  2. Plead the purpose. Say what the practice evidence will show — bias, bad faith, conflict — in terms that map onto the recognized factors. The complaint is where relevance is manufactured; the requests only harvest it.
  3. Already filed without it? Amend first. Before serving pattern discovery, not after it is denied.

Drafting the requests

  1. Key to the person, then the topic. All reports by this expert. All claims evaluated by this doctor for this insurer. All files handled by this adjuster. The same-professional key establishes the nexus on the face of the request and narrows scope in the same stroke.
  2. Where you cannot key to a person, name the similarity features. Same policy form, same coverage issue, same claim type, same state — written into the request’s own text, so the nexus argument is made before the objection arrives.
  3. Build the limits in. A defined temporal window, a geographic limit where state law drives the theory, a numerical cap or sampling offer where files (not data) are sought. Requests that carry their own limits convert the scope objections into surplusage.
  4. Stay inside the factor framework. Compensation, retention volume, outcome statistics, insurer–expert communications, selection and oversight policies — the established categories, granted again and again. A novel category needs its own justification.
  5. Run both tracks, and label them. Pattern discovery proves the practice; expert-specific discovery proves the conditions of this evaluation. Label each request’s track so the insurer cannot aim one track’s objection at the other.

Before the motion — and when the objection lands

  1. Assemble the reason-to-believe file. The anti-fishing showing has three parts, all from materials already in hand: the practice (name it), the predicates (the insurer’s own guidelines and positions, the visible defects in the report, the retention channel), and the mechanism (how the material confirms or refutes the practice).
  2. Document the meet-and-confer. Every offer to narrow, every refusal to engage. The record built here pays compounding dividends across every later part of the series.
  3. Force the codified frame. “Irrelevant” and “fishing expedition” are one objection in two costumes. Answer both: state the standard (doubts resolved for disclosure), connect each request to a pleaded issue and a factor, lay out the predicate. In California, lead with the abolition of the epithet; elsewhere, supply the specificity and nothing is left of it.
  4. Plead the asymmetry as a named factor. The rule text makes “the parties’ relative access to relevant information” part of the calculus. You have none of the evidence; the insurer has all of it. Say so, every time.
Get the implementing kit. The moves above are the framework. The working version — the case anchor behind each move, model complaint and request language, the predicate-showing template, and the objection-response scripts (including the full counter to the “statistics are meaningless” argument) — is the paid Implementing Kit on Expert Bias Report.

Free edition · The checklist

Surviving “Irrelevant”: The Relevance and Nexus Checklist

Every move in order, from the complaint you file to the reply brief you sign — plus the failure-mode audit to run against your own request set before you serve it.

Read the free checklist →

Paid edition · The kit

The Relevance and Nexus Implementing Kit

The checklist, armed: the case anchor for each move, model complaint and request language, the predicate-showing template, and the meet-and-confer and motion scripts — including the three-part answer to the argument that expert statistics are meaningless without first proving the other denials wrong.

Read the paid kit →

← Part 1 overview   The case study →   The bias-evaluation service →

Related

See the doctrine behind these moves in Irrelevant, Lacking Nexus, and the Fishing Epithet, the cost of skipping them in The Port That Lost Before It Asked, and the request-framing architecture for the pattern files in Framing an OICF Request That Survives.

Distilled from the project’s Part 1 doctrinal synthesis (wiki/doctrinal_analysis_and_synthesis/2026-07-17-discovery-objections-part1-relevance-nexus-fishing-synthesis.md) and its reading of Colonial Life, Greyhound, and Williams. The case anchor for each move, and the model language, are reserved for the subscriber Implementing Kit. Educational and informational only; not legal advice.

← Part 1: Case Study Part 1: Overview →