Details of request “Tendring Crematorium

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
2623292  sent  2017-11-09 10:56:36 +0000  waiting_response  2017-11-09 10:56:36 +0000  waiting_response  outgoing  
2623683  response  2017-11-09 13:37:31 +0000    2017-11-13 10:45:26 +0000  waiting_response  incoming  
2627779  status_update  2017-11-13 10:45:26 +0000  waiting_response  2017-11-13 10:45:26 +0000  waiting_response   
2644133  response  2017-11-24 10:05:29 +0000    2017-12-08 00:15:19 +0000  waiting_response  incoming  
2662444  status_update  2017-12-08 00:15:19 +0000  waiting_response  2017-12-08 00:15:19 +0000  waiting_response   
2663958  overdue  2017-12-09 00:00:00 +0000         
2667616  followup_sent  2017-12-12 12:14:27 +0000        outgoing  
2667739  response  2017-12-12 13:14:20 +0000    2017-12-12 13:27:20 +0000  waiting_response  incoming  
2667767  followup_sent  2017-12-12 13:27:11 +0000        outgoing  
2667768  status_update  2017-12-12 13:27:20 +0000  waiting_response  2017-12-12 13:27:20 +0000  waiting_response   
2667795  response  2017-12-12 13:39:01 +0000    2017-12-12 14:41:17 +0000  successful  incoming  
2667924  status_update  2017-12-12 14:41:17 +0000  successful  2017-12-12 14:41:17 +0000  successful   
2809057  edit  2018-03-13 03:45:34 +0000         
2809058  edit  2018-03-13 03:45:34 +0000         
2809059  edit  2018-03-13 03:45:34 +0000         
2809060  edit  2018-03-13 03:45:34 +0000         
2809061  edit  2018-03-13 03:45:34 +0000         
2809062  edit  2018-03-13 03:45:34 +0000         
2809063  edit  2018-03-13 03:45:34 +0000         
2809064  edit  2018-03-13 03:45:34 +0000         
2809065  edit  2018-03-13 03:45:34 +0000         
2809066  edit  2018-03-13 03:45:35 +0000         
2809067  edit  2018-03-13 03:45:35 +0000         
2809068  edit  2018-03-13 03:45:35 +0000         
3181316  edit  2018-06-13 03:47:12 +0100         
3181317  edit  2018-06-13 03:47:12 +0100         
3181318  edit  2018-06-13 03:47:12 +0100         
3181319  edit  2018-06-13 03:47:12 +0100         
3181320  edit  2018-06-13 03:47:12 +0100         
3181321  edit  2018-06-13 03:47:12 +0100         
3181322  edit  2018-06-13 03:47:12 +0100         
3181323  edit  2018-06-13 03:47:12 +0100         
3181324  edit  2018-06-13 03:47:12 +0100         
3181325  edit  2018-06-13 03:47:12 +0100         
3181326  edit  2018-06-13 03:47:12 +0100         
3181327  edit  2018-06-13 03:47:12 +0100         
3181328  edit  2018-06-13 03:47:12 +0100         
3181329  edit  2018-06-13 03:47:12 +0100         
3181330  edit  2018-06-13 03:47:12 +0100         
3181331  edit  2018-06-13 03:47:12 +0100         
3181332  edit  2018-06-13 03:47:13 +0100         
3181333  edit  2018-06-13 03:47:13 +0100         
3181334  edit  2018-06-13 03:47:13 +0100         
3181335  edit  2018-06-13 03:47:13 +0100         
3181336  edit  2018-06-13 03:47:13 +0100         
3181337  edit  2018-06-13 03:47:13 +0100         
3181338  edit  2018-06-13 03:47:13 +0100         
3181339  edit  2018-06-13 03:47:13 +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.