Details of request “Register of Academy Trusts/Sponsors

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
1013950  sent    2014-04-07 02:38:11 +0100  waiting_response  waiting_response  2014-04-07 02:38:11 +0100  outgoing  
1014928  response    2014-04-07 15:00:17 +0100    waiting_response  2014-04-11 13:16:13 +0100  incoming  
1019780  status_update    2014-04-11 13:16:12 +0100  waiting_response  waiting_response  2014-04-11 13:16:13 +0100   
1030223  response    2014-04-24 14:10:26 +0100    waiting_response  2014-04-24 16:58:47 +0100  incoming  
1030644  status_update    2014-04-24 16:58:47 +0100  waiting_response  waiting_response  2014-04-24 16:58:47 +0100   
1030646  followup_sent    2014-04-24 16:59:22 +0100        outgoing  
2154748  overdue    2014-05-09 00:00:00 +0100         
1053893  response    2014-05-19 10:28:15 +0100    waiting_response  2014-05-23 07:46:39 +0100  incoming  
1059850  status_update    2014-05-23 07:46:39 +0100  waiting_response  waiting_response  2014-05-23 07:46:39 +0100   
1067478  followup_sent    2014-05-31 07:55:32 +0100        outgoing  
1070489  response    2014-06-03 16:59:39 +0100    rejected  2014-06-03 17:13:37 +0100  incoming  
1070508  status_update  described_state  2014-06-03 17:13:37 +0100  rejected  rejected  2014-06-03 17:13:37 +0100   
1072925  followup_sent    2014-06-05 16:50:32 +0100        outgoing  
1073329  response    2014-06-06 10:13:00 +0100    rejected  2014-06-06 12:06:41 +0100  incoming  
1073523  status_update    2014-06-06 12:06:41 +0100  rejected  rejected  2014-06-06 12:06:41 +0100   
1077346  response    2014-06-11 09:40:42 +0100    rejected  2014-06-22 23:35:18 +0100  incoming  
1086821  status_update    2014-06-22 23:35:18 +0100  rejected  rejected  2014-06-22 23:35:18 +0100   
1086824  followup_sent    2014-06-22 23:44:58 +0100  internal_review  internal_review  2014-06-22 23:44:58 +0100  outgoing  
1086825  status_update    2014-06-22 23:46:00 +0100  internal_review  internal_review  2014-06-22 23:46:00 +0100   
1087391  response    2014-06-23 13:01:59 +0100    internal_review  2014-06-25 12:34:20 +0100  incoming  
1089702  status_update    2014-06-25 12:34:19 +0100  internal_review  internal_review  2014-06-25 12:34:20 +0100   
1110140  followup_sent    2014-07-21 07:10:10 +0100  internal_review  internal_review  2014-07-21 07:10:10 +0100  outgoing  
1110766  response    2014-07-21 14:28:34 +0100        incoming  
1112720  response    2014-07-23 11:57:19 +0100        incoming  
1114086  response    2014-07-24 16:34:59 +0100    rejected  2014-08-04 11:34:13 +0100  incoming  
1123176  status_update  described_state  2014-08-04 11:34:13 +0100  rejected  rejected  2014-08-04 11:34:13 +0100   

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.