Details of request “Civil Service Commissioner

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
2428127  sent  2017-06-25 11:48:36 +0100  waiting_response  2017-06-25 11:48:37 +0100  waiting_response  outgoing  
2428128  response  2017-06-25 11:49:05 +0100    2017-06-25 11:51:26 +0100  waiting_response  incoming  
2428130  status_update  2017-06-25 11:51:26 +0100  waiting_response  2017-06-25 11:51:26 +0100  waiting_response   
2468514  overdue  2017-07-25 00:00:00 +0100         
2468788  response  2017-07-25 09:45:22 +0100        incoming  
2493381  followup_sent  2017-08-09 17:01:31 +0100  internal_review  2017-08-09 17:01:31 +0100  internal_review  outgoing  
2493384  response  2017-08-09 17:02:01 +0100    2017-08-09 17:03:42 +0100  waiting_response  incoming  
2493393  status_update  2017-08-09 17:03:42 +0100  waiting_response  2017-08-09 17:03:42 +0100  waiting_response   
2498415  comment  2017-08-14 10:15:34 +0100         
2498451  response  2017-08-14 10:29:16 +0100    2017-08-14 13:55:03 +0100  waiting_response  incoming  
2499103  status_update  2017-08-14 13:55:02 +0100  waiting_response  2017-08-14 13:55:02 +0100  waiting_response   
2499106  comment  2017-08-14 13:57:05 +0100         
2500266  report_comment  2017-08-15 09:57:43 +0100         
2500575  comment  2017-08-15 12:15:25 +0100         
2500576  edit  2017-08-15 12:15:35 +0100         
2507309  edit_comment  2017-08-21 10:00:21 +0100         
2510548  very_overdue  2017-08-23 00:00:00 +0100         
2511455  response  2017-08-23 14:52:10 +0100    2017-12-31 20:59:49 +0000  rejected  incoming  
2684897  status_update  2017-12-31 20:59:49 +0000  rejected  2017-12-31 20:59:49 +0000  rejected   
3263058  edit  2018-07-01 03:45:40 +0100         
3263059  edit  2018-07-01 03:45:40 +0100         
3263060  edit  2018-07-01 03:45:40 +0100         
3263061  edit  2018-07-01 03:45:40 +0100         
3263062  edit  2018-07-01 03:45:40 +0100         
3263063  edit  2018-07-01 03:45:40 +0100         
3263064  edit  2018-07-01 03:45:40 +0100         
3263065  edit  2018-07-01 03:45:40 +0100         
3263066  edit  2018-07-01 03:45:40 +0100         
3263067  edit  2018-07-01 03:45:40 +0100         
3263068  edit  2018-07-01 03:45:40 +0100         
3263069  edit  2018-07-01 03:45:40 +0100         
3263070  edit  2018-07-01 03:45:40 +0100         
3263071  edit  2018-07-01 03:45:40 +0100         
3263072  edit  2018-07-01 03:45:40 +0100         
3263073  edit  2018-07-01 03:45:40 +0100         
3263074  edit  2018-07-01 03:45:40 +0100         
3263075  edit  2018-07-01 03:45:40 +0100         
3263076  edit  2018-07-01 03:45:40 +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.