AI Timekeeping for Litigation and Insurance Defense
You send a batch of invoices to the carrier. Two weeks later some of it comes back reduced: a block-billed line that bundled four tasks into one, a paralegal's exhibit-organizing time written off as clerical, a narrative that read "review file" and told the reviewer nothing. Now someone rebills it, and payment slips another cycle.
Defense work is the most scrutinized billing in law, and insurance defense billing is where that scrutiny bites hardest. Carrier guidelines decide what counts, invoices pass through e-billing review before a human ever reads them, and every vague or miscoded entry is an invitation to a write-down. Here's the rulebook defense firms bill under, and where contemporaneous, AI-drafted timekeeping fits it. Ajax, the tool we build, is one option in that category, and the mechanics below are general.
What defense firms bill under
Three layers sit between a defense lawyer's work and a paid invoice.
Task codes come first. Most carriers require UTBMS coding, the standardized litigation phase and activity codes (L-codes for litigation work, A-codes for activities, E-codes for expenses) that let a carrier compare spend across every firm on its panel. Each line needs the right code or it doesn't reconcile.
LEDES is the format. Invoices arrive as LEDES files, a fixed electronic layout the e-billing system parses line by line. A PDF doesn't clear; the data has to be structured.
Outside counsel guidelines are the rulebook. A carrier's outside counsel guidelines spell out what it will and will not pay for: no block billing, no clerical or administrative time, staffing limits, often a cap on internal conferences or non-working travel. Break a rule and the line comes back reduced or rejected.
Getting it wrong costs more than the written-down dollars - the rework and resubmission add weeks to a payment cycle that was already slow. In panel counsel billing, precise entries are the difference between getting paid on schedule and getting paid twice as late.
Why contemporaneous capture holds up under bill review
Here's the mundane cause of most write-downs: memory. When you rebuild a week from your sent folder on Friday, you round and you generalize, and you write "review file" because you genuinely cannot remember which document it was. Generalizations are the first thing a bill reviewer flags.
Contemporaneous capture removes the reconstruction. Software that reads the work as it happens knows the entry was 1.8 hours on the motion to compel rather than a generic "discovery," because it saw the brief on the screen while you wrote it. Ajax reads the screen about every thirty seconds and turns the day into draft entries within roughly a minute of the work, so the detail is there in the first draft instead of being reverse-engineered under a filing deadline.
Two things make those drafts fit defense work specifically. Task codes are applied per client, so a matter for one carrier picks up that carrier's UTBMS set automatically while a matter for another picks up its own. And outside counsel guidelines can be ingested, so the narrative is written to comply from the start: no bundled tasks, no clerical phrasing, the level of description the guidelines ask for. The entries that reach the reviewer are specific and correctly coded, and that's what survives review.
Litigation time tracking has a rhythm problem
Litigation work comes in bursts: a deposition day, a document review sprint before a production deadline, a motion push, then a trial week that swallows everything. Litigation time tracking has always struggled with that shape, because the busiest stretches are the ones nobody has a spare hand to log.
For the desk-bound stretches, screen capture is a clean fit. Document review, drafting, research, and email all happen on the screen, so they become entries without anyone touching a timer. Calls land as entries too: Ajax captures Zoom Phone, Microsoft Teams, RingCentral, Dialpad, VXT, GoTo Connect, and Intermedia Unite, and it reads Outlook and Gmail alongside Outlook, Google, and MyCase calendars for the meetings around them.
Trial weeks are where honesty matters. When you are on your feet in a courtroom, away from any computer, screen capture sees nothing, because there is nothing on a screen to read. That hour comes from the calendar entry for the hearing and the context around it, and any defense firm weighing a passive tool should hear that limit plainly. The prep, the travel, the exhibit work, and the post-hearing memo happen on the screen or the calendar and get captured; the stand-up courtroom hour stays a calendar-and-context estimate you confirm, the same as it is today.
What it looks like at two defense firms
Two firms running Ajax do exactly this kind of work. Doyle & Seelbach and Kamykowski & Taylor are both defense litigation shops billing under carrier guidelines and coded invoices. Their write-ups walk through what changed once entries started arriving contemporaneously instead of getting reconstructed at the end of the week, in a practice where the reconstructed version is the one that tends to get written down.
FAQ
Does Ajax support UTBMS codes and LEDES billing?
Yes. UTBMS task codes are applied per client, so each matter carries the code set its carrier requires, and the coded entries flow into your billing system to be invoiced in LEDES format. Custom and firm-specific codes are configured the same way.
Can Ajax follow different carrier guidelines for different clients?
Yes. Rules, task codes, and narrative style are set per client, so one carrier's outside counsel guidelines apply on its matters while a different carrier's apply on its own. Each client's drafts are written to that client's requirements from the first pass.
Does it work during trial weeks?
Partly, and it's worth being precise. Desk work during a trial week (prep, research, drafting, email, and calls) is captured from the screen and through the phone and calendar integrations. The hours spent standing in a courtroom away from a computer aren't captured by screen reading; that time comes from your calendar and the surrounding context, as it does now. Either way, nothing gets billed until you've reviewed it.
How does this reduce write-downs?
By making entries specific and guideline-compliant before they are ever submitted. Vague narratives, block-billed lines, and miscoded time are what get flagged in bill review, so producing detailed, correctly coded entries from the actual work leaves a reviewer less to reduce. It doesn't guarantee full payment, and a lawyer still reviews every entry, but it starts each invoice from a stronger position.
Bring a day of carrier work to a demo and watch it come back as coded, guideline-ready entries.
