Details of request “YAS Board Expenses

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
878250  sent    2013-11-11 20:13:57 +0000  waiting_response  waiting_response  2013-11-11 20:13:57 +0000  outgoing  
879483  response    2013-11-12 16:48:56 +0000    waiting_response  2013-11-22 23:38:36 +0000  incoming  
889489  status_update    2013-11-22 23:38:36 +0000  waiting_response  waiting_response  2013-11-22 23:38:36 +0000   
895831  response    2013-11-29 15:32:51 +0000    waiting_clarification  2013-12-02 09:00:27 +0000  incoming  
896786  status_update  described_state  2013-12-02 09:00:27 +0000  waiting_clarification  waiting_clarification  2013-12-02 09:00:27 +0000   
896794  followup_sent    2013-12-02 09:04:53 +0000  waiting_response  waiting_response  2013-12-02 09:04:53 +0000  outgoing  
898870  response    2013-12-03 16:09:25 +0000    waiting_response  2013-12-03 17:15:08 +0000  incoming  
898957  status_update    2013-12-03 17:15:08 +0000  waiting_response  waiting_response  2013-12-03 17:15:08 +0000   
2149913  overdue    2014-01-04 00:00:00 +0000         
924664  followup_sent    2014-01-05 03:54:05 +0000  internal_review  internal_review  2014-01-05 03:54:05 +0000  outgoing  
946177  response    2014-01-28 11:35:19 +0000    internal_review  2014-01-29 04:55:00 +0000  incoming  
946984  followup_sent    2014-01-29 04:54:53 +0000        outgoing  
946985  status_update    2014-01-29 04:55:00 +0000  internal_review  internal_review  2014-01-29 04:55:00 +0000   
962206  followup_sent    2014-02-13 13:53:58 +0000        outgoing  
1034828  followup_sent    2014-04-29 21:24:05 +0100  internal_review  internal_review  2014-04-29 21:24:05 +0100  outgoing  
1037003  response    2014-05-01 16:38:25 +0100    internal_review  2014-05-05 19:26:16 +0100  incoming  
1039302  status_update    2014-05-05 19:26:16 +0100  internal_review  internal_review  2014-05-05 19:26:16 +0100   
1040551  response    2014-05-06 15:41:04 +0100    not_held  2014-06-01 02:33:34 +0100  incoming  
1067714  status_update  described_state  2014-06-01 02:33:34 +0100  not_held  not_held  2014-06-01 02:33:34 +0100   
1067715  comment    2014-06-01 02:38:48 +0100         
1093808  response    2014-06-30 16:41:13 +0100    not_held  2014-06-30 21:17:43 +0100  incoming  
1094007  status_update    2014-06-30 21:17:43 +0100  not_held  not_held  2014-06-30 21:17:43 +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.