Details of request “Purchased "repossesed" proeprties

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
1956882  sent  2016-10-10 19:58:06 +0100  waiting_response  2016-10-10 19:58:06 +0100  waiting_response  outgoing  
1957165  response  2016-10-11 09:14:37 +0100        incoming  
1964365  response  2016-10-17 12:24:37 +0100    2016-10-19 19:36:31 +0100  partially_successful  incoming  
1969119  status_update  2016-10-19 19:36:31 +0100  partially_successful  2016-10-19 19:36:31 +0100  partially_successful   
1969127  followup_sent  2016-10-19 19:55:24 +0100        outgoing  
1969244  response  2016-10-20 08:56:11 +0100        incoming  
1983459  response  2016-11-03 11:10:55 +0000    2016-11-07 18:21:26 +0000  partially_successful  incoming  
1987591  status_update  2016-11-07 18:21:26 +0000  partially_successful  2016-11-07 18:21:26 +0000  partially_successful   
1987599  followup_sent  2016-11-07 18:36:09 +0000        outgoing  
2198664  overdue  2016-11-08 00:00:00 +0000         
1988151  response  2016-11-08 10:54:07 +0000    2016-11-19 09:54:59 +0000  waiting_response  incoming  
2002045  status_update  2016-11-19 09:54:58 +0000  waiting_response  2016-11-19 09:54:59 +0000  waiting_response   
2016403  response  2016-12-02 08:35:49 +0000    2016-12-09 20:25:41 +0000  waiting_response  incoming  
2254935  very_overdue  2016-12-07 00:00:00 +0000         
2024867  followup_sent  2016-12-09 20:25:12 +0000        outgoing  
2024868  status_update  2016-12-09 20:25:41 +0000  waiting_response  2016-12-09 20:25:41 +0000  waiting_response   
2025729  response  2016-12-12 09:10:32 +0000    2017-01-07 21:13:32 +0000  waiting_response  incoming  
2049899  status_update  2017-01-07 21:13:32 +0000  waiting_response  2017-01-07 21:13:32 +0000  waiting_response   
2213307  response  2017-02-09 11:47:54 +0000    2017-02-23 09:50:46 +0000  partially_successful  incoming  
2273826  status_update  2017-02-23 09:50:46 +0000  partially_successful  2017-02-23 09:50:46 +0000  partially_successful   
2273848  followup_sent  2017-02-23 10:01:50 +0000  internal_review  2017-02-23 10:01:50 +0000  internal_review  outgoing  
2278382  response  2017-02-27 13:05:05 +0000        incoming  
2320290  response  2017-04-03 17:40:32 +0100    2017-04-06 15:58:57 +0100  partially_successful  incoming  
2324194  status_update  2017-04-06 15:58:57 +0100  partially_successful  2017-04-06 15:58:57 +0100  partially_successful   
2626048  response  2017-11-10 19:02:00 +0000    2017-12-09 20:47:33 +0000  waiting_clarification  incoming  
2664314  status_update  2017-12-09 17:37:33 +0000  partially_successful  2017-12-09 17:37:33 +0000  partially_successful   
2664355  status_update  2017-12-09 20:46:42 +0000  waiting_response  2017-12-09 20:46:43 +0000  waiting_response   
2664356  status_update  2017-12-09 20:47:33 +0000  waiting_clarification  2017-12-09 20:47:33 +0000  waiting_clarification   
2664480  status_update  2017-12-10 11:08:01 +0000  waiting_clarification  2017-12-10 11:08:01 +0000  waiting_clarification   
2664816  edit  2017-12-10 21:33:47 +0000         
2665912  followup_sent  2017-12-11 13:47:29 +0000  waiting_response  2017-12-11 13:47:30 +0000  waiting_response  outgoing  
2666299  response  2017-12-11 16:37:47 +0000        incoming  
2667337  response  2017-12-12 10:42:39 +0000    2018-01-06 09:06:44 +0000  waiting_response  incoming  
2690870  status_update  2018-01-06 09:06:44 +0000  waiting_response  2018-01-06 09:06:44 +0000  waiting_response   
2700079  overdue  2018-01-13 00:00:00 +0000         
2700574  followup_sent  2018-01-13 15:46:35 +0000  internal_review  2018-01-13 15:46:35 +0000  internal_review  outgoing  
2722077  response  2018-01-29 10:34:02 +0000    2018-02-01 12:00:49 +0000  waiting_response  incoming  
2728308  status_update  2018-02-01 12:00:48 +0000  waiting_response  2018-02-01 12:00:49 +0000  waiting_response   
2728333  followup_sent  2018-02-01 12:12:13 +0000        outgoing  
2741729  very_overdue  2018-02-10 00:00:00 +0000         
2748405  response  2018-02-15 17:11:38 +0000        incoming  

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.