Details of request “Dalton Park

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
1843732  sent    2016-07-05 15:44:05 +0100  waiting_response  waiting_response  2016-07-05 15:44:06 +0100  outgoing  
1844204  response    2016-07-06 08:28:25 +0100    waiting_clarification  2016-07-06 17:18:30 +0100  incoming  
1845324  followup_sent    2016-07-06 17:18:13 +0100        outgoing  
1845325  status_update  described_state  2016-07-06 17:18:30 +0100  waiting_clarification  waiting_clarification  2016-07-06 17:18:30 +0100   
1848240  followup_sent    2016-07-08 19:37:31 +0100  waiting_response  waiting_response  2016-07-08 19:37:31 +0100  outgoing  
1849035  response    2016-07-10 21:01:14 +0100    waiting_response  2016-07-10 23:18:59 +0100  incoming  
1849066  status_update    2016-07-10 23:18:59 +0100  waiting_response  waiting_response  2016-07-10 23:18:59 +0100   
1882282  response    2016-08-08 08:26:52 +0100    waiting_response  2016-08-08 09:04:51 +0100  incoming  
1882351  status_update    2016-08-08 09:04:51 +0100  waiting_response  waiting_response  2016-08-08 09:04:51 +0100   
2191468  overdue    2016-08-10 00:00:00 +0100         
1885318  followup_sent    2016-08-10 09:24:38 +0100        outgoing  
1885398  response    2016-08-10 10:03:44 +0100    waiting_response  2016-08-14 08:15:01 +0100  incoming  
1890094  status_update    2016-08-14 08:15:01 +0100  waiting_response  waiting_response  2016-08-14 08:15:01 +0100   
1890095  followup_sent    2016-08-14 08:22:03 +0100  internal_review  internal_review  2016-08-14 08:22:03 +0100  outgoing  
1890299  response    2016-08-14 21:08:06 +0100        incoming  
1891643  response    2016-08-15 15:32:36 +0100        incoming  
1891645  response    2016-08-15 15:33:38 +0100        incoming  
1891646  response    2016-08-15 15:33:45 +0100        incoming  
1891650  response    2016-08-15 15:34:37 +0100        incoming  
1891652  response    2016-08-15 15:35:05 +0100        incoming  
1926752  response    2016-09-14 14:33:01 +0100        incoming  
2014032  response    2016-11-30 10:56:04 +0000    successful  2017-04-26 16:25:22 +0100  incoming  
2346206  status_update  described_state  2017-04-26 16:25:22 +0100  successful  successful  2017-04-26 16:25:22 +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.