Details of request “No Anticipatory Measures for Disabled Users to fairly access Cafcass Complaints Procedure

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.

Be careful! 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
3837317  sent    2018-12-27 21:07:37 +0000  waiting_response  waiting_response  2018-12-27 21:07:37 +0000  outgoing  
3852928  response    2019-01-04 11:23:41 +0000    waiting_response  2019-01-08 02:46:37 +0000  incoming  
3860242  status_update    2019-01-08 02:46:37 +0000  waiting_response  waiting_response  2019-01-08 02:46:37 +0000   
3860244  status_update    2019-01-08 02:48:24 +0000  waiting_response  waiting_response  2019-01-08 02:48:24 +0000   
3860245  status_update    2019-01-08 02:54:40 +0000  waiting_response  waiting_response  2019-01-08 02:54:41 +0000   
3860247  status_update    2019-01-08 02:55:17 +0000  waiting_response  waiting_response  2019-01-08 02:55:17 +0000   
3890129  response    2019-01-14 12:24:45 +0000    partially_successful  2019-01-16 03:13:40 +0000  incoming  
3896297  status_update  described_state  2019-01-16 03:13:40 +0000  partially_successful  partially_successful  2019-01-16 03:13:40 +0000   
4401147  edit metadata  allow_new_responses_from  2019-04-17 03:45:45 +0100         
4401148  edit metadata  allow_new_responses_from  2019-04-17 03:45:45 +0100         
4401149  edit metadata  allow_new_responses_from  2019-04-17 03:45:46 +0100         
4401150  edit metadata  allow_new_responses_from  2019-04-17 03:45:46 +0100         
4401151  edit metadata  allow_new_responses_from  2019-04-17 03:45:46 +0100         
4401152  edit metadata  allow_new_responses_from  2019-04-17 03:45:46 +0100         
4401153  edit metadata  allow_new_responses_from  2019-04-17 03:45:46 +0100         
4401154  edit metadata  allow_new_responses_from  2019-04-17 03:45:46 +0100         
6057077  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057078  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057079  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057080  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057081  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057082  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057083  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057084  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057085  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057086  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057087  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057088  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057089  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057090  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057091  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +0000         
6057092  edit metadata  allow_new_responses_from  2020-01-17 03:49:38 +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.