Details of request 'Collated information on ERO performance standards'

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
48637 sent Mon Apr 27 06:41:43 UTC 2009 waiting_response Mon Apr 27 07:41:43 UTC 2009 waiting_response outgoing
48643 response Mon Apr 27 07:29:35 UTC 2009 waiting_response Mon Apr 27 17:33:17 UTC 2009 waiting_response incoming
50199 response Tue May 05 12:56:16 UTC 2009 waiting_response Tue May 05 18:22:01 UTC 2009 waiting_response incoming
51857 response Mon May 11 11:34:37 UTC 2009 Mon May 11 18:37:14 UTC 2009 waiting_clarification incoming
52055 followup_sent Mon May 11 17:37:09 UTC 2009 waiting_clarification outgoing
52480 response Wed May 13 10:31:46 UTC 2009 waiting_response Wed May 13 20:07:47 UTC 2009 waiting_response incoming
52699 followup_sent Wed May 13 19:10:20 UTC 2009 outgoing
54936 response Fri May 22 08:56:07 UTC 2009 successful Fri May 22 18:43:44 UTC 2009 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.