🗣️ Shout Out! Carolyn Elefant’s "Be the Bellwether AI Litigator" Summit — And Why I’m Demonstrating Perplexity for Litigation Research on September 17-18 ⚖️🤖

Every so often a program comes along that treats artificial intelligence the way practicing litigators actually experience it — as an evidence problem, a privilege problem, a candor problem, and only then as a productivity tool. 🎯 Carolyn Elefant’s Be the Bellwether AI Litigator summit is that program. It runs online September 17–18, 2026, and I am delighted to give it a full-throated Shout Out!

I have an interest to disclose. I am one of the presenters. On Day Two, September 18, at 11:00 a.m., I am demonstrating "Perplexity for Litigation Research" — a ten-minute, screen-shared walkthrough followed by five minutes of Q&A. No slides about the future of law. Just the tool, a real research problem, and the verification work that has to follow. You can see the full lineup in the Bellwether AI Litigator Summit agenda and register through the summit program page.

Why Carolyn Elefant Earned This Shout Out 👏

Carolyn has been the standard-bearer for solo and small-firm lawyers for more than two decades at MyShingle.com. She is a Cornell Law graduate, an ABA Legal Rebel, an inaugural Fastcase 50 honoree, and a recipient of the American Legal Technology Lifetime Achievement award. She has trained roughly 2,500 lawyers on AI ethics and policy since ChatGPT arrived. Critically, she still litigates. She fights energy cases at FERC, state PUCs, and in court. That matters. Her programs never drift into vendor theater.

The summit reflects that discipline. It is a day-and-a-half intensive built for solos, boutiques, larger firms, government lawyers, and public-interest litigators — the whole bench, not just BigLaw innovation officers.

Day One: Courts, Consequences, and Judgment ⚖️

Day One is themed "Courts, Consequences, and Litigation Judgment," and the faculty list is genuinely strong.

Carolyn opens at 10:00 a.m. with a survey of 800+ standing orders on AI use in courts. Let that number sit for a moment. Eight hundred. Adam Feldman follows with "What We Learned From the Hallucination Cases." Nathan Gaffney addresses privilege rulings. Hilary Gerzhoy and Professor Jonah Perlin pair scholarship with hands-on confidentiality guidance. Shlomo Klapper and the Hon. Brian D. Palmucci offer the judicial view at 1:00 p.m. Will Moye brings an expert’s ChatGPT war story, Nick Rishwain covers expert prompts and disqualification risk, and Christopher Kercher closes the day with the AI-native litigation firm.

That sequencing is not accidental. It tracks the ethical architecture most of us are still assembling.

The Model Rules Are Not Optional Here 📋

Regular readers know this drum. I keep beating it.

Model Rule 1.1, Comment 8 makes technology competence an ethical duty, not a hobby. Forty-one jurisdictions have adopted it. You cannot supervise what you do not understand.

Model Rule 1.6 governs confidentiality, and ABA Formal Opinion 512 sharpened the point: think hard before client-identifying information enters a public large language model. Gerzhoy and Perlin’s session goes directly at vendor terms, retention, and enterprise-versus-consumer platforms.

Model Rule 3.3 demands candor toward the tribunal. Fabricated citations are the most public failure mode of the past three years, and the duty to correct continues until the proceeding ends. I walked through the remedial protocol in 🪙🪙 MTC: When Reputable Databases Fail: What Lawyers Must Do After AI Hallucinations Reach the Court, where Stanford’s research showed Lexis+ AI hallucinating at 17% and Westlaw’s AI-Assisted Research at roughly 34%. Paid platforms are not a safe harbor. 🚨

Model Rules 5.1 and 5.3 put supervision of lawyers and nonlawyer assistance squarely on you. If your paralegal breaches confidentiality through a chatbot, that is your breach.

Model Rule 8.4(c) covers dishonesty and misrepresentation — increasingly relevant as altered and generated evidence reaches the courtroom. I covered that ground with Professor Jennifer Wondracek’s students in 🎙️ TSL.P EP# 132: AI, Deepfakes, and Metadata, including Mendones v. Cushman & Wakefield and the terminating sanctions that followed.

Day Two: Ten Lawyers, Ten Screens 💻

