Details of request “Anti competitive practices in damp and timber surveys

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
1115652  sent  2014-07-27 09:51:29 +0100  waiting_response  2014-07-27 09:51:29 +0100  waiting_response  outgoing  
1116373  response  2014-07-28 12:09:27 +0100    2014-08-08 08:52:33 +0100  waiting_response  incoming  
1128004  status_update  2014-08-08 08:52:33 +0100  waiting_response  2014-08-08 08:52:33 +0100  waiting_response   
1144265  response  2014-08-26 16:50:51 +0100        incoming  
1147974  followup_sent  2014-08-30 10:16:27 +0100  internal_review  2014-08-30 10:16:27 +0100  internal_review  outgoing  
1148950  response  2014-09-01 12:40:52 +0100    2014-09-05 07:39:38 +0100  partially_successful  incoming  
1152813  status_update  2014-09-05 07:39:38 +0100  partially_successful  2014-09-05 07:39:38 +0100  partially_successful   
1172343  response  2014-09-25 15:47:17 +0100    2015-01-15 23:07:38 +0000  partially_successful  incoming  
1258808  comment  2014-12-30 11:32:44 +0000         
1259223  comment  2014-12-31 07:53:21 +0000         
1265194  comment  2015-01-07 15:39:21 +0000         
1265448  comment  2015-01-07 20:20:15 +0000  attention_requested       
1272550  edit_comment  2015-01-15 14:23:30 +0000         
1272883  comment  2015-01-15 16:30:25 +0000         
1272943  edit_comment  2015-01-15 17:15:39 +0000         
1273045  comment  2015-01-15 21:00:28 +0000         
1273096  edit_comment  2015-01-15 23:04:27 +0000         
1273097  edit_comment  2015-01-15 23:04:31 +0000         
1273098  edit  2015-01-15 23:04:48 +0000         
1273101  comment  2015-01-15 23:06:50 +0000         
1273102  edit  2015-01-15 23:06:57 +0000         
1273104  edit  2015-01-15 23:07:38 +0000  partially_successful  2015-01-15 23:07:38 +0000  partially_successful   
1274724  edit_outgoing  2015-01-18 22:42:15 +0000        outgoing  
1274725  edit_incoming  2015-01-18 22:43:04 +0000        incoming  
1274726  edit_outgoing  2015-01-18 22:45:54 +0000        outgoing  
1274728  edit_incoming  2015-01-18 22:46:32 +0000        incoming  
1274729  edit_comment  2015-01-18 22:47:28 +0000         
1274730  edit_comment  2015-01-18 22:47:30 +0000         
1274731  edit_comment  2015-01-18 22:47:34 +0000         
1274732  edit_comment  2015-01-18 22:47:38 +0000         
1274733  edit  2015-01-18 22:48:05 +0000         
1274734  comment  2015-01-18 22:48:50 +0000         
1274735  edit  2015-01-18 22:48:59 +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.