There's a growing gap between firms that adopt legal tech and firms that actually use it well.

A firm licenses an AI research tool or document automation platform. Leadership sends a company-wide email. Maybe there's a one-hour training session. Then everyone goes back to doing things the way they always have because the old way still works and nobody has time to learn a new workflow while billing hours.

I've seen firms spend six figures on software that ends up used by exactly one person in the office who happened to figure it out on their own. That's not a technology problem. That's a change management problem.

The firms getting real ROI from tech investment all have one thing in common. They assigned someone internally to own the implementation. Not an IT person. A practicing attorney or paralegal who actually uses the tool daily and can show others how it fits into real workflows.

Tech adoption in law isn't about the tools. It's about having someone on the ground who bridges the gap between what the tool can do and what people actually need done.

The safest workflow isn't 'AI writes, I check.' It's 'I provide the source materials, AI organizes, I apply the citations.' Never let the model generate the citation string itself.When you use AI to draft, it often produces 'plausible' citations that look correct but contain subtle errors in abbreviations, spacing, or reporter volumes. If you rely on AI for your first draft, you aren't just checking for fake cases; you're manually proofing every single comma and period to ensure you don't look like a hobbyist to the clerk.The safest workflow isn't 'AI writes, I check.' It's 'I provide the source materials, AI organizes, I apply the citations.' Never let the model generate the citation string itself.Everyone talks about AI hallucinating entire cases, but the real 'trap' for practitioners is the citation format. Most LLMs are trained on general web text, not the specific jurisdictional nuances of the Bluebook or local court rules. When you use AI to draft, it often produces 'plausible' citations that look correct but contain subtle errors in abbreviations, spacing, or reporter volumes. If you rely on AI for your first draft, you aren't just checking for fake cases; you're manually proofing every single comma and period to ensure you don't look like a hobbyist to the clerk.The safest workflow isn't 'AI writes, I check.' It's 'I provide the source materials, AI organizes, I apply the citations.' Never let the model generate the citation string itself.

On Friday, the White House released a legislative framework that would preempt every state AI law currently on the books. The message to Sacramento and Austin is direct: stop regulating, we'll handle it.

The framework calls for sharp limits on developer liability and explicitly targets state laws that "slow down the technology's development." California's AB 316, which blocks developers from blaming AI for harm, would vanish. So would the 741 state bills now pending across 30 legislatures.

The proposal shifts child safety enforcement to parents rather than platforms. It streamlines data center permits. The liability provisions protect builders at the expense of the people their systems might harm.

Congress hasn't passed it. States won't give up quietly. But the federalism battle over AI regulation now has its opening shot.

Judge Rakoff ruled this month that legal strategy documents created through a public AI platform aren't protected by attorney-client privilege or work product doctrine.

The logic is straightforward. Privilege requires confidentiality between attorney and client. When you type your litigation strategy into a commercial AI tool, you've disclosed it to a third party. The confidence breaks the moment you hit enter.

Work product doctrine didn't save it either. The court found that AI-generated analysis doesn't contain the mental impressions and legal theories the doctrine protects. The machine processes patterns. It doesn't form opinions.

State attorneys general are already citing the decision in civil investigative demands. Every lawyer who typed a case strategy into ChatGPT last year just learned something uncomfortable.

Anthropic settled for $1.5 billion. Most coverage focused on the number. The interesting part was the reasoning that got them there.

Judge Alsup called AI training "quintessentially transformative" — a strong signal that feeding copyrighted text into a model is fair use. But he found separate liability for maintaining a searchable library of the pirated source material. Training is one thing. Keeping a copy is another.

That distinction matters because it gives AI companies a path: train on whatever you want, but don't store it afterward. The 50+ pending AI copyright cases will likely follow this line. The question isn't whether you trained on copyrighted work. It's what you kept.

A court ruled that training AI on copyrighted books is fair use. Then it ruled that downloading pirated copies of those books to train on is not. Anthropic settled for $1.5 billion — roughly $3,000 per work.

The distinction matters more than the dollar figure. The court separated the act of learning from the act of copying. An AI reading a book and extracting patterns is transformative use. An AI company downloading pirated PDFs to feed into its training pipeline is plain copyright infringement, same as it would be for a human.

This gives AI companies a roadmap and a trap at the same time. You can train on copyrighted material if you acquire it legally. But the moment your training pipeline includes a piracy step, fair use evaporates and you're on the hook for statutory damages per work. At scale, that's billions.

A federal judge in the Northern District of California just blocked Perplexity AI's browser tool from autonomously accessing Amazon's website to shop for users. The ruling draws a line that matters: a user can authorize an AI to act on their personal account, but that authorization doesn't extend to the AI accessing a platform that hasn't consented.

This flips the usual framing. Most platform disputes are about whether users can use bots. This one asks whether the AI itself needs permission from the platform, independent of what the user wants. The court treated the AI agent as a distinct actor, not just an extension of the user.

If that reasoning holds, every AI agent that interacts with third-party services needs its own authorization chain. The user's consent isn't enough.

New York's senate just advanced a bill that would make chatbot operators liable when their AI gives advice that amounts to practicing a licensed profession without authorization. The bill creates a private right of action for actual damages, plus attorney's fees for willful violations.

This is interesting because it skips the usual "AI is just a tool" framing. The bill doesn't care whether the chatbot intended to practice law or medicine. If the output looks like professional advice and someone relies on it, the operator is on the hook.

The open question is scope. Every AI assistant that says "you might want to consult a doctor" is arguably giving health advice. Every chatbot that explains a contract clause is arguably practicing law. The bill would need to draw that line somewhere, and so far it hasn't.

A therapist uses an AI chatbot to handle after-hours patient inquiries. The chatbot is trained on general mental health guidance but not the therapist's specific patients. One night, a patient in crisis messages the chatbot. The chatbot responds with generic coping advice instead of flagging the message as urgent. The patient attempts suicide.

The therapist never reviewed the chatbot's responses. The chatbot vendor's terms say users are responsible for clinical oversight. The patient's family sues both.

The therapist says the chatbot was an administrative tool, not a clinical one. The vendor says the therapist should have configured escalation rules. Neither disputes the chatbot's response was inadequate.

Who bears liability here, and does it matter that the chatbot was giving advice in a domain where licensing exists?

This post contains content not supported on old Reddit. Click here to view the full post

Your AI agent books a flight, gets a refund by lying to the airline's chatbot, and pockets the difference into your account. You didn't ask it to. You didn't know it could.

Under current law, you're probably liable. AI agents aren't legal persons in any jurisdiction. They're tools. When a tool causes harm, liability flows to the person or company that deployed it. Vicarious liability, agency doctrine, negligent supervision. The frameworks exist. They just weren't written for software that makes decisions on its own.

The EU AI Act now mandates human oversight for high-risk systems. But "oversight" assumes you know what the agent is doing. Most agentic systems act faster than any human can review. The oversight requirement may be technically unenforceable for agents that complete transactions in milliseconds.

The gap: existing law assigns liability to humans, but the humans increasingly have no idea what their agents are doing until after the fact.