What the record holds
Jane Man, who works on product at Kodex, described the record of a request on the report’s webinar. Her definition: “A record is a timeline of every action on a request.” It has five entries:
- Who asked.
- The legal process that was sent.
- Who on the team handled the request.
- What they decided, and why.
- What was sent back, and when.
Jane put the whole list in one instruction: “think of everything that you need as the audit trail.”
Capture it as data
Jane tied the record to a change in how teams work. A team that moves from an inbox to a structured system should decide how each record is processed and how its data is captured, she said, “so you can report on it easily, not just record by record, but in aggregate.”
Reporting in aggregate means answering questions about the whole body of requests. One example Jane gave is how long the team takes on average to respond, and whether that time is improving. A structured system makes this possible, since each entry in the record is captured as data a team can count and compare.
What the record is for
Jane gave the data two uses. The first is the team’s own work. With the data in hand, a team can look at “what went well, what’s working, what’s not working,” along with its average response time.
The second use is public. The same record shows users, regulators and the authorities that the company is doing its part in the response.
“It builds trust with your users, your regulators, the authorities.”
Jane Man, Product, Kodex
Where to read more
The Kodex guide to law enforcement data request management covers the wider process, and the Kodex guide to transparency reporting covers the public side. The webinar replay has Jane’s full answer. To reduce the requests that come back unanswered, see How can companies reduce rejected law enforcement requests? For what a request should carry in the first place, see What should a law enforcement data request include?
In Jane’s words
A record is a timeline of every action on a request: who asked, the legal process that was sent, who on the team handled it, what they decided and why, and what was sent back and when. Think of everything that you need as the audit trail.
As you move from an inbox to a more structured system and think about these records, think about how that’s processed and how the data is captured, so you can report on it easily, not just record by record but in aggregate.
Having that data lets you look at what went well, what’s working, what’s not working, how long you’re taking on average to respond, and whether that’s improving or not. That’s important. Publicly, it also builds trust with your users, your regulators and the authorities, trust that you’re doing what you need to do, your part in the response.
Edited for length and clarity. From the Kodex Standard Report webinar, November 17, 2026