The gap Jesse saw in August
Regulation (EU) 2023/1543 has applied since August 18, 2026. The Kodex EU e-Evidence Prep Talk took place on August 6, twelve days earlier. Jesse Goodman, VP Product Delivery at Kodex, was asked what a team needs in place on day one, and what follows is what he said then, before the regulation applied.
Jesse said teams were missing “the technical systems and workflow and operating procedures.” He framed the question around “what happens when you actually receive a request,” and gave the middle of the night on a weekend as the test. He said it is the most important thing Kodex discusses with its customers.
What the first hours need
Jesse went through the request’s path in order. A request arrives and the team triages it. Someone determines whether it is an emergency. The team then needs systems and tools to notify an accountable person who is on call, so that person can “deal with it right away.”
The time allowed is short. A production order under the regulation gives a provider 10 days, and 8 hours in an emergency, as the Kodex e-Evidence guide sets out. Jesse said the windows are “really different from what we’ve seen in the past” across the EU, where an enforceable deadline now applies.
“These eight-hour windows are tight.”
Jesse Goodman, VP Product Delivery, Kodex
Work done before the page arrives
Jesse’s answer is that the work happens before the call comes. He named four things a team can have ready:
- Triage. The team sorts the request into the right queue.
- Validation. The team checks that the request is what it says it is.
- Signature checks. The systems check the signature of the request.
- Automation. Everything that can be done upfront is done upfront.
The aim is that a person paged in the middle of the night already has a place to look at the request. From there they can see whether they have responsive data, and whether the request is legally appropriate, including whether enforcing state approval is required.
Where to read more
The Kodex guide to EU e-Evidence covers who is in scope and the deadlines, and a European Production Order is defined in the glossary. The Prep Talk replay has the whole session.
For the clock itself, see How long do you have to answer an EU e-Evidence order? For why 10 days is hard to meet, see Why is the 10-day EU e-Evidence deadline hard to meet?
In Jesse’s words
One thing teams are missing as they get ready for day one is the technical systems, workflow and operating procedures. The most important thing to me is what happens when you actually receive a request. Say it’s the middle of the night, on a weekend. What systems and processes do you have in place to deal with that? It’s the most important thing we’re talking to our customers about.
If you dig a little deeper, a request comes in. Can you triage it in the right way? Can you determine whether it’s an emergency? Do you have systems and tools to notify an accountable person who’s on call, so they can receive the request and deal with it right away?
These eight-hour windows are tight. It’s really different from what we’ve seen in the past, especially across the EU, where there is an enforceable deadline, an SLA, that you’re expected to respond to. So you need to be able to triage the request and validate it, with systems in place to check its signature. And as much as possible, automate everything that can be done upfront. Then if somebody gets a page in the middle of the night, they already have a place to look at the request. They can see whether they have responsive data, whether it’s legally appropriate, and whether enforcing state approval is required. With all of that upfront work ready, you can respond within that tight window.
Edited for length and clarity. From the EU e-Evidence Prep Talk, August 6, 2026