The tools on my desk

I use AI. Here's how.

I'm human, and I don't pretend to know where any of this is headed. What I can tell you is that my AI once found something in one of my cases that I'd have missed.

Medical bills don't arrive in sentences. They arrive in codes. Left to myself, I'd have turned past that page thinking it was a column of numbers. Claude read the page and told me what the codes described: a hospital admission the plaintiff hadn't disclosed, which didn't appear in a single record we had been given. Running those records down afterward was just legwork, and case-changing.

Claude takes the reading, the sorting, and the first drafts, so that more of my time goes to the parts of a case that need a lawyer, and less of your bill goes to the parts that don't. What follows is the whole picture, including the places where I'm careful, and why.

Where the tools do the work

The heavy, repetitive, expensive parts.

Records

Summarizing medical records

My office requests the records, keeps a patient ledger of everything still owed to us, and follows up with anyone who hasn't sent it. That part is ours. What the tools do is read what comes back, index it and summarize it, so that by the time I sit down with a file I'm reading the pages that matter instead of hunting for them. On a serious injury case that's thousands of pages, and it used to be thousands of pages of billable review.

For a long time the only way to do that was a person, page by page, and the hours appeared on the invoice. There's another way now, and I'd rather not send you a bill for it.

Instead, I use a product designed specifically for law firms. It reads the entire record set and surfaces the things that decide these cases: the old injury to the same knee, the degenerative findings that predate the accident by a decade, the eight-month stretch with no treatment at all, the history given to one doctor that doesn't match the history given to the next. Then I can ask questions in plain language and get answers drawn from the records rather than from thin air.

Ten thousand pages of medical records, and the answer to almost any question I put to them in about twenty seconds. When did the plaintiff first complain of headaches? What was the total billed to Medicare? Is there a reference anywhere to a provider whose complete records I don't already have? Questions that once cost a day of paging through binders now cost less than a minute, and every answer still gets checked against the record before I rely on it.

In my firm, we don't outsource the collection of medical records. That's a deliberate choice, and here's why.

Record retrieval is often handed to a vendor, and I understand the appeal. But a vendor is paid to send a request and forward whatever comes back. No vendor has any reason to notice what didn't come back.

Every record that arrives here gets read for the names of other providers: another doctor, a lab, an imaging center, a therapist, an emergency room visit two years before the accident. If a record points to treatment we don't have, we chase it down. One set leads to the next until the trail runs out.

There's a reason I'm this stubborn about it. In almost every FELA and personal injury case I've tried, I've shown the jury far more of the plaintiff's medical records than the plaintiff's own lawyer did. In my experience, the complete medical file helps the defense more than it helps the plaintiff. In one admitted-liability FELA trial, the plaintiff had back surgery after a derailment and asked the jury to hold the railroad responsible for it. A single line in the surgical nursing notes told a different story: he had admitted to a nurse that he had needed that surgery for years and had simply been putting it off. The jury returned a defense verdict.

That's why, once a client agrees the full medical file is worth the effort, I don't consider the job finished until we have every record we know about.

Over the years I've been brought into many cases that another firm worked up first. When the record collection was outsourced, it shows, usually in the form of large holes in the medical history. So the tools carry the reading here, and the collecting stays with us.

Analysis

Spotting issues in a file

Claude gives the record a second read and never gets tired doing it. Claude flags inconsistencies, gaps, dates that don't line up, and things worth a closer look. Claude raises the questions. Answering them, and deciding anything, stays with me.

Drafting

First drafts

Letters, interrogatories, deposition outlines, deposition summaries, and the other documents in a case that follow a known shape. What comes back is a first draft and gets treated like one. Every word of it goes through me before it leaves the office.

Calendar

Scheduling, invitations, and deadlines

Setting meetings and circulating calendar invitations. Docketing works the other way around. My staff and I calculate every deadline ourselves, from the rule and the order, and we're the ones who enter it and set the tickler behind it. Artificial intelligence runs second, as a check on us, re-reading the order and recomputing the date so Claude can flag a disagreement for one of us to resolve. Claude never sets a deadline and never puts anything on the docket.

