Details of request “Traffic light schema for seismic monitoring at fracking development wells at Preston New Road

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
3672971  sent  2018-11-05 11:50:50 +0000  waiting_response  2018-11-05 11:50:50 +0000  waiting_response  outgoing  
3770342  overdue  2018-12-05 00:00:00 +0000         
3770463  followup_sent  2018-12-05 08:41:01 +0000  internal_review  2018-12-05 08:41:01 +0000  internal_review  outgoing  
3850297  response  2019-01-03 16:42:10 +0000        incoming  
3853185  response  2019-01-04 13:41:16 +0000    2019-09-06 16:01:42 +0100  waiting_response  incoming  
5292292  very_overdue  2019-01-08 00:00:00 +0000         
3903513  status_update  2019-01-16 16:05:50 +0000  partially_successful  2019-01-16 16:05:50 +0000  partially_successful   
4400423  edit  2019-04-17 03:45:20 +0100         
4400424  edit  2019-04-17 03:45:20 +0100         
4400425  edit  2019-04-17 03:45:20 +0100         
4400426  edit  2019-04-17 03:45:20 +0100         
4400427  edit  2019-04-17 03:45:20 +0100         
4400428  edit  2019-04-17 03:45:20 +0100         
5285085  followup_sent  2019-09-06 14:26:19 +0100        outgoing  
5285272  status_update  2019-09-06 16:01:42 +0100  waiting_response  2019-09-06 16:01:42 +0100  waiting_response   
5292358  followup_sent  2019-09-07 06:57:50 +0100        outgoing  
5575472  response  2019-10-25 12:11:12 +0100    2019-10-25 16:45:08 +0100  partially_successful  incoming  
5576492  status_update  2019-10-25 16:45:08 +0100  partially_successful  2019-10-25 16:45:08 +0100  partially_successful   
6126303  edit  2020-01-26 03:45:21 +0000         
6126304  edit  2020-01-26 03:45:21 +0000         
6126305  edit  2020-01-26 03:45:21 +0000         
6126306  edit  2020-01-26 03:45:21 +0000         
6126307  edit  2020-01-26 03:45:22 +0000         
6126308  edit  2020-01-26 03:45:22 +0000         
6126309  edit  2020-01-26 03:45:22 +0000         
6126310  edit  2020-01-26 03:45:22 +0000         
6126311  edit  2020-01-26 03:45:22 +0000         
6126312  edit  2020-01-26 03:45:22 +0000         
6126313  edit  2020-01-26 03:45:22 +0000         
6126314  edit  2020-01-26 03:45:22 +0000         
6126315  edit  2020-01-26 03:45:22 +0000         
6126316  edit  2020-01-26 03:45:22 +0000         
6126317  edit  2020-01-26 03:45:22 +0000         
6126318  edit  2020-01-26 03:45:22 +0000         
6126319  edit  2020-01-26 03:45:22 +0000         
6126320  edit  2020-01-26 03:45:22 +0000         

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.