Details of request “11+ Scores by Sitting Date

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
3794895  sent  2018-12-12 15:29:04 +0000  waiting_response  2018-12-12 15:29:04 +0000  waiting_response  outgoing  
3794943  response  2018-12-12 15:47:35 +0000        incoming  
3877363  response  2019-01-11 12:48:48 +0000    2019-01-11 17:02:24 +0000  partially_successful  incoming  
3877854  status_update  2019-01-11 17:02:24 +0000  partially_successful  2019-01-11 17:02:24 +0000  partially_successful   
3877859  followup_sent  2019-01-11 17:03:33 +0000        outgoing  
3895182  response  2019-01-15 11:54:44 +0000    2019-01-15 12:36:43 +0000  gone_postal  incoming  
3895290  status_update  2019-01-15 12:36:42 +0000  gone_postal  2019-01-15 12:36:43 +0000  gone_postal   
3895297  followup_sent  2019-01-15 12:38:28 +0000        outgoing  
4215752  response  2019-03-11 09:43:16 +0000    2019-03-20 22:44:28 +0000  partially_successful  incoming  
4270578  status_update  2019-03-20 22:44:27 +0000  partially_successful  2019-03-20 22:44:27 +0000  partially_successful   
4270588  followup_sent  2019-03-20 22:46:55 +0000        outgoing  
4296404  response  2019-03-26 15:11:47 +0000        incoming  
4787900  edit  2019-06-27 03:45:21 +0100         
4787901  edit  2019-06-27 03:45:21 +0100         
4787902  edit  2019-06-27 03:45:21 +0100         
4787903  edit  2019-06-27 03:45:21 +0100         
4787904  edit  2019-06-27 03:45:21 +0100         
4787905  edit  2019-06-27 03:45:21 +0100         
4787906  edit  2019-06-27 03:45:22 +0100         
4787907  edit  2019-06-27 03:45:22 +0100         
4787908  edit  2019-06-27 03:45:22 +0100         
4787909  edit  2019-06-27 03:45:22 +0100         
4787910  edit  2019-06-27 03:45:22 +0100         
4787911  edit  2019-06-27 03:45:22 +0100         
6560500  edit  2020-03-27 03:46:00 +0000         
6560501  edit  2020-03-27 03:46:00 +0000         
6560502  edit  2020-03-27 03:46:00 +0000         
6560503  edit  2020-03-27 03:46:00 +0000         
6560504  edit  2020-03-27 03:46:00 +0000         
6560505  edit  2020-03-27 03:46:00 +0000         
6560506  edit  2020-03-27 03:46:00 +0000         
6560507  edit  2020-03-27 03:46:00 +0000         
6560508  edit  2020-03-27 03:46:00 +0000         
6560509  edit  2020-03-27 03:46:00 +0000         
6560510  edit  2020-03-27 03:46:00 +0000         
6560511  edit  2020-03-27 03:46:00 +0000         
6560512  edit  2020-03-27 03:46:00 +0000         
6560513  edit  2020-03-27 03:46:00 +0000         
6560514  edit  2020-03-27 03:46:00 +0000         
6560515  edit  2020-03-27 03:46:00 +0000         
6560516  edit  2020-03-27 03:46:00 +0000         
6560517  edit  2020-03-27 03:46:00 +0000         
6560518  edit  2020-03-27 03:46:00 +0000         
6560519  edit  2020-03-27 03:46:00 +0000         
6560520  edit  2020-03-27 03:46:00 +0000         
6560521  edit  2020-03-27 03:46:00 +0000         
6560522  edit  2020-03-27 03:46:01 +0000         
6560523  edit  2020-03-27 03:46:01 +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.