Seven Ways Discovery Responses Go Wrong (And Why Courts Don't Let Boilerplate Slide)

Responding to a demand for production of documents feels, on its surface, like one of the more mechanical tasks in civil litigation — gather the documents, state your objections, produce what you have. In practice, discovery responses are governed by a surprisingly detailed set of statutory requirements, and falling short of them can turn what should be routine document production into its own satellite dispute. A recent meet-and-confer letter in California litigation lays out a useful catalog of the most common ways discovery responses fail to comply with the Civil Discovery Act — and why courts treat these failures as more than just technicalities.

Verification Isn't Optional

Every response to a request for production that includes a statement of compliance (an agreement to produce documents) or a statement of inability to comply (a representation that a diligent search found nothing) has to be verified — signed under oath by the responding party, not merely by their attorney. This makes intuitive sense: an attorney can certify that a document was served, but only the client actually knows what documents exist, what search was performed, and whether anything was withheld.

The consequence of skipping this step is more serious than it might seem. California courts have held that an unverified discovery response is the legal equivalent of no response at all. That means a party who serves substantively thorough, well-organized responses but forgets the verification has, as a matter of law, served nothing — exposing them to a motion to compel as if they'd simply ignored the discovery request altogether.

"Boilerplate" Objections Aren't Really Objections

A recurring theme in discovery disputes is the wholesale, undifferentiated objection — the same paragraph copied and pasted across every single request in a set, regardless of what that particular request actually asks for. Courts have consistently rejected this practice. Objections have to be justified with particularity as to each individual request; a blanket recitation that doesn't engage with what a specific request seeks doesn't function as a real objection at all, because it fails to tell the requesting party (or the court) what's actually being withheld and why.

This matters even when the underlying concern behind the objection might be legitimate for some requests. An objection based on the timing of expert disclosures, for instance, might genuinely apply to requests touching on expert analysis — but reciting that same objection against every request in a set, including ones that plainly have nothing to do with expert timing, undermines the objection's credibility and can itself expose a party to sanctions for discovery misuse.

Definitional Objections Still Need to Be Tied to the Actual Request

A related pattern involves objecting that broad definitions used throughout a discovery request (terms like "relating to" or "concerning") make every request overbroad. Courts have made clear that this kind of objection needs to be justified request by request. A definition that might genuinely create burden when applied to a sweeping request for "all financial records" doesn't automatically create the same burden when applied to a narrow request for a single executed contract. Objecting identically to both, using the same boilerplate language, misses the point of what a particularity requirement is designed to accomplish.

There's also a structural rule worth knowing: even where part of a request is genuinely objectionable, the responding party still has to state compliance — or inability to comply — with the non-objectionable remainder. An objection to one aspect of a request doesn't excuse a party from responding to the rest of it.

A Privilege Objection Requires an Actual Privilege Log — Not a Promise of One Later

Asserting attorney-client privilege or work product protection isn't the end of the inquiry; the responding party has to provide enough factual information for the other side to actually evaluate the claim. In practice, that generally means a privilege log identifying each withheld document, its date, author, recipient, and the specific privilege being claimed.

A response that simply promises a privilege log will be provided "to the extent required" at some unspecified future point doesn't satisfy this obligation. The duty to substantiate a privilege claim arises when the privilege is asserted, not whenever the responding party gets around to it. And there's an internal-consistency issue worth watching for: if a response asserts privilege but also states that no responsive documents were found at all, those two statements can't both be true — there's nothing to withhold on privilege grounds if nothing exists in the first place.

A Statement of Inability to Comply Needs Real Specificity

When a party can't produce documents because a diligent search turned up nothing, the applicable statute requires more than a generic statement to that effect. The response needs to specify which of several statutory categories applies — did the document never exist? Was it destroyed? Lost? Is it in someone else's possession? — and, if a third party is believed to have it, that person or entity needs to be identified by name and address.

A generic, repeated statement that "a diligent search located nothing" — used identically across dozens of requests covering completely different categories of documents — doesn't give the requesting party the information the statute requires, and can raise legitimate questions about whether a genuinely category-specific search was performed at all.

Recycled Answers Across Different Requests Are a Red Flag

Related to the boilerplate-objection problem is a subtler issue: identical substantive answers used across requests that plainly call for different things. If several requests seek documents from meaningfully different subject areas — photographs from different time periods, contracts for different types of work — and each one gets answered with the exact same single sentence, that pattern understandably raises doubt about whether each request actually received individualized attention. It's a useful diagnostic for anyone reviewing responses on the other side of a case: identical language across dissimilar requests often signals a response that was drafted for efficiency rather than accuracy.

Objections Need to Fit the Type of Discovery Being Answered

Finally, some objections are simply mismatched to the discovery device being used. An objection that a request "calls for a legal conclusion" has real teeth against an interrogatory or a request for admission, both of which can require a party to characterize facts or take a position. It has essentially no application to a request for production, which asks only that a party produce documents matching a description — it doesn't require any legal characterization at all.

The Broader Lesson

Discovery responses are often treated as a formality, but the Civil Discovery Act imposes real, specific requirements at every stage: verification, individualized objections, substantiated privilege claims, and precise statements when nothing can be produced. Responses that lean on repetition and generic language — rather than request-specific analysis — don't just risk a motion to compel; they can expose a party to sanctions for discovery misuse, and they undercut the credibility of whatever genuine objections might exist among the boilerplate.

For anyone drafting or reviewing discovery responses, the practical lesson is the same one that runs through most of civil procedure: specificity protects you, and generic language — however efficient it feels in the moment — tends to create more problems than it solves.

This post discusses general principles of California civil discovery procedure for informational purposes and is not legal advice.