Operations

Keeping the file moving

Claude also handles the paperwork that keeps a case moving. It puts documents on my letterhead and in the format the court requires. It prepares certificates of service and cover letters, and makes sure the right version of a document, PDF or Word, reaches the right person. It drafts my time entries the same day I do the work, instead of my rebuilding them from memory at the end of the month, which is all too common in law firms. And it finds things: a form I used two years ago, an exhibit buried in a stack of produced documents, the one email where someone agreed to something. You rarely see this work, but you pay for it, so the faster it gets done, the less it costs you.

The part that matters

I verify everything.

Every citation, every record summary, every date, every figure. Nothing produced with these tools goes to a client, to opposing counsel, or to a court until I have checked it against the source myself. These systems are fast and fluent and occasionally wrong, and it's the last of those three that decides how you have to work.

Part of every system I use

Claude runs across my whole technology stack rather than sitting in a browser tab off to one side: document management, email, calendar, billing, and the case files themselves. That integration is what makes Claude useful.

Built with advice

I did not set this up on my own. Legal experts are advising me on doing it in compliance with applicable law and with my ethical obligations, including confidentiality, competence, and the supervision of any assistance a lawyer uses. ABA Formal Opinion 512, issued July 29, 2024, is the guidance that addresses generative artificial intelligence in a law practice. It is the standard this is built against.

The judgment stays mine

No tool decides what to argue, what to concede, whom to depose, or what a case is worth. Those are the things you're hiring a lawyer for, and delegating them would defeat the point of hiring one.

Ask me anything about it

If you want to know how any part of this touches your file, ask. I'd rather walk a claims department through it in detail than have anyone guess.

Confidentiality

Your file never trains the AI.

The American Bar Association's ethics committee identified the real confidentiality danger in these tools, and it is a specific one. ABA Formal Opinion 512 warns that "self-learning" tools, the kind that keep learning from whatever users put into them, "by their very nature" risk letting one client's information surface in work done for someone else. Before a lawyer puts client information into a tool like that, the opinion requires the client's informed consent.

Claude doesn't work that way here. My firm uses Claude on Anthropic's Team plan, which is governed by Anthropic's commercial terms, and Anthropic's published policy is plain: by default, it "will not use your inputs or outputs from our commercial products" to train its models. What Claude reads in your file is used to do the work on your file. It is not folded into the model, and it is never drawn on to answer anyone else's questions. The policy names one exception, feedback a user chooses to submit, and the firm doesn't submit feedback on client work.

Opinion 512 also tells lawyers to read and understand the terms of use and privacy policy of every AI tool they rely on. I have, and you can read the ones that govern my firm's account yourself: Anthropic's Commercial Terms of Service, its Data Processing Addendum, and its policy on model training for commercial accounts. Terms like these change over time, so I keep dated copies of each. If you ever want to see what was in force while I handled your file, ask and I'll send them.

The decision

I have decided to embrace AI.

I made that decision deliberately. I don't know exactly where artificial intelligence is headed, and I'm wary of anyone who claims to. But I believe the firms that learn to use it well will do better work, faster, and at less cost to their clients, and that the firms that don't will find it harder and harder to keep up with the ones that do. It's already difficult to justify billing a client for four thousand pages of reading that Claude can do in an afternoon, so long as a lawyer checks every line of what comes back.

The conversation runs both ways. I can work with you on how artificial intelligence could streamline your own operations, from claims handling to record keeping, and on where it could create exposure you would rather avoid. For railroads, there's a page devoted to exactly that.

Learning it properly

I went to Los Angeles to learn it.

Deciding to use a tool is the easy part. Learning to use it well, and safely, is the work. So I flew to Los Angeles for a seminar built to teach attorneys how to put Claude to work in a law practice: not the headlines, but the daily use of it on real files, with real confidentiality obligations attached. In my view, and at least as of now, Claude is the best fit for my practice.

I try to be open about where Claude helps and how I check its work. I welcome questions about any of it.