Details of request “Arrest Reports & Indictments

Event history

This table shows the technical details of the internal events that happened to this request on OPRAmachine. This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Be careful! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on OPRAmachine. How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand FOI law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type details created_at described_state calculated_state last_described_at link
1617505  sent    2026-05-21 09:30:02 -0400  waiting_response  waiting_response  2026-05-21 09:30:02 -0400  outgoing  
1618310  response    2026-05-22 12:46:12 -0400    waiting_response  2026-05-27 08:58:20 -0400  incoming  
1621383  status_update    2026-05-27 08:58:20 -0400  waiting_response  waiting_response  2026-05-27 08:58:20 -0400   
1624672  overdue    2026-06-02 00:00:00 -0400         
1637274  very_overdue    2026-06-19 00:00:00 -0400         
1640210  response    2026-06-25 16:16:39 -0400        incoming  
1640226  response    2026-06-25 17:22:39 -0400        incoming  
1640227  response    2026-06-25 17:23:20 -0400        incoming  
1640229  response    2026-06-25 17:36:51 -0400        incoming  
1640231  response    2026-06-25 17:39:13 -0400        incoming  
1640237  response    2026-06-25 18:27:47 -0400        incoming  
1640239  response    2026-06-25 18:45:06 -0400        incoming  
1640240  response    2026-06-25 18:46:33 -0400        incoming  
1640844  response    2026-06-26 12:57:53 -0400        incoming  
1640847  response    2026-06-26 12:59:58 -0400        incoming  
1640848  response    2026-06-26 13:01:59 -0400        incoming  
1640886  response    2026-06-26 16:14:12 -0400        incoming  
1642677  response    2026-06-29 16:39:48 -0400        incoming  
1642680  response    2026-06-29 17:09:47 -0400        incoming  
1642681  response    2026-06-29 17:12:16 -0400        incoming  
1642982  response    2026-06-30 18:16:33 -0400        incoming  
1642983  response    2026-06-30 18:17:56 -0400        incoming  
1642984  response    2026-06-30 18:19:41 -0400        incoming  
1644128  response    2026-07-02 15:42:52 -0400        incoming  
1644129  response    2026-07-02 15:58:22 -0400        incoming  
1645168  response    2026-07-05 14:15:58 -0400        incoming  
1645169  response    2026-07-05 14:44:42 -0400        incoming  
1645866  response    2026-07-06 18:18:02 -0400        incoming  
1645867  response    2026-07-06 18:29:20 -0400        incoming  
1645869  response    2026-07-06 18:58:22 -0400        incoming  
1646364  response    2026-07-07 16:38:40 -0400        incoming  
1646372  response    2026-07-07 17:02:44 -0400        incoming  
1646373  response    2026-07-07 17:32:08 -0400    successful  2026-07-13 11:45:21 -0400  incoming  
1650675  status_update  described_state  2026-07-13 11:45:21 -0400  successful  successful  2026-07-13 11:45:21 -0400   

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by OPRAmachine for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.