Details of request “Freedom of Information request from all meetings/correspondence with Denby Holdings ref Poole Pottery business in Poole

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 details created_at described_state calculated_state last_described_at link
2599185  sent    2017-10-24 19:06:29 +0100  waiting_response  waiting_response  2017-10-24 19:06:30 +0100  outgoing  
2640864  overdue    2017-11-22 00:00:00 +0000         
2642685  response    2017-11-23 10:18:47 +0000    waiting_response  2017-11-27 11:13:20 +0000  incoming  
2646595  status_update    2017-11-27 11:13:20 +0000  waiting_response  waiting_response  2017-11-27 11:13:20 +0000   
2652698  response    2017-12-01 10:01:08 +0000    partially_successful  2017-12-19 15:33:04 +0000  incoming  
2676525  status_update  described_state  2017-12-19 15:33:04 +0000  partially_successful  partially_successful  2017-12-19 15:33:04 +0000   
2676532  followup_sent    2017-12-19 15:36:13 +0000        outgoing  
2706583  response    2018-01-17 12:15:15 +0000    partially_successful  2022-03-26 21:21:03 +0000  incoming  
2941360  edit metadata  allow_new_responses_from  2018-04-18 03:45:18 +0100         
2941361  edit metadata  allow_new_responses_from  2018-04-18 03:45:18 +0100         
2941362  edit metadata  allow_new_responses_from  2018-04-18 03:45:18 +0100         
2941363  edit metadata  allow_new_responses_from  2018-04-18 03:45:18 +0100         
2941364  edit metadata  allow_new_responses_from  2018-04-18 03:45:18 +0100         
2941365  edit metadata  allow_new_responses_from  2018-04-18 03:45:18 +0100         
2941366  edit metadata  allow_new_responses_from  2018-04-18 03:45:18 +0100         
2941367  edit metadata  allow_new_responses_from  2018-04-18 03:45:18 +0100         
3912898  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912899  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912900  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912901  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912902  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912903  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912904  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912905  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912906  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912907  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912908  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912909  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912910  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912911  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912912  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
3912913  edit metadata  allow_new_responses_from  2019-01-18 03:46:35 +0000         
11490816  status_update    2022-03-26 21:21:03 +0000  partially_successful  partially_successful  2022-03-26 21:21:03 +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.