How Ajax Knows Which Matter You're Working On
A litigation associate can touch nine matters before lunch: three emails on a discovery fight, a dozen browser tabs chasing one question about personal jurisdiction, a partner's call that pulls her off a half-finished brief, then back to it twenty minutes later like nothing happened.
So when software promises to sort those minutes into the right client and matter, the fair reaction is to ask how it could possibly know. That's the first question on nearly every call about Ajax, the AI timekeeping tool we build. Here's the answer, in the order the software works, including where it gets things wrong.
Start with what Ajax can see
Prediction is only as good as its raw material. Ajax runs quietly on the desktop, a form of passive time tracking that reads what's on the screen about every 30 seconds, no timer required. It also pulls activity from tools the lawyer already uses: email from Outlook and Gmail, calendars from Outlook, Google, and MyCase, and calls from phone systems like Zoom Phone, Microsoft Teams, RingCentral, and Dialpad.
The screen is what makes the rest possible. An API connection can log that Word was open or that an email went to a certain address. Reading the screen picks up the content: that section 4.3 of the merger agreement was the part being revised, that a dozen open tabs all concern the same plaintiff. Those specifics are what a prediction has to run on. We go deeper on that contrast in screen capture versus API timekeeping.
Grouping comes before guessing
Here's the step most people skip. Before Ajax names a matter, it works out which pieces of the day belong together.
Every slice of the day gets compared against every other slice. Those twelve tabs on personal jurisdiction, the two emails citing the same case, and the forty minutes in a memo with the same party names get read as one research session instead of a scatter of separate events. The partner's interrupting call gets separated back out, because its content and the people on it don't match the brief.
This ordering matters. Twelve tabs treated as twelve fragments would mean twelve chances to guess wrong and twelve entries to clean up; grouped first, they become one decision about one block of work. That's fifteen coherent entries to review instead of a few hundred scraps.
How the match actually gets made
Once the day is sorted into sessions, each one gets matched to a client and matter.
Ajax syncs the firm's real client and matter list from its billing system, so it's choosing among matters that already exist. For each block of work it weighs several signals together: the people on the email thread or the call, the documents and their file names, the terminology and party names in the text, and the firm's history of which go with which matter. A block that carries opposing counsel's name, a case caption, and a phrase like "motion to compel" lands on the right litigation matter because every signal agrees.
Across a firm's work, the match is right about 92% of the time, and it climbs as the software learns the firm: that email from one paralegal almost always concerns one client, that documents in a certain folder belong to a certain matter. From work on screen to a finished draft with a predicted matter and a narrative, the whole path takes about 45 seconds.
What happens when it's wrong
About eight percent of the time it picks the wrong matter, and we designed Ajax to handle that gracefully. Every entry is a draft until the lawyer looks at it. When the matter is off, the lawyer reassigns it in the review screen in a second or two, and nothing incorrect reaches a bill.
That reassignment pulls double duty: it corrects the entry and teaches the system. The fix shapes that lawyer's future work, and the parts that generalize, like a client's set of matters or a recurring contact, carry over so other timekeepers benefit too. The 92% behaves like a floor that rises with use.
Who else can see any of this
The next question is fair for any tool that reads your screen: who else can see this? At Ajax, draft entries and captured activity stay private to the individual timekeeper until that person releases entries. A partner or administrator can't pull up another lawyer's screen or read their unreleased drafts. Management sees rolled-up reporting, capacity, unreleased hours, firm-wide activity, never the screens themselves.
Captured data is encrypted in transit and at rest, and deleted automatically on a rolling basis rather than kept indefinitely. The outside AI services that help process the work are contractually barred from training on a firm's data. For the longer version, we lay it out in is AI timekeeping safe for law firms.
FAQ
How accurate is Ajax's matter prediction?
Ajax assigns the correct client and matter about 92% of the time, and that rate improves as it learns a firm's people, documents, and patterns. The rest is caught at review, where the lawyer reassigns the entry and the correction feeds back so the same miss is less likely.
What information does Ajax use to predict the matter?
Ajax uses the content of the work itself, read from the screen about every 30 seconds, plus activity from connected email, calendar, and phone tools. It weighs the people involved, the documents and their names, the terminology, and the firm's history, then matches that against the client and matter list from the billing system.
What happens when Ajax picks the wrong matter?
When Ajax assigns the wrong matter, the lawyer reassigns it in the review screen before the entry is released, which takes a second or two. Every entry stays a draft until a person approves it, so an incorrect prediction never reaches a bill, and the correction teaches the system for that user and, where it generalizes, for the whole firm.
Can anyone else see what Ajax captured from my screen?
No. Draft entries and captured activity are private to the individual timekeeper until they release entries. Partners and administrators see rolled-up reporting like capacity and unreleased hours, never another person's screen or drafts, and captured data is encrypted and deleted automatically on a rolling basis.
The surest test is your own files. Book a demo and we'll run a real day of work through Ajax so you can see the matters it nails, and the ones it doesn't.