Day Two is the part I find most valuable, and not because I am on it.

Ten practicing litigators share their screens and run real workflows end to end. Porter Heath Morgan on in-house litigation management. Sarah Bashir on family law. John Stobart using Claude at trial. Regina Edwards on discovery. E. Aaron Cartright III generating thirteen litigation documents from one structured input. Arthur Rothrock running a case start to finish. Jim White on Obsidian. C. Todd Smith on Copilot. Descrybe.ai on emerging research tools.

Each demonstration answers four questions: What problem was the lawyer solving? What did AI actually do? Where did it fail? What did the lawyer have to verify?

That third question is the one vendors never answer. It is the reason this summit is worth your time.

My own segment will show how I use Perplexity to help with litigation research — building queries, evaluating sources, and, most importantly, the verification loop that follows every single output. Reading the underlying authority is not negotiable. If you have followed The Tech-Savvy Lawyer.Page Podcast, you know I treat AI drafts as hypotheses, never as answers. 🧪

Practical Details 📅

Registration is open, early-bird pricing is $249, and every participant receives the Bellwether Litigator Resource Kit — covering court AI-order tracking, pre-filing verification, citation and quotation checking, protective orders, vendor due diligence, and human-review protocols. Tickets are also available via Eventbrite.

Come for the judges. Stay for the screen shares. And please say hello during my Q&A. 👋

Congratulations, Carolyn. This one is going to matter. 🎉

When AI Falls Short - What Legal Professionals Must Know Before Relying on Microsoft Copilot and Similar Embedded AIs.

AI Errors in Legal Practice Demand Vigilant Attorney Oversight!

Any reader of my blog should realize by now that artificial intelligence is no longer a novelty in law practice; it is embedded in research platforms, document automation, e‑discovery, and now in tools like Microsoft Copilot that appear inside the same Microsoft 365 ecosystem lawyers already live in. Yet Copilot’s own terms of use long described it as being “for entertainment purposes only,” while Microsoft has simultaneously marketed it as an enterprise‑grade productivity assistant and is now backing away from prominent Copilot buttons in several Windows 11 apps. For lawyers who must live under the ABA Model Rules of Professional Conduct, this tension is not an amusing footnote; it is an ethics problem waiting to happen. 

Microsoft’s Copilot terms have advised that the service “can make mistakes,” “may not work as intended,” and should not be relied on for important advice. At the same time, Microsoft has begun removing or rebranding Copilot buttons from Notepad, Snipping Tool, Photos, and Widgets in Windows 11, framing this move as an effort to reduce “unnecessary Copilot entry points” and be “more intentional” about where AI shows up. The features, or at least the underlying AI, are not disappearing entirely; they are simply becoming less conspicuous. For the practicing lawyer, the message is clear: powerful AI is being woven into everyday tools, but its creators still do not want you to rely on it the way you rely on a human associate. 🤖

when AI falls short, it is the lawyer—not the software vendor—who will have to answer to clients, courts, and regulators.

⚠️

when AI falls short, it is the lawyer—not the software vendor—who will have to answer to clients, courts, and regulators. ⚠️

That is precisely where the ABA Model Rules step in. Model Rule 1.1 requires competent representation and, through Comment 8, includes a duty to keep abreast of the benefits and risks of relevant technology. Using AI in law practice is increasingly seen as part of that competence obligation, but competence does not mean blind trust in unvetted outputs from a system whose own terms warn you not to rely on it. A lawyer who treats Copilot’s draft as a finished research memo, brief, or contract without independent verification risks violating the duty of competence every bit as much as a lawyer who never learned to use electronic research tools in the first place.

Model Rule 1.6 on confidentiality presents a second, and in many ways more pressing, concern. Generative AI systems may store, log, or otherwise use prompt content for analysis and improvement, which means uncritical copying and pasting of confidential client information into Copilot can create a non‑trivial risk of exposure. The ABA and commentators have emphasized that before entering client data into a generative AI tool, lawyers must assess whether that data could be disclosed or accessed by others, including through unintended re‑use in future outputs to different users. That risk analysis is not optional; it is part of your obligation to make reasonable efforts to prevent unauthorized access or disclosure.

