Details of request “Financial Viabilty Reports For Central Hill Estate

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
1914045  sent    2016-09-05 09:20:23 +0100  waiting_response  waiting_response  2016-09-05 09:20:23 +0100  outgoing  
1914149  response    2016-09-05 10:12:43 +0100    waiting_response  2016-09-09 10:20:11 +0100  incoming  
1919719  status_update    2016-09-09 10:20:11 +0100  waiting_response  waiting_response  2016-09-09 10:20:11 +0100   
1948296  response    2016-10-03 16:04:21 +0100    partially_successful  2016-10-07 15:34:05 +0100  incoming  
2422829  overdue    2016-10-04 00:00:00 +0100         
1954319  status_update  described_state  2016-10-07 15:34:05 +0100  partially_successful  partially_successful  2016-10-07 15:34:05 +0100   
1957215  followup_sent    2016-10-11 09:35:25 +0100  internal_review  internal_review  2016-10-11 09:35:25 +0100  outgoing  
1959085  response    2016-10-12 10:00:10 +0100    internal_review  2016-10-16 10:21:34 +0100  incoming  
1963410  status_update    2016-10-16 10:21:33 +0100  internal_review  internal_review  2016-10-16 10:21:34 +0100   
2414544  very_overdue    2016-11-01 00:00:00 +0000         
2078438  response    2017-01-31 09:28:23 +0000    waiting_response  2017-02-09 12:41:28 +0000  incoming  
2257456  status_update  described_state  2017-02-09 12:41:28 +0000  waiting_response  waiting_response  2017-02-09 12:41:28 +0000   
3184389  edit metadata  allow_new_responses_from  2018-06-13 11:50:34 +0100         
3184430  response    2018-06-13 12:02:35 +0100    successful  2018-07-02 15:02:08 +0100  incoming  
3266730  status_update  described_state  2018-07-02 15:02:07 +0100  successful  successful  2018-07-02 15:02:08 +0100   
4820910  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820911  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820912  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820913  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820914  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820915  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820916  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820917  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820918  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820919  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820920  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820921  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820922  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820923  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         
4820924  edit metadata  allow_new_responses_from  2019-07-03 03:47:31 +0100         

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.