Details of request 'Length of Complaint'
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 |
|---|---|---|---|---|---|---|
| 38975 | sent | Mon Mar 09 16:46:13 UTC 2009 | waiting_response | Mon Mar 09 16:46:14 UTC 2009 | waiting_response | outgoing |
| 39092 | response | Tue Mar 10 08:16:24 UTC 2009 | waiting_clarification | Tue Mar 10 14:58:30 UTC 2009 | waiting_clarification | incoming |
| 40530 | followup_sent | Mon Mar 16 15:58:45 UTC 2009 | waiting_response | Mon Mar 16 15:58:45 UTC 2009 | waiting_response | outgoing |
| 40539 | response | Mon Mar 16 16:19:49 UTC 2009 | incoming | |||
| 40746 | response | Tue Mar 17 16:24:33 UTC 2009 | incoming | |||
| 40926 | followup_sent | Wed Mar 18 13:39:22 UTC 2009 | waiting_response | Wed Mar 18 13:39:33 UTC 2009 | waiting_response | outgoing |
| 41277 | response | Fri Mar 20 08:01:42 UTC 2009 | waiting_clarification | Tue Mar 24 14:06:48 UTC 2009 | waiting_clarification | incoming |
| 41945 | followup_sent | Tue Mar 24 14:25:33 UTC 2009 | waiting_response | Tue Mar 24 14:25:33 UTC 2009 | waiting_response | outgoing |
| 48490 | followup_sent | Fri Apr 24 21:07:40 UTC 2009 | internal_review | Fri Apr 24 22:07:40 UTC 2009 | internal_review | outgoing |
| 48685 | response | Mon Apr 27 09:51:36 UTC 2009 | internal_review | Mon Apr 27 11:36:20 UTC 2009 | internal_review | incoming |
| 48720 | followup_sent | Mon Apr 27 10:50:34 UTC 2009 | outgoing | |||
| 48725 | response | Mon Apr 27 11:01:30 UTC 2009 | incoming | |||
| 51262 | response | Fri May 08 12:46:12 UTC 2009 | Sat May 09 08:46:40 UTC 2009 | internal_review | incoming | |
| 51536 | comment | Fri May 08 19:03:04 UTC 2009 | ||||
| 51567 | comment | Sat May 09 07:45:31 UTC 2009 | internal_review | |||
| 51569 | followup_sent | Sat May 09 07:48:35 UTC 2009 | outgoing | |||
| 51671 | comment | Sun May 10 19:06:09 UTC 2009 | ||||
| 51706 | comment | Mon May 11 07:10:07 UTC 2009 | ||||
| 51708 | response | Mon May 11 07:27:22 UTC 2009 | Sun Aug 16 21:32:30 UTC 2009 | partially_successful | incoming | |
| 51788 | comment | Mon May 11 09:40:43 UTC 2009 | partially_successful | |||
| 78864 | status_update | Sun Aug 16 20:32:31 UTC 2009 |
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.
Make and explore Freedom of Information requests