Fake Citations from AI Tools can Threaten Accuracy and Legal Ethics!

Model Rules 5.1 and 5.3, which govern the responsibilities of partners, managers, supervisory lawyers, and non‑lawyer assistants, also apply to AI use. When you deploy Copilot in your firm, you are functionally introducing a new category of “assistant” whose work product must be supervised like that of a junior lawyer or paralegal. Policies, training, and review procedures are needed so that AI‑drafted content is consistently checked for accuracy, bias, hallucinations, and improper legal conclusions before it ever reaches a client, court, or counterparty. Ignoring Copilot’s disclaimers and Microsoft’s own hedging around reliability is, in effect, ignoring red flags that any reasonable supervising attorney would address.

Model Rule 1.4 on communication adds yet another dimension: transparency with clients about how you are using AI in their matters. Authorities interpreting the Model Rules have stressed that lawyers should keep clients reasonably informed, which includes explaining when and how AI tools are utilized to assist in their cases. This is particularly important where AI may affect cost, turnaround time, or the nature of the work performed, such as using Copilot to generate a first draft instead of assigning that task to an associate. Engagement letters and fee agreements are increasingly incorporating language about AI use, both to set expectations and to align with evolving ethical guidance.

The “for entertainment purposes only” language is more than a curiosity; it is a signal about allocation of risk. Microsoft’s disclaimer mirrors language historically used by psychic hotlines and other services seeking to avoid responsibility for inaccurate advice. When such a disclaimer is attached to a tool you might be tempted to use for legal analysis, the tool is telling you that you assume the risks of errors. Under the Model Rules, those risks ultimately translate into potential malpractice, sanctions, or disciplinary action if AI‑generated errors make their way into filed documents or client counseling.

Recent real‑world incidents involving lawyers who submitted briefs containing AI‑fabricated citations demonstrate how quickly misuse of generative AI can cross ethical lines. In those cases, the core problem was not that AI was used; it was that the lawyers failed to verify the content and then misrepresented fictitious cases as genuine authority to the court. That behavior implicates Model Rules 3.3 (candor toward the tribunal) and 8.4 (misconduct) along with competence. Copilot’s warnings about possible mistakes do not excuse a lawyer from the duty to check every citation, quote, and legal conclusion that AI produces before relying on it.

lawyers must assess whether that data could be disclosed or accessed by others

⚠️

lawyers must assess whether that data could be disclosed or accessed by others ⚠️

For practitioners with limited to moderate technology skills, the answer is not to abandon AI entirely, but to approach it with structured safeguards. A practical workflow might involve using Copilot to outline a research plan or draft a first pass at a contract clause, followed by standard legal research in trusted databases and rigorous review by a human lawyer before anything is finalized. Firms should configure Copilot and other AI tools in ways that minimize data exposure, such as disabling cross‑tenant learning, a feature that lets the system learn from patterns across multiple organizations’ environments, where possible, and restricting which matters and users can access certain features. Training sessions can focus less on technical jargon and more on concrete do’s and don’ts tied directly to the Model Rules, which is the language most lawyers already speak. 🧠

alawys Protect Client Confidentiality When Using AI in Modern Law Practice!

Governance is also essential. Written AI policies should address acceptable use cases, prohibited content for prompts, mandatory review standards, logging and auditing of AI‑assisted work, and incident response if an AI‑related error is discovered. These policies should be backed by regular training and by leadership that models appropriate use, rather than quietly delegating AI experimentation to the most tech‑savvy associates. Vendors’ evolving terms of use—including Microsoft’s move to revise its “entertainment purposes” language and adjust Copilot integration in Windows—should be monitored and incorporated into risk assessments over time.

In short, when AI falls short, it is the lawyer—not the software vendor—who will have to answer to clients, courts, and regulators. Copilot and similar tools can be valuable allies in a modern legal practice, but only if they are treated as fallible assistants whose work must be checked, not as oracles. The ABA Model Rules already provide the framework: competence, confidentiality, supervision, and honest communication. The task for today’s legal professionals is to apply that framework thoughtfully to AI, recognizing both its promise and its very real limitations before letting it anywhere near client work or court filings. ⚖️🤖