Details of request “Montrose Beach Stakeholders Group Meeting 12 November 2018

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
3715671  sent  2018-11-17 17:28:06 +0000  waiting_response  2018-11-17 17:28:06 +0000  waiting_response  outgoing  
3715672  response  2018-11-17 17:28:42 +0000    2018-11-19 15:04:20 +0000  waiting_response  incoming  
3719837  status_update  2018-11-19 15:04:20 +0000  waiting_response  2018-11-19 15:04:20 +0000  waiting_response   
3722894  response  2018-11-20 18:18:50 +0000    2018-11-25 15:24:33 +0000  waiting_response  incoming  
3739536  status_update  2018-11-24 15:33:25 +0000  rejected  2018-11-24 15:33:25 +0000  rejected   
3741927  status_update  2018-11-25 15:24:32 +0000  waiting_response  2018-11-25 15:24:33 +0000  waiting_response   
3812219  overdue  2018-12-18 00:00:00 +0000         
3813982  status_update  2018-12-18 09:18:37 +0000  waiting_response  2018-12-18 09:18:37 +0000  waiting_response   
3815303  response  2018-12-18 15:41:33 +0000    2018-12-18 16:54:05 +0000  not_held  incoming  
3815468  status_update  2018-12-18 16:54:05 +0000  not_held  2018-12-18 16:54:05 +0000  not_held   
4257675  edit  2019-03-19 03:45:32 +0000         
4257676  edit  2019-03-19 03:45:32 +0000         
4257677  edit  2019-03-19 03:45:32 +0000         
4257678  edit  2019-03-19 03:45:32 +0000         
4257679  edit  2019-03-19 03:45:32 +0000         
4257680  edit  2019-03-19 03:45:32 +0000         
4257681  edit  2019-03-19 03:45:32 +0000         
4257682  edit  2019-03-19 03:45:33 +0000         
4257683  edit  2019-03-19 03:45:33 +0000         
4257684  edit  2019-03-19 03:45:33 +0000         
5896883  edit  2019-12-19 03:47:56 +0000         
5896884  edit  2019-12-19 03:47:56 +0000         
5896885  edit  2019-12-19 03:47:56 +0000         
5896886  edit  2019-12-19 03:47:56 +0000         
5896887  edit  2019-12-19 03:47:56 +0000         
5896888  edit  2019-12-19 03:47:56 +0000         
5896889  edit  2019-12-19 03:47:56 +0000         
5896890  edit  2019-12-19 03:47:56 +0000         
5896891  edit  2019-12-19 03:47:56 +0000         
5896892  edit  2019-12-19 03:47:56 +0000         
5896893  edit  2019-12-19 03:47:56 +0000         
5896894  edit  2019-12-19 03:47:57 +0000         
5896895  edit  2019-12-19 03:47:57 +0000         
5896896  edit  2019-12-19 03:47:57 +0000         
5896897  edit  2019-12-19 03:47:57 +0000         
5896898  edit  2019-12-19 03:47:57 +0000         
5896899  edit  2019-12-19 03:47:57 +0000         
5896900  edit  2019-12-19 03:47:57 +0000         
5896901  edit  2019-12-19 03:47:57 +0000         
5896902  edit  2019-12-19 03:47:57 +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.