Details of request “Correspondence with Merton Council on plans for Wilson Health and Wellbeing Campus

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
2711423  sent  2018-01-21 14:38:42 +0000  waiting_response  2018-01-21 14:38:43 +0000  waiting_response  outgoing  
2713695  response  2018-01-23 08:05:52 +0000    2018-01-23 09:22:55 +0000  waiting_response  incoming  
2713837  status_update  2018-01-23 09:22:55 +0000  waiting_response  2018-01-23 09:22:55 +0000  waiting_response   
2745004  response  2018-02-13 11:49:53 +0000    2018-02-14 16:35:33 +0000  waiting_clarification  incoming  
2747055  followup_sent  2018-02-14 16:35:18 +0000        outgoing  
2747057  status_update  2018-02-14 16:35:33 +0000  waiting_clarification  2018-02-14 16:35:33 +0000  waiting_clarification   
2747833  response  2018-02-15 11:01:40 +0000    2018-02-15 11:03:10 +0000  waiting_response  incoming  
2747839  status_update  2018-02-15 11:03:10 +0000  waiting_response  2018-02-15 11:03:10 +0000  waiting_response   
2750434  overdue  2018-02-17 00:00:00 +0000         
2830494  very_overdue  2018-03-17 00:00:00 +0000         
2846809  followup_sent  2018-03-21 17:55:08 +0000        outgoing  
2957971  overdue  2018-04-21 00:00:00 +0100         
2970229  followup_sent  2018-04-24 18:12:26 +0100        outgoing  
2970231  status_update  2018-04-24 18:12:59 +0100  waiting_response  2018-04-24 18:12:59 +0100  waiting_response   
2979158  response  2018-04-26 09:44:00 +0100    2018-04-26 23:48:34 +0100  waiting_response  incoming  
2980609  status_update  2018-04-26 23:48:33 +0100  waiting_response  2018-04-26 23:48:34 +0100  waiting_response   
3085462  very_overdue  2018-05-22 00:00:00 +0100         
3091285  followup_sent  2018-05-23 16:33:39 +0100  internal_review  2018-05-23 16:33:39 +0100  internal_review  outgoing  
3201705  followup_sent  2018-06-16 22:18:25 +0100        outgoing  
3205467  response  2018-06-17 16:53:00 +0100    2018-06-17 21:33:41 +0100  waiting_response  incoming  
3205597  status_update  2018-06-17 21:33:41 +0100  waiting_response  2018-06-17 21:33:41 +0100  waiting_response   

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.