Details of request “C2 and C3 land use classification for Knowle development

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
2013657  sent  2016-11-29 20:31:29 +0000  waiting_response  2016-11-29 20:31:29 +0000  waiting_response  outgoing  
2014268  response  2016-11-30 13:25:06 +0000    2016-11-30 21:19:04 +0000  waiting_response  incoming  
2014742  status_update  2016-11-30 21:19:04 +0000  waiting_response  2016-11-30 21:19:04 +0000  waiting_response   
2039631  response  2016-12-23 08:52:33 +0000        incoming  
2046721  response  2017-01-04 15:36:29 +0000    2017-01-21 23:54:03 +0000  successful  incoming  
2067103  status_update  2017-01-21 23:54:03 +0000  successful  2017-01-21 23:54:03 +0000  successful   
2067105  followup_sent  2017-01-22 00:01:23 +0000        outgoing  
2067971  response  2017-01-23 11:23:53 +0000    2017-01-23 23:13:31 +0000  waiting_clarification  incoming  
2069055  followup_sent  2017-01-23 23:13:18 +0000        outgoing  
2069056  status_update  2017-01-23 23:13:31 +0000  waiting_clarification  2017-01-23 23:13:31 +0000  waiting_clarification   
2069466  response  2017-01-24 10:50:24 +0000        incoming  
2070472  followup_sent  2017-01-24 21:32:08 +0000  waiting_response  2017-01-24 21:32:08 +0000  waiting_response  outgoing  
2070473  status_update  2017-01-24 21:33:11 +0000  successful  2017-01-24 21:33:12 +0000  successful   
2076263  followup_sent  2017-01-29 22:49:35 +0000        outgoing  
2076264  status_update  2017-01-29 22:50:03 +0000  waiting_response  2017-01-29 22:50:03 +0000  waiting_response   
2076265  response  2017-01-29 22:50:05 +0000    2017-01-29 22:50:33 +0000  waiting_response  incoming  
2076266  status_update  2017-01-29 22:50:32 +0000  waiting_response  2017-01-29 22:50:33 +0000  waiting_response   
2407373  overdue  2017-02-22 00:00:00 +0000         
2273640  followup_sent  2017-02-22 23:45:55 +0000  internal_review  2017-02-22 23:45:55 +0000  internal_review  outgoing  
2273722  response  2017-02-23 08:12:53 +0000    2017-03-11 18:56:59 +0000  successful  incoming  
2294443  followup_sent  2017-03-11 18:56:51 +0000        outgoing  
2294444  status_update  2017-03-11 18:56:59 +0000  successful  2017-03-11 18:56:59 +0000  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 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.