Why a request comes back
A company rejects a request when it sends the request back unanswered. The legal process may be wrong or incomplete, or the request may duplicate one the company already received. Each rejection costs the requester time and adds work to the company’s queue.
Jane Man, who works on product at Kodex, took up the question on the report’s webinar. She started with the agents who send requests: “there’s a lot of education that we can be doing for law enforcement agents to help them understand what’s required in order to get a complete or prompt response.”
Four things a company controls
Jane named four changes that sit inside the company’s own process:
- Education. Tell law enforcement agents what a complete request needs, so the first request they send is one the company can answer.
- Guidelines. Publish them and keep them plain. Jane’s words were “being really clear, creating good guidelines.”
- Requirements at intake. In a structured system, she said, “you’re enforcing some of those requirements right in the intake itself.”
- Acknowledgment. A short note that a request arrived keeps the requester from sending a new one in case the first didn’t go through. “That’s gonna get rid of some of your duplicates,” Jane said.
Checking a request before a person does
Jane closed on automation. Intake rules catch a missing requirement when a request arrives, and she sees room for the industry to go further.
“I think there’s really an opportunity for the industry as a whole to start using more automation to check requests before a person has to.”
Jane Man, Product, Kodex
In her picture, software makes the first check, and a person starts with a request that has already been looked over.
Where to read more
The Kodex guide to law enforcement data request management covers the wider process, and the webinar replay has Jane’s full answer. The requester’s side of the same exchange is in What should a law enforcement data request include? The record a team keeps of each request is in What should an audit trail for law enforcement requests include?
In Jane’s words
There’s a lot of education we can be doing for law enforcement agents to help them understand what’s required to get a complete or prompt response.
That means being clear and creating good guidelines. If you’re using a structured system, maybe you’re enforcing some of those requirements right in the intake itself. Then make sure you follow up on a request. Simple things like saying, “Hey, we got it,” so the requester doesn’t submit a new one thinking it didn’t go through. That’s going to get rid of some of your duplicates.
Looking ahead, and I’m sorry, this is the product nerd in me, I think there’s an opportunity for the industry as a whole to start using more automation to check requests before a person has to.
Edited for length and clarity. From the Kodex Standard Report webinar, November 17, 2026