The benchmark to start from
The Kodex Standard Report gives the median resolution time for an emergency request on the Kodex network as 44 minutes, down from about 55 a year earlier. That is a 22% reduction. Ike Anude presented the figure on stage at the Kodex keynote in October.
The 44 minutes is a median across the network, and it works as a benchmark for your own team. The deadline on any single request comes from its legal process.
Ayush Dagar, a solutions engineer at Kodex, was asked on the report’s webinar how a team should set a response target of its own. He opened by saying his answer was “gonna sound maybe a little too obvious.”
Three steps to a target
Ayush laid out the work in order, and the first step starts with your colleagues.
- Agree on a number. Sit down with your team and settle on “what we think we’re capable of doing in terms of turnaround time.” The number should be realistic, so the conversation covers every consideration your team has internally.
- Track against it. Work inside a system that records your own targets. You then have data as emergency requests come through and can see “how you’re tracking against that internal target.”
- Make sure a person knows. When an emergency request lands, somebody at the company is notified and aware.
Telling someone the moment one lands
Ayush said Kodex clients use “all kinds of different tools, processes” for the third step. He named an integration with a system like PagerDuty or with Slack, and an on-call rotation. Each makes sure somebody at the company hears about an emergency request when it arrives.
He added that there are further steps a team can take to automate parts of the response to an emergency.
“And there’s even other processes, next steps we could take to even try to automate some of the steps in an emergency, so when they do come in early morning on a Sunday, they’re not just sitting in the queue for hours and hours.”
Ayush Dagar, Solutions Engineer, Kodex
Setting your number against the network’s
Once a team has its own target and a record of how it performs, the network’s 44 minutes gives it a point of comparison. For the benchmark itself, see How quickly should you respond to an emergency data request? For the finding across all request types, see How fast should a legal team resolve a law enforcement request?
The webinar replay has Ayush’s whole answer and the rest of the session.
In Ayush’s words
My answer is going to sound a little too obvious, but the first step is to sit down with your team and agree on a target: what we think we’re capable of in terms of turnaround time, with all the considerations you have internally for what a realistic number is. It’s also important to work inside a system that tracks your own targets, so you have data as you work through these emergency requests. You can pull that data and see how you’re tracking against the internal turnaround time you’ve established.
Among our clients, we see all kinds of tools and processes in place to accommodate that. It might be an integration with a system like PagerDuty, an on-call rotation, or an integration with Slack, so that when an emergency request lands, somebody at the company is notified and aware. There are even other processes we could put in place to try to automate some of the steps in an emergency, so when requests come in early on a Sunday morning, they’re not sitting in the queue for hours and hours.
Edited for length and clarity. From the Kodex Standard Report webinar, November 17, 2026