Details of request “Police Constable Thomas Blake 1131

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
1542808  sent    2015-09-30 19:28:15 +0100  waiting_response  waiting_response  2015-09-30 19:28:15 +0100  outgoing  
1542826  response    2015-09-30 19:48:14 +0100    waiting_response  2015-10-01 16:43:44 +0100  incoming  
1542842  status_update  described_state  2015-09-30 20:04:15 +0100  attention_requested  attention_requested  2015-10-01 15:26:42 +0100   
1543952  edit metadata  title  2015-10-01 16:41:46 +0100         
1543956  edit metadata  described_state  2015-10-01 16:43:44 +0100  waiting_response  waiting_response  2015-10-01 16:43:44 +0100   
1572010  response    2015-10-28 15:42:44 +0000    partially_successful  2015-10-28 16:26:06 +0000  incoming  
1572061  comment    2015-10-28 16:09:44 +0000         
1572101  status_update  described_state  2015-10-28 16:26:06 +0000  partially_successful  partially_successful  2015-10-28 16:26:06 +0000   
2178206  overdue    2015-10-29 00:00:00 +0000         
1575317  followup_sent    2015-11-01 17:46:04 +0000        outgoing  
1575509  response    2015-11-02 08:09:13 +0000        incoming  
1575524  followup_sent    2015-11-02 08:27:05 +0000        outgoing  
1575613  response    2015-11-02 09:22:56 +0000    waiting_response  2015-11-06 07:44:00 +0000  incoming  
1575670  followup_sent    2015-11-02 09:39:08 +0000        outgoing  
1580627  status_update  described_state  2015-11-06 07:44:00 +0000  waiting_response  waiting_response  2015-11-06 07:44:00 +0000   
1581549  followup_sent    2015-11-07 07:33:43 +0000        outgoing  
1581766  response    2015-11-07 16:24:05 +0000    partially_successful  2015-12-11 20:42:26 +0000  incoming  
1582025  followup_sent    2015-11-08 17:58:59 +0000        outgoing  
1582026  status_update  described_state  2015-11-08 17:59:06 +0000  partially_successful  partially_successful  2015-11-08 17:59:06 +0000   
2243305  very_overdue    2015-11-26 00:00:00 +0000         
1617723  status_update  described_state  2015-12-11 20:41:30 +0000  waiting_response  waiting_response  2015-12-11 20:41:30 +0000   
1617724  followup_sent    2015-12-11 20:42:11 +0000        outgoing  
1617725  status_update  described_state  2015-12-11 20:42:26 +0000  partially_successful  partially_successful  2015-12-11 20:42:26 +0000   
1618410  response    2015-12-14 09:44:39 +0000    partially_successful  2015-12-14 09:58:49 +0000  incoming  
1618427  followup_sent    2015-12-14 09:58:43 +0000        outgoing  
1618428  status_update    2015-12-14 09:58:49 +0000  partially_successful  partially_successful  2015-12-14 09:58:49 +0000   
1619908  response    2015-12-15 12:50:11 +0000    partially_successful  2015-12-17 21:28:47 +0000  incoming  
1622742  followup_sent    2015-12-17 21:28:39 +0000        outgoing  
1622744  status_update    2015-12-17 21:28:47 +0000  partially_successful  partially_successful  2015-12-17 21:28:47 +0000   
1622881  response    2015-12-18 09:18:35 +0000        incoming  
1622918  followup_sent    2015-12-18 09:34:43 +0000        outgoing  
1622928  response    2015-12-18 09:39:02 +0000        incoming  
1626601  followup_sent    2015-12-23 09:22:33 +0000        outgoing  
1626602  response    2015-12-23 09:23:05 +0000    partially_successful  2016-03-12 08:33:12 +0000  incoming  
1629222  status_update  described_state  2015-12-29 20:06:12 +0000  waiting_response  waiting_response  2015-12-29 20:06:12 +0000   
1645172  status_update  described_state  2016-01-16 18:15:25 +0000  partially_successful  partially_successful  2016-01-16 18:15:25 +0000   
1710882  status_update  described_state  2016-03-11 22:00:38 +0000  waiting_response  waiting_response  2016-03-11 22:00:38 +0000   
1711022  followup_sent    2016-03-12 08:32:58 +0000        outgoing  
1711024  status_update  described_state  2016-03-12 08:33:12 +0000  partially_successful  partially_successful  2016-03-12 08:33:12 +0000   
1711036  response    2016-03-12 08:52:25 +0000    partially_successful  2016-05-22 09:19:03 +0100  incoming  
1761221  status_update    2016-04-22 12:34:55 +0100  partially_successful  partially_successful  2016-04-22 12:34:55 +0100   
1761229  comment    2016-04-22 12:40:09 +0100         
1791905  status_update  described_state  2016-05-18 12:40:47 +0100  internal_review  internal_review  2016-05-18 12:40:48 +0100   
1796031  comment    2016-05-22 09:18:30 +0100         
1796032  status_update  described_state  2016-05-22 09:19:03 +0100  partially_successful  partially_successful  2016-05-22 09:19:03 +0100   
1944145  response    2016-09-28 17:32:09 +0100    waiting_response  2016-11-25 17:29:12 +0000  incoming  
1944197  followup_sent    2016-09-28 18:31:53 +0100        outgoing  
1956914  comment    2016-10-10 20:56:17 +0100         
2009963  status_update  described_state  2016-11-25 17:29:12 +0000  waiting_response  waiting_response  2016-11-25 17:29:12 +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.