Your opposing counsel hasn't complained about your late discovery responses. You've been emailing back and forth about timing. You assume you're covered.
You're not.
The gap between what legal teams think protects them during discovery and what actually does creates real risk. These myths persist because informal communication feels sufficient, and courts sometimes show leniency. But relying on judicial grace instead of procedural compliance puts your objections in jeopardy.
Myth 1: Ongoing Communication About Delays Equals Consent
The Reality: Asking when late responses will arrive doesn't constitute agreement to extend deadlines.
In Dochee v. The Methodist Hospitals, Inc., defense counsel argued they'd been "in communication with Plaintiff during the course of discovery" and that opposing counsel "was aware that Defendants were working on responses." The court rejected this argument. Plaintiff's counsel made the distinction clear: requesting information about when responses would be provided "does not mean that she consented or acquiesced to an extension of any kind."
The court sided with the plaintiff, noting it viewed "Defendants' failure to move for an extension of time or timely provide responses and objections with disfavor." Defendants hadn't filed a motion and didn't "even explicitly ask Plaintiff" for an extension.
What protects you: A formal stipulation signed by opposing counsel, or a court order granting additional time. Email exchanges about status don't create enforceable extensions under Federal Rule of Civil Procedure 33(b)(4), which states that "[a]ny ground not stated in a timely objection is waived unless the court, for good cause, excuses the failure."
Myth 2: Volume and Complexity Excuse Procedural Non-Compliance
The Reality: Your workload doesn't suspend the rules.
Defense teams often argue they "responded to the best of their ability to the voluminous requests." Courts hear this regularly. It rarely matters.
The procedural framework exists precisely because discovery is burdensome. If volume justified delays, the rules would be meaningless. You have two compliant options when facing requests you can't answer on time: move for an extension before the deadline, or object to the requests as overly broad or unduly burdensome within the response period.
What you can't do is simply respond late and cite the difficulty of the task. The Dochee court's language is instructive: it viewed the failure "with disfavor" despite acknowledging the volume. Your resource constraints are a reason to seek relief, not an excuse to ignore deadlines.
Myth 3: Courts Will Strike Late Responses and Waive All Objections
The Reality: Sanctions vary, and eventual compliance matters.
Here's where teams swing to the opposite extreme. After learning that informal extensions don't work, they assume any late response means automatic waiver of all objections.
The Dochee court didn't strike the responses or deem objections waived because defendants had eventually responded. This leniency reflects judicial pragmatism: courts prefer to resolve disputes on the merits rather than through procedural defaults.
But don't mistake this outcome for permission. The court still criticized the delay and could have ruled differently. More importantly, you can't predict which judge will show leniency and which will enforce strict compliance. Responses in this case were "between six weeks to two months late." That's a significant delay that could have resulted in waiver.
The lesson isn't that late responses are acceptable. It's that the consequences are unpredictable, which makes compliance the only defensible strategy.
Myth 4: A Single Privilege Objection Eliminates the Need for a Log
The Reality: Layered objections don't automatically excuse privilege log requirements.
When you object to a request on multiple grounds (relevance and privilege, for example), you might assume the non-privilege objection means you don't need to log the documents. The Dochee court clarified this: "Defendant Methodist need not provide a privilege log for the requests where it objected on grounds besides just privilege, but does need to provide a privilege log for" requests where privilege was the sole or primary objection.
This distinction matters for your Records Freeze and Legal Hold processes. When you identify potentially responsive documents during a hold, you need to track which objections apply to each category. Documents withheld solely on privilege grounds require logging. Documents withheld on relevance or other grounds first may not.
The practical implication: your document review workflow must distinguish between objection types, not just apply blanket privilege claims. This requires coordination between legal teams and whoever manages your hold custodians and collection scope.
Myth 5: Informal Practice Among Counsel Creates Binding Precedent
The Reality: Professional courtesy isn't procedural compliance.
Many legal communities develop informal norms. Attorneys routinely grant each other short extensions without formal stipulations. This works until it doesn't.
The problem surfaces when relationships change (new counsel enters the case), stakes increase (a motion for sanctions gets filed), or one party decides to enforce the rules strictly. What felt like mutual understanding becomes "he said, she said" about whether an extension was granted.
Your email saying "we'll need another week" and opposing counsel's silence doesn't create an enforceable agreement. Neither does a phone call where the other side says "that's fine." Under most local rules and Federal Rule of Civil Procedure 29, stipulations extending discovery deadlines must be in writing and often require court approval.
What to Do Instead
Build these practices into your discovery response workflow:
File extension motions early. If you receive requests you can't answer within the deadline, move for an extension immediately. Don't wait to see how much progress you make. Courts grant reasonable requests filed before deadlines far more readily than they excuse late responses.
Document all agreements in writing. When opposing counsel agrees to an extension, send a confirming email that explicitly states the new deadline and asks for written confirmation. Better yet, file a stipulation with the court.
Separate your objection tracking. Maintain a matrix showing which objections apply to which requests. This prevents the privilege log confusion and helps you respond to motions to compel with precision.
Treat informal communication as advocacy, not agreement. Your emails updating opposing counsel on your progress serve a relationship-management function. They don't create legal rights. Don't rely on them for protection.
Train your team on the difference. Make sure everyone involved in discovery understands that being responsive and communicative is good practice, but it doesn't substitute for formal compliance.
The procedural rules around discovery deadlines exist to create certainty. When you rely on informal arrangements instead, you're choosing uncertainty. And in discovery disputes, uncertainty favors the party arguing for waiver.
