Details of request “Definitive Statement of Public Rights of Way

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
1692080  sent  2016-02-28 21:33:47 +0000  waiting_response  2016-02-28 21:33:48 +0000  waiting_response  outgoing  
1692180  response  2016-02-29 08:11:49 +0000    2016-02-29 08:34:43 +0000  waiting_response  incoming  
1692201  status_update  2016-02-29 08:34:43 +0000  waiting_response  2016-02-29 08:34:43 +0000  waiting_response   
1730587  response  2016-03-29 16:30:07 +0100    2016-04-01 12:30:39 +0100  waiting_clarification  incoming  
1734787  status_update  2016-04-01 12:30:39 +0100  waiting_clarification  2016-04-01 12:30:39 +0100  waiting_clarification   
1734815  followup_sent  2016-04-01 12:39:57 +0100  waiting_response  2016-04-01 12:39:57 +0100  waiting_response  outgoing  
1764928  response  2016-04-26 11:27:02 +0100    2016-04-30 19:41:47 +0100  waiting_clarification  incoming  
1771669  status_update  2016-04-30 19:41:47 +0100  waiting_clarification  2016-04-30 19:41:47 +0100  waiting_clarification   
1782774  followup_sent  2016-05-11 09:00:27 +0100  waiting_response  2016-05-11 09:00:27 +0100  waiting_response  outgoing  
1783761  response  2016-05-11 15:39:09 +0100    2016-05-15 15:15:56 +0100  waiting_clarification  incoming  
1787778  status_update  2016-05-15 15:15:56 +0100  waiting_clarification  2016-05-15 15:15:56 +0100  waiting_clarification   
1800399  followup_sent  2016-05-25 16:24:58 +0100  internal_review  2016-05-25 16:24:59 +0100  internal_review  outgoing  
1800903  response  2016-05-26 09:42:30 +0100    2016-05-30 15:21:17 +0100  internal_review  incoming  
1804230  status_update  2016-05-30 15:21:17 +0100  internal_review  2016-05-30 15:21:17 +0100  internal_review   
1864770  followup_sent  2016-07-22 08:14:00 +0100        outgoing  
1864822  response  2016-07-22 09:11:06 +0100    2016-07-22 16:33:22 +0100  internal_review  incoming  
1865861  status_update  2016-07-22 16:33:22 +0100  internal_review  2016-07-22 16:33:22 +0100  internal_review   
2417902  very_overdue  2016-07-23 00:00:00 +0100         
1871036  response  2016-07-27 15:36:45 +0100    2016-08-03 08:07:28 +0100  internal_review  incoming  
1878072  status_update  2016-08-03 08:07:28 +0100  internal_review  2016-08-03 08:07:28 +0100  internal_review   
1894531  followup_sent  2016-08-17 15:06:14 +0100  internal_review  2016-08-17 15:06:14 +0100  internal_review  outgoing  
1894567  response  2016-08-17 15:23:32 +0100    2016-08-17 15:24:32 +0100  internal_review  incoming  
1894568  status_update  2016-08-17 15:24:32 +0100  internal_review  2016-08-17 15:24:32 +0100  internal_review   
1894738  response  2016-08-17 16:35:51 +0100    2016-08-19 16:09:31 +0100  internal_review  incoming  
1897684  status_update  2016-08-19 16:09:31 +0100  internal_review  2016-08-19 16:09:31 +0100  internal_review   
2052761  response  2017-01-10 15:07:37 +0000    2017-01-10 15:12:18 +0000  internal_review  incoming  
2052769  status_update  2017-01-10 15:12:18 +0000  internal_review  2017-01-10 15:12:18 +0000  internal_review   
2052787  followup_sent  2017-01-10 15:18:04 +0000        outgoing  
2266232  comment  2017-02-16 22:29:54 +0000         
2325515  followup_sent  2017-04-07 16:02:28 +0100  internal_review  2017-04-07 16:02:28 +0100  internal_review  outgoing  
2342536  comment  2017-04-24 13:46:34 +0100         
2357938  redeliver_incoming  2017-05-08 21:01:52 +0100         
2358056  status_update  2017-05-08 23:59:29 +0100  waiting_response  2017-05-08 23:59:30 +0100  waiting_response   
2358199  followup_sent  2017-05-09 08:37:14 +0100        outgoing  
2360577  response  2017-05-10 16:03:26 +0100    2017-05-11 00:13:08 +0100  waiting_response  incoming  
2360987  status_update  2017-05-11 00:13:08 +0100  waiting_response  2017-05-11 00:13:08 +0100  waiting_response   
2375220  response  2017-05-23 16:22:42 +0100    2017-05-23 16:33:43 +0100  partially_successful  incoming  
2375246  status_update  2017-05-23 16:33:43 +0100  partially_successful  2017-05-23 16:33:43 +0100  partially_successful   
2375348  followup_sent  2017-05-23 17:55:18 +0100        outgoing  
2383603  response  2017-06-01 11:55:46 +0100    2017-06-01 12:49:16 +0100  partially_successful  incoming  
2383676  status_update  2017-06-01 12:49:15 +0100  partially_successful  2017-06-01 12:49:16 +0100  partially_successful   
2383700  followup_sent  2017-06-01 13:03:53 +0100        outgoing  
2384212  response  2017-06-01 18:27:38 +0100    2017-06-01 19:26:55 +0100  successful  incoming  
2384235  status_update  2017-06-01 19:26:54 +0100  successful  2017-06-01 19:26:55 +0100  successful   

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.