Details of request “Correspondence & Documentation connected with TfL's participation in the "Trams Update" conducted at the 20 March 2018 Meeting of the Croydon Council Scrutiny and Overview Committee

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 details created_at described_state calculated_state last_described_at link
6081107  sent    2020-01-21 09:33:27 +0000  waiting_response  waiting_response  2020-01-21 09:33:27 +0000  outgoing  
6081637  response    2020-01-21 12:06:55 +0000    waiting_response  2020-01-22 21:22:13 +0000  incoming  
6102643  status_update    2020-01-22 21:22:12 +0000  waiting_response  waiting_response  2020-01-22 21:22:13 +0000   
6301764  response    2020-02-18 15:56:46 +0000    waiting_response  2020-02-19 09:42:27 +0000  incoming  
6318204  overdue    2020-02-19 00:00:00 +0000         
6309083  status_update    2020-02-19 09:42:27 +0000  waiting_response  waiting_response  2020-02-19 09:42:27 +0000   
6508097  response    2020-03-18 16:38:50 +0000    partially_successful  2020-03-19 10:53:28 +0000  incoming  
6517595  status_update  described_state  2020-03-19 10:53:28 +0000  partially_successful  partially_successful  2020-03-19 10:53:28 +0000   
7126332  edit metadata  allow_new_responses_from  2020-06-20 03:46:16 +0100         
7126333  edit metadata  allow_new_responses_from  2020-06-20 03:46:16 +0100         
7126334  edit metadata  allow_new_responses_from  2020-06-20 03:46:16 +0100         
7126335  edit metadata  allow_new_responses_from  2020-06-20 03:46:16 +0100         
7126336  edit metadata  allow_new_responses_from  2020-06-20 03:46:16 +0100         
7126337  edit metadata  allow_new_responses_from  2020-06-20 03:46:16 +0100         
7126338  edit metadata  allow_new_responses_from  2020-06-20 03:46:16 +0100         
7126339  edit metadata  allow_new_responses_from  2020-06-20 03:46:17 +0100         
8914921  edit metadata  allow_new_responses_from  2021-03-20 03:46:16 +0000         
8914922  edit metadata  allow_new_responses_from  2021-03-20 03:46:16 +0000         
8914923  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914924  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914925  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914926  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914927  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914928  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914929  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914930  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914931  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914932  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914933  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914934  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914935  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +0000         
8914936  edit metadata  allow_new_responses_from  2021-03-20 03:46:17 +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.