Details of request “Bailiff Company Used to Enforce Liability Orders and Warrants for Council Tax Arrears

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
4084621  sent  2019-02-15 22:55:13 +0000  waiting_response  2019-02-15 22:55:13 +0000  waiting_response  outgoing  
4084623  response  2019-02-15 22:55:30 +0000        incoming  
4095454  response  2019-02-18 09:53:49 +0000    2019-02-22 16:44:18 +0000  waiting_response  incoming  
4122153  status_update  2019-02-22 16:44:18 +0000  waiting_response  2019-02-22 16:44:18 +0000  waiting_response   
4245559  overdue  2019-03-16 00:00:00 +0000         
4262817  followup_sent  2019-03-19 20:19:28 +0000        outgoing  
4262818  response  2019-03-19 20:19:42 +0000    2019-03-19 20:21:22 +0000  waiting_response  incoming  
4262819  status_update  2019-03-19 20:21:22 +0000  waiting_response  2019-03-19 20:21:22 +0000  waiting_response   
4269508  response  2019-03-20 11:18:51 +0000    2019-03-20 14:02:40 +0000  successful  incoming  
4269880  status_update  2019-03-20 14:02:40 +0000  successful  2019-03-20 14:02:40 +0000  successful   
4758899  edit  2019-06-21 03:46:02 +0100         
4758900  edit  2019-06-21 03:46:02 +0100         
4758901  edit  2019-06-21 03:46:02 +0100         
4758902  edit  2019-06-21 03:46:02 +0100         
4758903  edit  2019-06-21 03:46:02 +0100         
4758904  edit  2019-06-21 03:46:02 +0100         
4758905  edit  2019-06-21 03:46:02 +0100         
4758906  edit  2019-06-21 03:46:02 +0100         
4758907  edit  2019-06-21 03:46:02 +0100         
4758908  edit  2019-06-21 03:46:02 +0100         
6530899  edit  2020-03-21 03:50:33 +0000         
6530900  edit  2020-03-21 03:50:33 +0000         
6530901  edit  2020-03-21 03:50:33 +0000         
6530902  edit  2020-03-21 03:50:33 +0000         
6530903  edit  2020-03-21 03:50:34 +0000         
6530904  edit  2020-03-21 03:50:34 +0000         
6530905  edit  2020-03-21 03:50:34 +0000         
6530906  edit  2020-03-21 03:50:34 +0000         
6530907  edit  2020-03-21 03:50:34 +0000         
6530908  edit  2020-03-21 03:50:34 +0000         
6530909  edit  2020-03-21 03:50:34 +0000         
6530910  edit  2020-03-21 03:50:34 +0000         
6530911  edit  2020-03-21 03:50:34 +0000         
6530912  edit  2020-03-21 03:50:34 +0000         
6530913  edit  2020-03-21 03:50:34 +0000         
6530914  edit  2020-03-21 03:50:34 +0000         
6530915  edit  2020-03-21 03:50:34 +0000         
6530916  edit  2020-03-21 03:50:34 +0000         
6530917  edit  2020-03-21 03:50:34 +0000         
6530918  edit  2020-03-21 03:50:34 +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.