Details of request “Parking fines in Eastbourne

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
1016461  sent    2014-04-08 16:27:38 +0100  waiting_response  waiting_response  2014-04-08 16:27:39 +0100  outgoing  
1016469  followup_sent    2014-04-08 16:30:52 +0100        outgoing  
1016815  response    2014-04-09 08:11:10 +0100    waiting_response  2014-04-13 11:07:27 +0100  incoming  
1020638  status_update    2014-04-13 11:07:27 +0100  waiting_response  waiting_response  2014-04-13 11:07:27 +0100   
1027357  response    2014-04-22 11:07:39 +0100    waiting_response  2014-04-26 23:19:43 +0100  incoming  
1032188  status_update    2014-04-26 23:19:43 +0100  waiting_response  waiting_response  2014-04-26 23:19:43 +0100   
1034404  response    2014-04-29 13:58:31 +0100    rejected  2014-05-03 08:02:35 +0100  incoming  
1038420  status_update  described_state  2014-05-03 08:02:35 +0100  rejected  rejected  2014-05-03 08:02:35 +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.