Skip to content
Artwork for Meet and Confer with Kelly Twigger

Meet and Confer with Kelly Twigger

Kelly Twigger

Meet and Confer is the podcast for litigators, eDiscovery professionals, and anyone who knows that in a world of electronically stored information, discovery strategy isn’t optional—it’s essential. Hosted by attorney and discovery strategist Kelly Twigger, each episode offers clear, practical discussions on how to effectively leverage the power of ESI to craft successful discovery strategies for any type of litigation. Topics include, navigating evolving rules, understanding emerging case law, and making the strategic decisions that shape the outcome of a case. Whether you're a seasoned litigator, brand new associate, in-house counsel, or law student, Meet and Confer helps you think critically, stay prepared, and master your discovery strategy for modern litigation.

Play
  • 26 episodes
  • Avg 34 min
  • English
Counted on this page — what you have heard stays on this device, so it is not something the list can be paged by.
  • Yesterday · 29 min

    How One Court Created an AI Chat Discovery Checklist

    AI chats can be discoverable and still feel impossible to obtain. That’s the tension driving our latest Case of the Week breakdown of Fontainebleau Florida Hotel LLC v. Boteach, where a defamation damages fight turns on intent and the plaintiff goes after AI prompts and outputs tied to social media statements. The headline is not just “AI discovery is allowed” but how the court builds a step by step path to get records from AI providers when ordinary subpoenas hit a wall. We walk through the orders that changed everything: the moment provider requirements entered the record. Once counsel learned the platforms maintain deletion logs but require account holder consent to release them, the court moved from refusing to compel consent to ordering a tightly limited authorization and, after noncompliance, an expanded consent covering all AI account data and content. The details matter: no edits to court required language, full account identifiers, notarization, submission from the email address tied to the account, and even a separate xAI privacy portal step. This is the practical checklist most lawyers wish they had before they brief an AI chat discovery dispute. We also connect the story to core eDiscovery rules and risks: Rule 34 possession, custody, or control for user exports; Rule 26 proportionality and duplication concerns; privilege logs under Rule 26(b)(5)(A); and fee shifting under Rule 37 when deadlines are ignored. If you work with ESI, subpoenas, preservation notices, or generative AI governance, you’ll leave with a clearer playbook for AI chat discovery that stands up in court. If this was useful, subscribe so you don’t miss the next update, share it with a colleague who is drafting AI discovery requests right now, and leave a review to help more litigators find the show. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • November 4 · 33 min

    When AI Prompts Show Intent for Punitive Damages

    Someone used generative AI to help write hostile social media posts during a lawsuit and the other side wants every prompt, draft, revision, and even the deleted chats. So what happens when AI prompt history becomes evidence, and how do we apply the discovery rules without inventing new “AI law”? We walk through Fontainebleau Florida Hotel, LLC v. Bo Touch from the Southern District of Florida, where the court treats AI conversations as ordinary ESI and asks the only questions that really matter under Rule 26: is it relevant to a claim, defense, or element of damages, and is it proportional? Because the case is in damages-only discovery and punitive damages are in play, the court ties discoverability to specific intent to harm under Florida punitive damages statutes and to reprehensibility factors discussed in State Farm v. Campbell. That legal framework is what makes certain AI prompts and outputs discoverable, not the novelty of the tool. Then we get practical about protection and process. Work product under Rule 26(b)(3) is not automatic, and it is not waived just because AI is involved either. The analysis turns on purpose, and it has to be proven chat by chat with a real privilege log under Rule 26(b)(5). We also unpack the court’s refusal to force a party to sign blanket consents for AI providers, the move toward Rule 45 subpoenas, and why the Stored Communications Act may become the biggest obstacle to obtaining AI chat content from providers in civil litigation. If you are advising clients who use ChatGPT-style tools at work, this is your roadmap for drafting targeted discovery requests, setting AI legal holds, handling deletion risk and Rule 37(e) spoliation exposure, and negotiating a production protocol that does not “unring the bell.” Subscribe for more case-driven eDiscovery guidance, share this with a colleague, and leave a review with your biggest question about AI prompts in discovery. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • October 21 · 28 min

    The Discovery Timing Trap

    You can do everything “right” on relevance and still lose the evidence that proves your case. That’s the uncomfortable lesson from FTC v. Uber Technologies, where the court looks at a massive transaction-level data request, calls it “a doozy,” agrees it’s relevant, and then denies it because of timing, burden, and the realities of the final weeks of fact discovery. We walk through the Uber One allegations and why the plaintiffs wanted granular structured data, including ride and Uber Eats fields, discounts, and a data dictionary, to compare members and non-members using a difference in differences analysis. Then we slow down and trace the discovery timeline: early pricing requests that get narrowed, late-arriving productions, new facts revealed through interrogatory answers, and a joint letter brief filed with about six weeks left. If you litigate in fast-moving dockets where discovery disputes are decided on short letter briefs, this story will feel painfully familiar. From there, we turn the ruling into an eDiscovery playbook you can use right away: put a dated timeline directly where the judge decides the issue, treat burden as a fact you must prove (not a vibe), and make late requests realistically grantable through sampling and phased discovery. We also dig into the leverage you can get from Rule 30(b)(6) testimony about how databases are built and what it actually takes to pull a random sample, especially when proportionality under Rule 26(b)(1) depends on what can be done before the cutoff. If you’re facing a motion to compel, structured data production, or a shrinking discovery schedule, this one will sharpen your strategy. Subscribe, share this with your team, and leave a review with the discovery fight you want us to break down next. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • October 15 · 32 min

    When Your Client’s ChatGPT History Proves Intent for Sanctions

    Your clients are already using AI to fact-check you, test defenses, and workshop their next move and they’re doing it on their phones with a timestamp. That means generative AI chat history is no longer a novelty in e-discovery. It’s ESI that can show intent, knowledge, and credibility, and a judge may end up reading it line by line. We break down Conlin Tire Company v Gonzalez, a non-solicitation dispute where the entire case turns on whether an agreement was signed and returned by email. During a forensic examination, the defendant’s ChatGPT prompts about deleted Yahoo emails become a key piece of circumstantial evidence. The court ties those prompts to the timeline, shifting explanations, and access delays, ultimately finding intent to deprive under Rule 37(e) and moving toward an adverse inference instruction. From there, we follow the arc: targeted replacement discovery, fights over what can be restored or replaced, and how incomplete compliance can make missing evidence truly irreplaceable. Then we connect the sanctions record to real-world litigation outcomes, including how the adverse inference supports a preliminary injunction. Along the way, we translate the decision into practical steps for preservation letters, forensic collection protocols, and client intake scripts so you’re ready for AI evidence in employment, trade secret, and contract cases. If you found this useful, subscribe, share the episode with a colleague, and leave a review. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • September 23 · 31 min

    Why Signal Is the Most Dangerous Source of ESI You Need to Understand

    Disappearing messages feel like a convenience until a court treats them as spoliation. We walk through the Delaware Court of Chancery’s May 27, 2026 ruling from the N-Ray World Wrestling Entertainment merger litigation, where key executives used Signal and repeatedly shortened auto-delete windows after receiving explicit litigation holds. The decision is a masterclass in how timing drives everything: when the duty to preserve arises, when a legal hold is issued, and how retention changes lined up with deal milestones in a way the court found impossible to ignore. We unpack the Rule 37E framework step by step: duty to preserve, loss of ESI, reasonable steps, and prejudice. Then we get practical about the technology. Signal is not natively ephemeral, it becomes ephemeral only when users affirmatively turn on disappearing messages. That single detail changes the preservation story, the credibility analysis, and the risk profile for anyone advising clients who communicate on personal phones outside company IT control. We also explain why even excellent forensic work may prove when settings changed without being able to recover what the messages said once they are gone. The biggest strategic insight is forum-specific. Delaware’s Court of Chancery Rule 37E expressly allows serious remedies on a showing of recklessness, while federal Rule 37(e)(2) typically requires intent to deprive. We compare how federal courts build intent through circumstantial patterns, drawing on Skanska, FTC v. Noland, and Hunter’s Capital, and we translate that into real guidance for your next preservation fight. If you care about eDiscovery, legal holds, mobile device preservation, and spoliation sanctions, this is a must-listen. Subscribe, share this with a colleague who writes holds, and leave a review with the app or platform that gives you the most preservation anxiety. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • September 9 · 18 min

    When The AI Product Becomes The Evidence

    The evidence you need from an AI company might not be emails, chats, or a handful of prompt screenshots. It might be the machinery behind the product: the retrieval index, the operational database, and the logs that capture every interaction at scale. That shift changes what you ask for, how you scope it, and how you argue proportionality when the data volumes get huge. We walk through Encyclopedia Britannica and Merriam-Webster v Perplexity AI, a Southern District of New York decision that reads like a plain English guide to retrieval augmented generation (RAG). We explain how an “answer machine” pulls content from a RAG database, hands it to a large language model, and generates outputs that can allegedly reproduce or paraphrase copyrighted works. We also break down Perplexity’s user activity log and why it can be the clearest record of what a user asked, what the system retrieved and ranked, what instructions went to the model, and what answer came back. From there, we translate the holding into a practical discovery playbook: why copyright registration dates can define the right time window for technical discovery in a retrieval time case, how courts apply Rule 26 relevance and proportionality to limit massive productions, and how cost shifting can hinge on whether your cost numbers stay consistent and well supported. If you litigate, manage eDiscovery, or advise clients using AI tools, you’ll leave with sharper vocabulary and better requests. Subscribe, share the episode with a colleague, and leave a review if these case driven takeaways help you. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • August 26 · 44 min

    When Gen AI Outputs are the Evidence

    Your case doesn’t have “documents.” It has a database full of everything a system ever generated and no sane way to collect or review it all. That’s the discovery problem generative AI is creating, and it’s why the Disney v Midjourney orders are worth reading line by line if you draft ESI protocols, negotiate protective orders, or litigate proportionality fights around prompt logs and AI outputs. We break down a statistical sampling protocol built for prompts and outputs at massive scale, including why the parties land on 385 records per character bucket, what that margin of error really means, and where sampling can mislead you when the thing you’re measuring is rare or when damages depend on counts. We also dig into the practical drafting choices that make this workable: defining the population up front with character buckets, spelling out deduplication rules that preserve repeated prompts and multi-franchise overlap, and naming the exact metadata fields that tell the real story (from job IDs and parent job IDs to publication and moderation flags). The core takeaway is verifiability. Instead of asking the other side to “trust the sample,” the protocol uses a reproducible SHA-256 hashing method, requires a signed certification that the process was followed, and adds a verification list that discloses every eligible prompt ID and its hash so the other side can rerun the draw and confirm the denominator. We compare that approach to the OpenAI output log fights and explain why a smaller audited sample can be more valuable than a huge uncheckable production. Subscribe to Meet and Confer, share this with someone drafting a discovery protocol right now, and leave a review if you want more breakdowns of real court-approved language you can adapt. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • August 14 · 31 min

    Why Agreeing on Short Message Context Is Critical

    One disconnected Microsoft Teams message can look like evidence, but without the surrounding thread you can miss valuable context that can lead to additional evidence. We walk through Valcrum LLC v Dexter Axle Company LLC, a trademark and trade dress dispute that turns into a focused battle over Teams chat discovery, missing context, and what courts will actually order when keyword search fails on short form messaging. We trace the timeline from early requests through rolling productions where Teams content shows up as standalone messages, then a later production suddenly arrives with organized threads that reveal what everyone has been missing. From there, we unpack the procedural pressure points that can decide a motion before the judge ever reaches the merits: meet and confer certification requirements, building a real paper trail, and why a separate Rule 30(b)(6) motion gets denied for lack of good-faith conferral. On the substance, we dig into the court’s practical compromise. The judge refused to force a full reconstruction of all Teams chats into threads, leaning on proportionality and Sedona Principle 6, but still rejected the idea that keyword searches alone are “good enough” for Teams. The result is a context window of three days before and after disputed messages, plus an order requiring unredacted production of threads when objections are vague and unsupported. If you litigate ESI, negotiate an ESI protocol, or collect Teams and Slack data, you’ll leave with concrete language and strategy to use right away. Subscribe, share this with your litigation team, and leave a review with your biggest Teams discovery question. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • August 7 · 43 min

    You Can't Compel What You Didn't Negotiate: The Importance of AI Language in an ESI Protocol

    A party can run generative AI to decide what gets produced, and you still might not be able to “see inside” the process after the fact. That’s the gut punch and the practical lesson from Schulte v LinkedIn Corp. (N.D. Cal.), where plaintiffs tried to compel detailed transparency about LinkedIn’s Relativity AIR document review, including metrics like illusion estimates, document error rate, and how many humans validated the AI’s calls. We unpack why the court says no and how the interim ESI order does most of the work. The order was negotiated in January 2023, before generative AI review became a standard litigation flashpoint, and it only requires disclosure of technology assisted review. The court folds generative AI review into that TAR disclosure clause, treats the requested metrics as discovery on discovery, and applies a familiar rule: you do not get discovery about the other side’s search and review methods without a specific, non-speculative showing that the production itself is deficient. From there, we walk through the rest of the rulings that make this order so usable in day-to-day e-discovery strategy: keyword search term pre-culling before AI review, the proportionality math when you’re staring at multiple terabytes across custodians, the high bar for adding an in-house lawyer as a new custodian, and why text messages stay off the table when your ESI protocol carves them out absent good cause. The throughline is simple and sharp: what you can negotiate into an ESI protocol is far broader than what a judge will order on a motion to compel months later. If you’re drafting or revisiting an ESI protocol, this is your roadmap for generative AI, TAR, search terms, and messaging data. Subscribe to the Meet and Confer podcast, share the episode with a colleague negotiating a protocol, and leave a review with the one AI disclosure clause you would fight hardest for. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • July 15 · 41 min

    The First Stipulated ESI Protocol For Generative AI Review

    A new line just got crossed in e-discovery: a federal stipulated ESI protocol treats generative AI document review as its own governed process, and it requires disclosures many lawyers have spent years trying to protect. We walk through James v Cerebras Systems, where the parties agree to an AI-specific review appendix that demands documented workflows, human-confirmed privilege calls, audit trails, and prompt disclosure with rapid redline updates. We unpack how the protocol is built and why that structure matters: search terms, TAR, and “AI responsiveness review” each get their own rulebook, plus explicit controls for layering methods that can silently compound missed responsive documents. Then we dig into the details that will change meet and confer conversations, including 95% confidence level sampling with a plus or minus 2% margin of error, reporting of recall and precision, an “illusion” rate trigger, and required quality checks for hallucination, oversummarization, and misclassification. The bottom line is clear: AI doesn’t reduce counsel’s Rule 26G duty, it raises the bar for defensibility. We also connect the ESI protocol to the companion protective order, where AI use on protected material turns on contract terms in a data processing agreement, not hype about a brand name. We explain what it really means when an order references enterprise ChatGPT or Harvey, why consumer accounts typically fail the “no training” requirement, and how these rules can create new incentives to over-designate confidentiality. Subscribe to Meet and Confer for more case-driven discovery strategy, and if you found this useful, share the episode with a colleague and leave a review with your biggest takeaway. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • June 24 · 23 min

    Your Protective Order Wasn't Written for ChatGPT

    A Texas judge just gave litigators something they’ve been asking for and something they’ve been dreading: a clear ruling that litigation-related ChatGPT conversations can qualify as work product, paired with a warning flare about protective orders that never anticipated generative AI. We walk through Tate Group Automotive v Legacy Automotive Capital from the Business Court of Texas and explain why the analysis isn’t really about what the AI “did,” but who used the tool, in what role, and for what litigation purpose. We connect Tate to the growing body of AI discovery case law, including the federal decisions that treat AI as a tool rather than an automatic waiver event under Federal Rule 26(b)(3), and the outlier authority that opponents cite when they want to argue waiver. Then we show what changes when you’re in Texas, where Rule 192.5 protects work product prepared “by or for a party.” That single word expands protection and helps explain why Tate comes out the way it does, even though the user is a represented party acting on their own. The most practical part of the ruling isn’t the privilege win. It’s the court-ordered disclosure of what went into ChatGPT: an inventory of discovery materials shared with the tool, identified by Bates number where possible, including documents produced under a protective order. That tees up the uncomfortable question every litigator should raise at the next meet and confer: if you paste confidential discovery into a generative AI platform, did you “disclose” it to someone outside the permitted recipients list, or did you simply use software? We end with concrete next steps for e-discovery teams and trial counsel: audit your active protective orders, negotiate AI-specific language before the fight starts, document tool usage and data sources, and make sure you can account for inputs if a motion to compel lands. If you find this helpful, subscribe, share with a colleague, and leave a review so more lawyers can keep up with how fast AI discovery law is moving. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • June 18 · 48 min

    When Expert AI Prompts Become Evidence

    Your expert uses generative AI to cut millions of documents down to something a human can actually read. Then the other side asks the question everyone has been dancing around: are the AI prompts and outputs discoverable? I walk through Conservation Law Foundation v Shell Oil Company (D. Conn.), where a magistrate judge answers “yes” and frames prompts as expert methodology under Rule 26, not some brand-new category of evidence. The twist: the ruling comes as a text-only minute order on the docket, and it’s currently stayed while the district judge reviews a Rule 72 objection, so the doctrine is moving in real time. We get specific about what was used and why that matters. The expert team worked with GPT-4 models through Microsoft Azure OpenAI Service via the secure Azure API, an enterprise deployment with a very different risk profile than the consumer ChatGPT product. That technical choice intersects with discovery obligations, vendor retention questions, and preservation planning. If you are relying on “we don’t have it” defenses, we also talk about the court’s trust-but-verify approach and how sworn Rule 33 and Rule 34 responses can create Rule 37 exposure if anything later turns up in logs, metadata, or cloud systems. From there, I pull out the practical drafting and strategy lessons: why Rule 29 stipulations must name AI prompts, AI queries, and AI outputs explicitly; why relabeling prompts as “search terms” won’t hold when the technology is generative; and how a prompt produced cold can be a gift to cross-examination unless the expert report explains the full AI methodology. We also connect the through line to Florida’s amended Rule 2.515, which puts citation accuracy and verification squarely on the signer, with sanctions on the table. If you work with testifying experts, eDiscovery, or AI-assisted document review, this is the roadmap you want before the next motion to compel lands. Subscribe, share the episode with your team, and leave a review so more litigators can keep up with how AI discovery doctrine is being built. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • May 13 · 42 min

    How an Enterprise Migration and an Extended Discovery Stay Created the Perfect Storm for Sanctions

    A legal hold system that “works” can still wipe out the evidence you need, and you may not realize it until the sanctions motion lands. We unpack a major Rule 37(e) preservation decision from DDC in United States ex rel. Staggers v. Medtronic that every litigator, legal operations leader, and discovery counsel should study, especially if your company is migrating email or sitting under a long discovery stay. We walk through the timeline problem that drives the whole outcome: a case served in 2016, discovery stayed for years, and an enterprise-scale Enterprise Vault to Microsoft Exchange migration happening in the background under a two-year retention policy. You’ll hear exactly how “dropped holds” and normal retention can quietly delete older ESI while dashboards still report that mailboxes are migrated. Then we split the analysis the way the court does: system-level migration steps can be reasonable under the Sedona Principles, while custodian-by-custodian legal hold timing can still be unreasonable and costly. We also dig into the practical litigation lessons: why deposition testimony is not a substitute for missing ESI, why “replacement” has to be substantially complete, why intent to deprive remains a high bar, and why you must prove prejudice with specific documents rather than generic argument. Finally, we highlight the real financial exposure that too many teams underestimate: multi-bucket fee awards for spoliation investigation, motion practice, and even fees on fees. If you’re responsible for eDiscovery, legal holds, retention policy risk, or managing outside counsel, listen through and pressure-test your preservation plan against this checklist. Subscribe to Meet and Confer, share the episode with a colleague, and leave a review with your biggest takeaway. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • April 8 · 1 hr 1 min

    The Latest Decision on the Use of Generative AI Tools and Confidentiality

    We break down Morgan v V2X, the most detailed federal ruling yet on generative AI, work product protection, and what happens when confidential discovery meets mainstream AI tools. We also track how Morgan fits with Heppner and Gilbarco and why the real fight is shifting toward protective orders, platform contracts, and access to justice. why Morgan v V2X becomes a turning point for AI in civil discovery the work product doctrine under FRCP 26(b)(3) and why it applies to pro se litigants when AI use does not equal waiver and why third-party access is not the whole story why prompts can be opinion work product and outputs may be qualified work product the court’s limits on protection and why tool name disclosure is treated differently a court-built framework for AI language in protective orders and why consumer AI often fails it the practical burden of training prohibitions, third-party flow-down terms, deletion rights, and documentation the emerging enterprise AI advantage and the access to justice gap it creates tactical takeaways on over-designation, tailoring discovery requests, and counseling clients on unsupervised AI use Please share this episode with your friends and colleagues. Subscribe to our blog at Minerva26 to follow all of our case of the week updates. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • March 24 · 35 min

    When the Platform Goes Dark: How Failure to Supervise Collection Led to Spoliation Sanctions

    A single analytics export can decide whether your damages story looks like math or guesswork. This week, we take on a spoliation decision out of the Southern District of New York that every litigator handling ESI should read, because the lost evidence is not email or chat logs. It’s Google Analytics website traffic data, the kind your marketing team lives in and your discovery plan might never mention until it’s too late. We unpack PharmacyChecker.com v. National Association of Boards of Pharmacy and the nightmare scenario behind the sanctions motion: Google’s Universal Analytics gets sunset, an IT employee downloads data without attorney direction, and a 19-month window of granular source-by-source traffic data (Google vs Bing vs others) disappears for good. When a party’s antitrust claims and damages theory depend on proving lost organic search traffic, that missing granularity becomes a hole you can drive expert cross-examination through. From there, we walk step-by-step through Rule 37(e)(1): duty to preserve, “reasonable steps,” whether the ESI can be replaced, and the prejudice finding that caps what a court can do. Judge Resnick’s prejudice analysis is unusually nuanced, and it directly shapes the remedies: no overbroad preclusion, but required caveats that the missing-period numbers are estimates, permission to tell the jury what happened, a potential jury instruction, and a targeted fee award. Along the way, we pull out practical eDiscovery lessons for SaaS preservation, dynamic databases, and meet and confer clarity when someone promises to “refresh the data.” Subscribe to the Meet and Confer podcast, share this with a colleague who handles discovery, and leave a review if these case-driven breakdowns help you stay ahead. What’s one third-party platform in your current matters you would preserve today if you knew access could disappear tomorrow? Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • March 3 · 26 min

    AI on Trial: The First Federal Rulings on Privilege and Generative Tools

    Two federal rulings issued the same week just redrew the map for AI, discovery, and privilege. We break down how Warner v. Gilbarco framed ChatGPT as a drafting tool and shielded a pro se litigant’s prompts and outputs, while U.S. v. Heppner denied privilege where a platform’s privacy policy allowed training and disclosure. The contrast is stark and deeply practical: facts, platform settings, and attorney involvement now drive whether AI-generated content is protected or exposed. We walk through what made the difference in each case—timing under Rule 26, the line between internal thought processes and actual documents, and whether counsel directed the AI work. Then we zoom into the privacy and confidentiality layer: why consumer AI settings can undermine privilege, how enterprise copilots promise stronger safeguards, and where platform policies can make or break your arguments. Along the way, we surface key quotes from the bench, including the “AI is a tool, not a person” framing and the warning that broad waiver theories would gut work product in modern drafting environments. To help teams act now, we share concrete steps: update custodian interviews to capture AI usage; set retention and logging rules for prompts and outputs; choose enterprise configurations that disable training; and document attorney direction when AI assists with strategy. We also flag the unresolved questions—what counts as ESI, how to handle prompt discovery requests, and what duties vendors have to preserve AI interactions—so you can anticipate challenges before they surface in meet-and-confers. If you’re advising clients who touch ChatGPT, Claude, Gemini, or Microsoft Copilot, this conversation is your primer on privilege, confidentiality, and eDiscovery in the age of generative AI. Subscribe, share with your team, and leave a review with your take: should AI-assisted drafts be treated like any other protected work product, or is the risk of disclosure too high without new rules? Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • February 18 · 25 min

    Slam Dunk for the Defense: How Missing Texts Cost an NBA Star His Case

    The dramatic spoliation of evidence case of former NBA star Charles Oakley shows how failing to preserve text messages can severely damage litigation outcomes. Oakley's misrepresentations about his texting habits and phone upgrades led to substantial sanctions in his case against Madison Square Garden. Text messages are primary evidence in most litigation cases and must be preserved Charles Oakley's case against MSG was undermined when AT&T records revealed he sent 800+ texts after the incident despite claiming he "doesn't text much" The court granted an adverse inference instruction after finding Oakley intentionally failed to preserve evidence MSG's counsel effectively used subpoenas to AT&T and other individuals to prove their sanctions motion The duty to preserve for plaintiffs may arise before filing the complaint, contrary to this court's finding Courts are increasingly considering sanctions against counsel who fail to ensure client preservation Multiple affordable technologies exist that can preserve mobile device data in just hours Link to Oakley decision Link to ModeOne Technologies for Mobile Device Collection If you're interested in seeing how Minerva 26 can help you engage in better discovery strategy, please visit us at Minerva26.com. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • January 30 · 18 min

    Your Client “Saved Everything,” Said No iPhone Ever

    Telling your client to “preserve their text messages” is not a preservation plan—and a new decision out of the District of Colorado makes that painfully clear. In this episode of Meet and Confer, Kelly Twigger breaks down Peddada v. Catholic Health Initiatives Colorado, where a magistrate judge found intentional spoliation after key text messages went missing. Even without a forensic smoking gun, the court inferred intent based on circumstantial evidence, third-party comparisons, and common sense. Kelly walks through what the court did, how Rule 37(e) was applied, and why mobile-device preservation failures create serious credibility and sanctions risk. She also flags a troubling trend: meaningful sanctions being deferred until after summary judgment—raising real questions about whether current remedies actually deter spoliation. Key takeaways include: Why self-directed text preservation is rarely defensible How courts infer intent when messages disappear What litigators should be doing early to reduce mobile ESI risk Why waiting on sanctions may be encouraging bad behavior If your case involves people, it involves text messages. And if you don’t get in front of that early, you’re building spoliation risk into your case. Case Links: ESI Order Court Issued Second Order Prompted Third Order Jones v. Riot Hospitality UF eDiscovery Conference Registration Sponsor ModeOne Technologies Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • January 29 · 1 hr 6 min

    Phones, Chats, and Subpoenas: DOJ/FTC Guidance Meets Mobile Reality

    Your chats are now your records. In this episode of Mobile Minutes sponsored by ModeOne Technologies, we dig into why mobile and off-channel messages—texts, WhatsApp, Signal, Slack, and Teams—have moved from “nice-to-have” discovery to core evidence and a core compliance obligation. With new DOJ and FTC guidance and eye-watering SEC penalties, regulators are no longer hinting; they’re spelling out what credible programs must include and how they’ll evaluate your effort, resources, and results. Ruth Hauswirth of Cooley joins Kelly Twigger to translate policy into practice. We break down what changed in 2024, how agencies define off-channel communications, and why “messages are documents” is the standard. Then we get tactical: approved channel lists, BYOD and retention controls that survive scrutiny, legal holds that actually reach phones, and supervised mobile collections that avoid the self-collection trap. We also tackle the messy realities—auto-delete defaults, device upgrades, shadow IT, and the speed regulators and courts now expect when preservation triggers. If you lead litigation, investigations, or compliance, you’ll walk away with a focused playbook: map your chat footprint, upgrade your holds with plain-English steps, run a tabletop for a subpoena or CID, and align legal, IT, HR, and security on a risk-based governance model. For global teams using WhatsApp or WeChat, we discuss harmonizing standards across jurisdictions and when to prohibit tools you cannot preserve. The through-line is simple: content over form, relevance and proportionality, and a documented, defensible program that proves you took this seriously before the knock on the door. If business lives in chats, compliance must live there too. Subscribe, share this with your legal and IT teams, and leave a review with one question you want us to tackle next. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
  • January 14 · 22 min

    Carvana and the New Hyperlink Fight: “Contemporaneous” Isn’t Automatic—It’s Earned

    Everyone’s finally past the first question on hyperlinked documents: yes, they’re discoverable. That debate is over. The real fight now is sharper—and it’s what makes the Carvana decision a must-read: when does a party have to produce a contemporaneous (point-in-time) version of a hyperlinked document, and what does the requesting party have to show to get that relief? Because in the cloud, the “attachment” is living. If you produce the file as it exists today, you may be producing something that did not exist when the email was sent. And courts are increasingly unwilling to let the timeline get rewritten—whether intentionally or not. Thank you for tuning in to Meet and Confer with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on creating cost-effective discovery strategies leveraging ESI, visit Minerva26 and explore our practical tools, case law library, and on-demand education from the Academy.

    • Transcript
    • Chapters
Showing 1–20 of 26 episodes