Details of request 'FOI Request handling, Data for Jan 2009 - Jan 2010 inclusive'

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 created_at described_state last_described_at calculated_state link
142198 sent Mon Feb 15 22:18:39 UTC 2010 waiting_response Mon Feb 15 22:18:39 UTC 2010 waiting_response outgoing
144215 followup_sent Sun Feb 21 18:21:38 UTC 2010 outgoing
144433 response Mon Feb 22 11:47:00 UTC 2010 incoming
144509 followup_sent Mon Feb 22 13:24:38 UTC 2010 waiting_response Mon Feb 22 13:24:48 UTC 2010 waiting_response outgoing
144613 response Mon Feb 22 15:59:16 UTC 2010 waiting_response Tue Feb 23 08:10:04 UTC 2010 waiting_response incoming
146872 response Mon Mar 01 17:22:06 UTC 2010 incoming
151266 response Mon Mar 15 09:36:21 UTC 2010 incoming
151538 response Mon Mar 15 16:24:30 UTC 2010 waiting_response Mon Mar 15 22:01:00 UTC 2010 waiting_response incoming
151735 response Tue Mar 16 09:42:23 UTC 2010 successful Thu Mar 18 21:17:08 UTC 2010 successful incoming

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.