Recently, at about 9 o’clock at night, my partner texted me. She had a temporary support hearing the next morning and the file hadn’t been prepped. Every family lawyer knows that feeling.

I was lying in bed with my phone. I sent my AI paralegal one message: tomorrow there’s a hearing on this matter and the file hasn’t been prepped. Because I was on my phone, I also pasted the link to the client’s folder. On my computer, I wouldn’t have needed to.

It answered: got it, tomorrow’s hearing is before this magistrate, I’m building the packet and saving everything to the matter folder. About ten minutes later, it was done.

What it actually checked

This is the part that matters, because a pretty summary isn’t the point. The useful part is what it caught.

• The general magistrate’s procedures. It knows to look these up every time. It flagged a 48-hour requirement and noted it couldn’t find confirmation that exhibits had gone to chambers.
• Who’s actually on the case. Opposing counsel was set to appear, but there was no notice of appearance in the file. Worth knowing before you walk in.
• The financial affidavit. It went through the financial affidavit and found issues we hadn’t caught, then listed the decisions my partner needed to make about them.
• The numbers. It ran the support guidelines and laid out the figures for the hearing.
• The logistics. It confirmed the Zoom link and suggested a ten-minute prep call with the client, with the questions to ask.

Then it gave us the theory of the hearing, direct and cross outlines, the other side’s likely exhibits and arguments, a list of files it couldn’t read, and what to do after the hearing.

I read it, then I pushed back

I didn’t forward it blind. I read the whole packet and had a couple of questions, so I asked whether it had read all of our internal Slack messages on the case. It went back, updated the packet, and gave me a PDF version for printing. Then it posted everything to the client’s Slack channel for my partner: the interactive version, the PDF, and a short list of what she needed to know.

At 6:45 the next morning, she decided she couldn’t go forward and asked for a motion for continuance. It was drafted by 6:51. Then a lawyer reviewed it before it went anywhere, because that part doesn’t change.

Why one sentence was enough

It wasn’t the sentence. It was everything underneath it.

The client folder was organized. It knew where pleadings, financial affidavits, and correspondence lived, because our folders follow the same structure on every matter.

The communication was readable. Our internal Slack and email were connected, so it could see what the team had discussed about the case, not just what was filed.

The procedures were taught once. It checks magistrate procedures on every hearing because we told it to, one time, and it kept doing it.

The guidelines were built in. Support calculations ran inside the same system instead of a separate app.

That’s the difference between an AI that writes a generic hearing outline and one that tells you opposing counsel never filed a notice of appearance. The second one is reading your file. I wrote about why AI failure is usually a file structure problem, and this is the flip side. When the file is right, the output is specific.

What this does and doesn’t replace

It doesn’t replace the attorney. My partner still decided whether to go forward. I still read every line. Nothing was filed or sent to the other side without a lawyer’s sign-off.

What it replaces is the hours of digging through a file at 9 PM to figure out what you’re walking into. That work still happens, and it’s thorough. Now it takes ten minutes, and the lawyer spends her time on judgment instead of searching.

A coaching client of mine described the same shift from her side. She used to keep everything about her 56 open files in her head and live with the low-grade fear that she’d forgotten something. Now she asks, and the answer comes back from the file.

If you want to see what this looks like on one of your own cases, bring it to Open Office Hours, Fridays 2:00 to 3:00 PM ET. Join on Zoom. Or book a custom build strategy session and we’ll map what your file needs so one sentence is enough.