Details of request “Correspondence and documents

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
1474048  sent    2025-11-26 11:26:19 -0500  waiting_response  waiting_response  2025-11-26 11:26:19 -0500  outgoing  
1474072  response    2025-11-26 13:34:28 -0500        incoming  
1474074  response    2025-11-26 13:38:02 -0500    not_held  2025-11-30 08:50:41 -0500  incoming  
1476879  status_update  described_state  2025-11-30 08:50:41 -0500  not_held  not_held  2025-11-30 08:50:41 -0500   
1476886  followup_sent    2025-11-30 09:34:59 -0500  internal_review  internal_review  2025-11-30 09:34:59 -0500  outgoing  
1476887  response    2025-11-30 09:35:05 -0500    error_message  2025-11-30 09:49:40 -0500  incoming  
1476888  status_update  described_state  2025-11-30 09:49:40 -0500  error_message  error_message  2025-11-30 09:49:40 -0500   
1485734  overdue    2025-12-09 00:00:00 -0500         
1485121  response    2025-12-09 08:56:39 -0500        incoming  
1485122  response    2025-12-09 08:56:55 -0500        incoming  
1485185  followup_sent    2025-12-09 13:35:26 -0500        outgoing  
1485186  response    2025-12-09 13:35:33 -0500    waiting_response  2025-12-09 13:37:04 -0500  incoming  
1485188  status_update  described_state  2025-12-09 13:37:04 -0500  waiting_response  waiting_response  2025-12-09 13:37:04 -0500   
1496413  very_overdue    2025-12-27 00:00:00 -0500         
1629850  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629851  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629852  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629853  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629854  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629855  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629856  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629857  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629858  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629859  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629860  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629861  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629862  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -0400         
1629863  edit metadata  allow_new_responses_from  2026-06-11 03:45:12 -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.