Details of request “Disclosure of Data regrading turnover, exit numbers by reason and more...

Event history

This table shows the technical details of the internal events that happened to this request on WhatDoTheyKnow. 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 WhatDoTheyKnow. 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
2617448  sent  2017-11-06 17:38:38 +0000  waiting_response  2017-11-06 17:38:38 +0000  waiting_response  outgoing  
2658449  overdue  2017-12-06 00:00:00 +0000         
2678391  response  2017-12-20 22:25:45 +0000    2018-03-14 07:17:19 +0000  partially_successful  incoming  
2817507  status_update  2018-03-14 07:17:19 +0000  partially_successful  2018-03-14 07:17:19 +0000  partially_successful   
3191712  edit  2018-06-15 03:45:12 +0100         
3191713  edit  2018-06-15 03:45:12 +0100         
3191714  edit  2018-06-15 03:45:12 +0100         
3191715  edit  2018-06-15 03:45:12 +0100         
4236614  edit  2019-03-15 03:46:20 +0000         
4236615  edit  2019-03-15 03:46:20 +0000         
4236616  edit  2019-03-15 03:46:20 +0000         
4236617  edit  2019-03-15 03:46:20 +0000         
4236618  edit  2019-03-15 03:46:20 +0000         
4236619  edit  2019-03-15 03:46:20 +0000         
4236620  edit  2019-03-15 03:46:20 +0000         
4236621  edit  2019-03-15 03:46:20 +0000         

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