How fast should a legal team resolve a law enforcement request?

Ike Anude: Are teams actually able to keep up? Request volume is going up, so you might expect response times to get worse. But we’re seeing the opposite. Across all forms of legal process, median resolution time improved from about 21 hours to 12 hours year over year. That’s a 42% reduction in the time to resolution, even as teams are handling more requests. They’re doing more and they’re doing it faster. But here’s the part that really stood out to me. For emergency requests, where every minute matters, median resolution time got even faster, improving from about 55 to 44 minutes. That’s another 22% reduction year over year. Think about what this means. As volume grows, teams aren’t just becoming more efficient. They’re prioritizing requests where time matters most.

Ike Anude, Engineer, Integrations

Kodex Global Keynote · October 27, 2026

A benchmark of 12 hours

The first annual Kodex Standard Report gives legal teams a number to hold their own work against. Across all forms of legal process on the Kodex network, median resolution time improved from about 21 hours to 12 over the year, a 42% reduction.

Ike Anude, an engineer on the Kodex integrations team, presented the finding on stage at the Kodex keynote. Request volume across the network rose 57% in the same year, so “you might expect response times to get worse.” Ike told the room “we’re seeing the opposite,” with resolution time down “even as teams are handling more requests.”

“They’re doing more and they’re doing it faster.”

Ike Anude, Engineer, Integrations, Kodex

How to read the figure

The 12 hours is a median across the Kodex network, which makes it a benchmark for comparison. Deadlines come from the legal process itself. To put the benchmark to use, a team can take two steps:

  • Calculate its own median resolution time across every form of legal process it handles.
  • Set that figure beside 12 hours, and beside the 21 hours the network posted a year earlier.

Volume rose 57% over the same stretch, so the network reached 12 hours while carrying a heavier load than the year before. A team comparing itself to that median is comparing itself to teams that were busier than they had been. The report’s measure is year over year, which gives a team a second reading: whether its own median is falling the way the network’s did.

What sits behind a faster median

Ike credits three changes a company can make itself: structured intake from law enforcement, a notification the moment a request arrives, and internal targets for how quickly a case gets resolved.

Where to read more

The Kodex Standard Report holds the full benchmark, and the keynote has Ike’s presentation of it. For the three changes in his own words, see Why are law enforcement requests resolved faster as volume rises?. Emergency requests have a benchmark of their own, covered in How quickly should you respond to an emergency data request?. The volume figure is on Are law enforcement data requests increasing?

In Ike’s words

Request volume is going up, so you might expect response times to get worse. But we’re seeing the opposite. Across all forms of legal process, median resolution time improved from about 21 hours to 12 hours year over year. That’s a 42% reduction in the time to resolution, even as teams are handling more requests. They’re doing more and they’re doing it faster.

For emergency requests, where every minute matters, median resolution time got even faster, improving from about 55 to 44 minutes. That’s another 22% reduction year over year. As volume grows, teams aren’t just becoming more efficient. They’re prioritizing requests where time matters most.

Edited for length and clarity. From the Kodex Global Keynote, October 27, 2026

More questions

See what
we can do
for you.

Request a demo