The Real Importance of the Rule 26(f) Conference
In litigation support team meetings, legal ops Slack channels, and prep calls before scheduling conferences, the Rule 26(f) conference often gets treated like paperwork, a box to check before the "real" discovery work begins. This mindset can lead to costly mistakes: missing custodians, stripped metadata, auto-deleted chat logs, and production formats that obscure the story you're trying to reconstruct.
Teams understand the conference matters, but they're often unsure what "doing it right" looks like when juggling multiple cases and dealing with opposing counsel eager to get off the phone.
Should We Push Back on a Quick 26(f) Call?
Yes, push back gently but firmly.
A ten-minute call might cover deadlines and expert disclosure dates, but it won't address the ESI issues crucial to proving your case. The conference must occur at least 21 days before the court's scheduling conference, and what you agree to becomes the foundation for the Rule 16(b) scheduling order, which can't be changed later without showing good cause.
Say this: "I need more time to walk through custodians, search methodology, and production format. Can we schedule an hour and exchange a draft protocol first?" You're not being difficult. You're preventing future issues, like discovering a key custodian wasn't preserved or a chat platform has been auto-deleting since the complaint was filed.
How to Propose Custodians Without Appearing Secretive
Start with a defensible hypothesis, not a negotiable floor.
Identify the three to five people who directly managed the transaction or decision at issue. Propose them as the initial custodians with a clear path to expand if the record shows gaps. Frame it this way: "We're starting with the project leads. If their documents reference others whose communications would fill in the story, we'll add them in the next round."
This isn't a concession. It's a statement about where you think the truth lies, inviting the other side to test that hypothesis. If they push for all thirty people in the department immediately, ask what they expect to find in the other twenty-seven that wouldn't surface in the leads' emails first. Often, they won't have a solid reason, they're just asking for volume.
Responding to Self-Collection Proposals
Don't lead with a threat. Lead with the problem.
Self-collection won't produce a reliable record. Employees may miss attachments, skip personal devices, and make inconsistent judgments about relevance. The result is gaps you'll both discover too late, usually right before a deposition.
Try this: "That approach won't work for you or for us. We need a collection method that captures metadata, preserves original file structures, and gives us confidence we're seeing the whole conversation. Let me walk you through a simpler process that'll cost you less and get us both better data."
You're solving their problem, not just objecting to their proposal. Most self-collection ideas come from clients who don't know there's a better way, not from lawyers trying to hide evidence.
Should We Fight for Native Files Over PDFs?
It depends on the case specifics.
If you're reconstructing a decision that went through multiple drafts, a pricing memo, a contract negotiation, an internal investigation, you need native files. Metadata shows who edited the document, when, and what changed between versions. PDFs erase that history.
But if the case turns on what a final contract said, or whether a notice was sent, PDFs may be adequate and cheaper to produce. Don't fight for native files just because it's standard practice. Fight for them when you can explain why the metadata matters to understanding what happened.
Frame it: "The key issue is how the pricing decision evolved between March and April. We need the native files to see who changed the numbers and when. PDFs would strip the edit history we need to reconstruct that timeline."
Can We Skip Reviewing Two Million Teams Messages?
Not quite, but propose a targeted approach.
Volume alone doesn't make a request overbroad. Importance does. If your sample covered the full time period and found minimal relevance, propose producing only the six-week negotiation window where activity concentrated. Offer to revisit the broader set if the initial production shows gaps or if specific search terms surface in depositions.
This is judgment, not gamesmanship. You're saying: "Based on what we've seen, this is where the story lives. If we're wrong, we'll expand." That's defensible. Refusing to produce anything because the total volume is large is not.
Understanding Clawback Agreements for Privileged Documents
Acknowledge reality, but don't get sloppy.
Every large production will eventually include a privileged document by mistake. A clawback procedure backed by a Federal Rule of Evidence 502(d) order doesn't excuse careless review. It builds in a remedy for the errors that will happen despite good-faith effort.
Propose it this way: "We'll both conduct thorough privilege reviews, and we'll agree that if a privileged document slips through, the producing party can claw it back within five business days of discovering the error. We'll ask the court to enter a 502(d) order so the disclosure doesn't waive privilege in other cases."
You're not lowering standards. You're being realistic about human error in high-volume review.
Evaluating Technology-Assisted Review Tool Effectiveness
Ask the harder question beyond recall percentages.
Eighty percent recall means one in five relevant documents won't be seen. What's likely in that missing fifth? If it's duplicative emails or routine status updates, the gap probably doesn't matter. If it's text messages or chat logs where people discussed key decisions, the gap could be critical.
Don't negotiate recall percentages as if they're abstract scores. Discuss what you're trying to understand and whether the search method gets you there. Sometimes that means sampling the null set to see what you're missing. Sometimes it means adjusting search terms after reviewing an initial batch.
The goal isn't hitting a number. It's reconstructing what happened well enough for a jury to understand.
Next Steps
The Rule 26(f) conference isn't governed by a checklist you can download. It requires judgment about your case specifics, exercised with opposing counsel trying to do the same. Read the rule itself, it's short. Then look at cases in your district where judges have granted or denied motions to compel based on what parties agreed to at the conference.
And next time someone suggests a ten-minute call, block out an hour instead.
