Details of request “New Area 7 maintenance contract with Amey

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
1724210  sent    2016-03-22 12:18:53 +0000  waiting_response  waiting_response  2016-03-22 12:18:53 +0000  outgoing  
1724212  response    2016-03-22 12:19:34 +0000    waiting_response  2016-03-29 16:33:29 +0100  incoming  
1730591  status_update    2016-03-29 16:33:29 +0100  waiting_response  waiting_response  2016-03-29 16:33:29 +0100   
1733855  response    2016-03-31 15:57:53 +0100    waiting_response  2016-04-04 10:48:18 +0100  incoming  
1736684  status_update    2016-04-04 10:48:18 +0100  waiting_response  waiting_response  2016-04-04 10:48:18 +0100   
1736739  followup_sent    2016-04-04 11:10:34 +0100        outgoing  
2185743  overdue    2016-04-22 00:00:00 +0100         
1767567  followup_sent    2016-04-27 15:58:26 +0100        outgoing  
1767775  response    2016-04-27 16:39:51 +0100        incoming  
1768138  followup_sent    2016-04-27 19:39:01 +0100        outgoing  
1768139  response    2016-04-27 19:39:38 +0100    waiting_response  2016-04-28 16:17:57 +0100  incoming  
1769481  status_update    2016-04-28 16:17:57 +0100  waiting_response  waiting_response  2016-04-28 16:17:57 +0100   
1773943  response    2016-05-03 15:45:47 +0100        incoming  
1776572  comment    2016-05-05 10:35:31 +0100         
1776679  followup_sent    2016-05-05 11:21:47 +0100  internal_review  internal_review  2016-05-05 11:21:47 +0100  outgoing  
1776681  response    2016-05-05 11:22:33 +0100    internal_review  2016-05-05 11:35:24 +0100  incoming  
1776715  status_update    2016-05-05 11:35:24 +0100  internal_review  internal_review  2016-05-05 11:35:24 +0100   
1780131  comment    2016-05-09 12:07:43 +0100         
1790672  response    2016-05-17 14:01:49 +0100    gone_postal  2016-05-17 14:49:10 +0100  incoming  
1790837  status_update  described_state  2016-05-17 14:49:10 +0100  gone_postal  gone_postal  2016-05-17 14:49:10 +0100   
1794393  response    2016-05-20 09:41:25 +0100    successful  2016-05-20 11:33:25 +0100  incoming  
1794647  status_update  described_state  2016-05-20 11:33:25 +0100  successful  successful  2016-05-20 11:33:25 +0100   
2705351  comment    2018-01-16 17:11:10 +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.