Details of request “Board Minutes

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
1743999  sent    2016-04-08 17:44:04 +0100  waiting_response  waiting_response  2016-04-08 17:44:04 +0100  outgoing  
1744001  response    2016-04-08 17:44:35 +0100    waiting_response  2016-04-11 15:36:05 +0100  incoming  
1745792  status_update    2016-04-11 15:36:05 +0100  waiting_response  waiting_response  2016-04-11 15:36:05 +0100   
1772342  comment    2016-05-02 17:18:10 +0100         
1776852  response    2016-05-05 12:27:42 +0100        incoming  
1777003  followup_sent    2016-05-05 13:30:15 +0100        outgoing  
1777006  response    2016-05-05 13:30:48 +0100    waiting_response  2016-05-09 08:21:42 +0100  incoming  
1778824  comment    2016-05-07 08:43:51 +0100         
1779479  status_update    2016-05-09 08:21:41 +0100  waiting_response  waiting_response  2016-05-09 08:21:42 +0100   
1780423  response    2016-05-09 14:16:20 +0100        incoming  
1780484  followup_sent    2016-05-09 14:30:27 +0100        outgoing  
1780486  response    2016-05-09 14:31:09 +0100        incoming  
1784659  response    2016-05-12 11:55:35 +0100    successful  2016-05-16 09:28:20 +0100  incoming  
1788186  status_update  described_state  2016-05-16 09:28:20 +0100  successful  successful  2016-05-16 09:28:20 +0100   
1791267  comment    2016-05-17 22:34:03 +0100         
1791283  comment    2016-05-17 23:25:21 +0100         
1814105  followup_sent    2016-06-07 20:13:52 +0100        outgoing  
1814106  response    2016-06-07 20:14:22 +0100    waiting_response  2016-06-08 10:07:22 +0100  incoming  
2247875  very_overdue    2016-06-08 00:00:00 +0100         
1814584  status_update  described_state  2016-06-08 10:07:22 +0100  waiting_response  waiting_response  2016-06-08 10:07:22 +0100   
1814593  comment    2016-06-08 10:12:16 +0100         
1828693  comment    2016-06-21 17:58:06 +0100         
1828879  followup_sent    2016-06-21 22:42:57 +0100  internal_review  internal_review  2016-06-21 22:42:57 +0100  outgoing  
1828880  response    2016-06-21 22:43:29 +0100    internal_review  2016-06-22 08:26:22 +0100  incoming  
1829033  status_update    2016-06-22 08:26:22 +0100  internal_review  internal_review  2016-06-22 08:26:22 +0100   
1833147  response    2016-06-27 09:10:15 +0100        incoming  
1833257  followup_sent    2016-06-27 09:41:17 +0100        outgoing  
1833260  response    2016-06-27 09:41:48 +0100    internal_review  2016-06-28 09:34:29 +0100  incoming  
1834791  comment    2016-06-28 00:25:33 +0100         
1835000  status_update    2016-06-28 09:34:29 +0100  internal_review  internal_review  2016-06-28 09:34:29 +0100   
1840279  comment    2016-07-01 20:45:17 +0100         
1840301  comment    2016-07-01 22:03:31 +0100         
1877980  followup_sent    2016-08-02 21:39:13 +0100  internal_review  internal_review  2016-08-02 21:39:13 +0100  outgoing  
1877981  response    2016-08-02 21:39:45 +0100    internal_review  2016-08-08 14:27:28 +0100  incoming  
1883103  status_update    2016-08-08 14:27:28 +0100  internal_review  internal_review  2016-08-08 14:27:28 +0100   
1883252  followup_sent    2016-08-08 15:30:56 +0100  internal_review  internal_review  2016-08-08 15:30:56 +0100  outgoing  
1883254  response    2016-08-08 15:31:16 +0100    internal_review  2016-08-08 17:43:28 +0100  incoming  
1883483  status_update    2016-08-08 17:43:28 +0100  internal_review  internal_review  2016-08-08 17:43:28 +0100   
1883746  response    2016-08-09 08:43:01 +0100        incoming  
1883891  followup_sent    2016-08-09 09:55:54 +0100  internal_review  internal_review  2016-08-09 09:55:54 +0100  outgoing  
1883949  response    2016-08-09 10:11:53 +0100    rejected  2016-08-13 08:55:30 +0100  incoming  
1884449  comment    2016-08-09 12:48:11 +0100         
1884658  comment    2016-08-09 14:30:32 +0100         
1889794  status_update  described_state  2016-08-13 08:55:30 +0100  rejected  rejected  2016-08-13 08:55:30 +0100   
1893904  comment    2016-08-17 10:06:41 +0100         
1900595  response    2016-08-22 17:34:28 +0100        incoming  
1900656  followup_sent    2016-08-22 19:25:24 +0100        outgoing  
1900657  response    2016-08-22 19:25:46 +0100    partially_successful  2016-08-22 20:00:47 +0100  incoming  
1900695  status_update  described_state  2016-08-22 20:00:47 +0100  partially_successful  partially_successful  2016-08-22 20:00:47 +0100   
1901423  response    2016-08-23 11:39:42 +0100    successful  2016-08-27 20:50:10 +0100  incoming  
1902395  comment    2016-08-23 17:11:43 +0100         
1903648  comment    2016-08-24 13:42:00 +0100         
1907323  status_update  described_state  2016-08-27 20:50:10 +0100  successful  successful  2016-08-27 20:50:10 +0100   
2454582  hide_comment  visible  2017-07-15 14:10:06 +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.