Details of request “Judges and social work malpractice referrals

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
2573008  sent    2017-10-05 18:51:10 +0100  waiting_response  waiting_response  2017-10-05 18:51:10 +0100  outgoing  
2576149  response    2017-10-09 10:52:29 +0100    waiting_response  2017-10-10 15:52:28 +0100  incoming  
2579517  status_update    2017-10-10 15:52:28 +0100  waiting_response  waiting_response  2017-10-10 15:52:28 +0100   
2611942  response    2017-11-02 16:39:19 +0000    waiting_response  2017-11-12 16:12:36 +0000  incoming  
2627322  overdue    2017-11-03 00:00:00 +0000         
2627122  status_update    2017-11-12 16:12:36 +0000  waiting_response  waiting_response  2017-11-12 16:12:36 +0000   
2627477  response    2017-11-13 09:26:28 +0000    successful  2018-01-12 15:33:14 +0000  incoming  
2699604  status_update  described_state  2018-01-12 15:33:14 +0000  successful  successful  2018-01-12 15:33:14 +0000   
2922523  edit metadata  allow_new_responses_from  2018-04-13 03:45:14 +0100         
2922524  edit metadata  allow_new_responses_from  2018-04-13 03:45:14 +0100         
2922525  edit metadata  allow_new_responses_from  2018-04-13 03:45:14 +0100         
2922526  edit metadata  allow_new_responses_from  2018-04-13 03:45:14 +0100         
2922527  edit metadata  allow_new_responses_from  2018-04-13 03:45:14 +0100         
2922528  edit metadata  allow_new_responses_from  2018-04-13 03:45:14 +0100         
2922529  edit metadata  allow_new_responses_from  2018-04-13 03:45:14 +0100         
2922530  edit metadata  allow_new_responses_from  2018-04-13 03:45:14 +0100         
3884947  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884948  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884949  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884950  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884951  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884952  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884953  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884954  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884955  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884956  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884957  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884958  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884959  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884960  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884961  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +0000         
3884962  edit metadata  allow_new_responses_from  2019-01-13 03:46:10 +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.