Details of request “Policy on email management and automated deletion of emails

Event history

This table shows the technical details of the internal events that happened to this request on 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.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on 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 created_at described_state last_described_at calculated_state link
26343  sent  2016-12-15 10:52:10 +0100  waiting_response  2016-12-15 10:52:10 +0100  waiting_response  outgoing  
26359  response  2016-12-15 11:55:37 +0100    2016-12-15 11:59:28 +0100  waiting_response  incoming  
26361  status_update  2016-12-15 11:59:28 +0100  waiting_response  2016-12-15 11:59:28 +0100  waiting_response   
26374  response  2016-12-15 16:46:00 +0100    2016-12-28 11:45:48 +0100  waiting_response  incoming  
26668  status_update  2016-12-28 11:45:48 +0100  waiting_response  2016-12-28 11:45:48 +0100  waiting_response   
26931  response  2017-01-12 16:43:12 +0100    2017-01-13 14:41:59 +0100  successful  incoming  
26958  status_update  2017-01-13 14:41:59 +0100  successful  2017-01-13 14:41:59 +0100  successful   

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 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.