Details of request 'Verrus contract Re Motorcycle parking'

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
76324 sent Sat Aug 08 23:43:37 UTC 2009 waiting_response Sun Aug 09 00:43:38 UTC 2009 waiting_response outgoing
76510 response Mon Aug 10 08:32:39 UTC 2009 waiting_response Fri Aug 14 10:23:08 UTC 2009 waiting_response incoming
85842 followup_sent Thu Sep 10 11:00:41 UTC 2009 internal_review Thu Sep 10 11:00:41 UTC 2009 internal_review outgoing
85940 response Thu Sep 10 14:31:51 UTC 2009 internal_review Thu Sep 10 20:13:45 UTC 2009 internal_review incoming
86320 response Fri Sep 11 14:43:32 UTC 2009 incoming
86821 response Mon Sep 14 16:57:20 UTC 2009 internal_review Sun Sep 20 10:59:14 UTC 2009 internal_review incoming
91404 response Wed Sep 30 12:23:06 UTC 2009 internal_review Sun Oct 04 22:29:51 UTC 2009 internal_review incoming
99662 response Fri Oct 16 12:58:30 UTC 2009 incoming
100321 response Mon Oct 19 15:35:02 UTC 2009 partially_successful Wed Nov 25 21:06:55 UTC 2009 successful incoming
109217 status_update Tue Nov 10 12:10:24 UTC 2009 successful
177981 comment Mon May 31 02:50:46 UTC 2010

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.