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.

  1. 3d ago

    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.

  2. Nov 4

    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.

  3. Oct 21

    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.

  4. Oct 15

    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.

  5. Sep 23

    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.

  6. Sep 9

    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.

  7. Aug 26

    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.

  8. Aug 14

    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.

Trailer

Ratings & Reviews

5
out of 5
8 Ratings

About

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.

You Might Also Like