What the survey asked
For the Kodex Standard Report, Kodex surveyed legal response teams. One question asked what they wish law enforcement investigators knew before sending a request. Ayush Dagar, a solutions engineer at Kodex, reported the answers on the report’s webinar.
The answers work as a checklist for an investigator and as a brief for a company deciding how to set up its intake. Ayush described three of them.
Three things companies ask for
- A complete, accurate request. The top response asked for “complete, accurate requests, things that are legally valid.” The company needs the metadata and “all the various identifiers” to produce the data and find it in its own systems.
- A read of the guidelines. A common response asked requesters to read “the guidelines that the company provides and publicly publishes.”
- The right track. Submit through the right process, labeled clearly, and keep the emergency label for “genuine emergencies.”
Why Ayush singles out the right track
Of the three, Ayush picked the right track to highlight. It helps both sides. A requester gets a response more reliably and more quickly, and a company with its different rails set up can plan how to automate and answer more efficiently.
“I would highlight that one, making sure the requests go on the right track, because it allows for efficiency on both sides.”
Ayush Dagar, Solutions Engineer, Kodex
The label matters most on emergencies. Ayush asked that the emergencies submitted are real ones, and the glossary entry for an emergency disclosure request explains the term.
For investigators and for companies
An investigator can run the list before sending: the request is complete, the identifiers are in it, the company’s guidelines have been read and the track is the right one. A company can use the same list to decide what its guidelines and its intake should spell out.
The Kodex guide to law enforcement data request management covers verifying requesters, tracking deadlines, responding securely and cost recovery. The webinar replay has Ayush’s whole answer. For what a company can do about requests it sends back, see How can companies reduce rejected law enforcement requests? For the record each request leaves behind, see What should an audit trail for law enforcement requests include?
In Ayush’s words
The top response was that companies want requesters to give them complete, accurate requests: things that are legally valid and have all the information inside, all the metadata, all the various identifiers the company needs to produce the data and find it internally in their own systems.
A common response after that was a desire for requesters to read the guidelines that the company provides and publicly publishes, and to choose the right track. That means submitting through the right process, labeled clearly, and making sure that the emergencies being submitted are genuine emergencies.
I would highlight that one, making sure requests go on the right track, because it allows for efficiency on both sides. Requesters get responses more reliably and more quickly, and once companies have these different rails set up, they can think about how to automate and be more efficient in how they respond to these various requests.
Edited for length and clarity. From the Kodex Standard Report webinar, November 17, 2026