Details of request “CAMHS transformation money / plans

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
2362497  sent  2017-05-12 08:20:47 +0100  waiting_response  2017-05-12 08:20:47 +0100  waiting_response  outgoing  
2366903  response  2017-05-16 15:12:58 +0100    2017-05-16 17:44:59 +0100  waiting_response  incoming  
2367188  status_update  2017-05-16 17:44:59 +0100  waiting_response  2017-05-16 17:44:59 +0100  waiting_response   
2367191  status_update  2017-05-16 17:46:14 +0100  waiting_response  2017-05-16 17:46:14 +0100  waiting_response   
2392974  response  2017-06-09 16:53:46 +0100    2017-07-07 11:11:26 +0100  successful  incoming  
3481856  overdue  2017-06-13 00:00:00 +0100         
2444048  status_update  2017-07-07 11:11:25 +0100  successful  2017-07-07 11:11:26 +0100  successful   
3481861  very_overdue  2017-07-11 00:00:00 +0100         
3443655  destroy_incoming  2018-08-22 12:30:42 +0100         
3443656  destroy_incoming  2018-08-22 12:30:42 +0100         
3443657  destroy_incoming  2018-08-22 12:30:43 +0100         
3443658  destroy_incoming  2018-08-22 12:30:43 +0100         
3443659  destroy_incoming  2018-08-22 12:30:43 +0100         
3443660  destroy_incoming  2018-08-22 12:30:43 +0100         
3443661  destroy_incoming  2018-08-22 12:30:43 +0100         
3443662  destroy_incoming  2018-08-22 12:30:43 +0100         
3443663  destroy_incoming  2018-08-22 12:30:43 +0100         
3443664  destroy_incoming  2018-08-22 12:30:44 +0100         
3443666  destroy_incoming  2018-08-22 12:30:44 +0100         
3443667  destroy_incoming  2018-08-22 12:30:44 +0100         
3443668  destroy_incoming  2018-08-22 12:30:44 +0100         
3443669  destroy_incoming  2018-08-22 12:30:44 +0100         
3443670  destroy_incoming  2018-08-22 12:30:44 +0100         
3443671  destroy_incoming  2018-08-22 12:30:44 +0100         
3456681  response  2018-08-27 20:57:37 +0100    2018-09-03 09:13:15 +0100  successful  incoming  
3481118  status_update  2018-09-02 12:53:16 +0100  waiting_response  2018-09-02 12:53:16 +0100  waiting_response   
3482090  status_update  2018-09-03 09:13:15 +0100  successful  2018-09-03 09:13:15 +0100  successful   
3493309  response  2018-09-05 23:22:02 +0100    2018-09-10 09:42:17 +0100  partially_successful  incoming  
3506290  status_update  2018-09-10 09:42:17 +0100  partially_successful  2018-09-10 09:42:17 +0100  partially_successful   
3512196  response  2018-09-12 04:36:54 +0100        incoming  
3512197  response  2018-09-12 04:52:20 +0100        incoming  
3523355  response  2018-09-14 13:30:12 +0100        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.