Details of request “State of requirement and evaluation from "You won't be settled" public information campaign

Event history

This table shows the technical details of the internal events that happened to this request on Right to Know. 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 Right to Know. 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
47920  sent  2020-07-17 00:02:58 +1000  waiting_response  2020-07-17 00:02:58 +1000  waiting_response  outgoing  
47921  response  2020-07-17 00:04:02 +1000    2020-07-17 00:16:09 +1000  waiting_response  incoming  
47937  status_update  2020-07-17 00:16:09 +1000  waiting_response  2020-07-17 00:16:09 +1000  waiting_response   
48740  response  2020-08-12 07:17:32 +1000    2020-08-14 01:27:31 +1000  waiting_clarification  incoming  
48792  followup_sent  2020-08-14 01:27:23 +1000        outgoing  
48793  status_update  2020-08-14 01:27:31 +1000  waiting_clarification  2020-08-14 01:27:31 +1000  waiting_clarification   
48794  response  2020-08-14 01:28:25 +1000    2020-08-14 01:30:35 +1000  waiting_response  incoming  
48795  status_update  2020-08-14 01:30:35 +1000  waiting_response  2020-08-14 01:30:35 +1000  waiting_response   
54965  overdue  2020-08-18 00:00:00 +1000         
49772  response  2020-09-14 15:43:58 +1000    2020-10-09 07:18:57 +1100  waiting_response  incoming  
56562  very_overdue  2020-09-16 00:00:00 +1000         
50507  status_update  2020-10-09 07:18:57 +1100  waiting_response  2020-10-09 07:18:57 +1100  waiting_response   
50941  followup_sent  2020-10-27 08:30:19 +1100        outgoing  
51180  response  2020-11-04 09:06:31 +1100        incoming  
51403  response  2020-11-12 16:21:30 +1100    2020-11-20 02:59:15 +1100  partially_successful  incoming  
51605  status_update  2020-11-20 02:59:14 +1100  partially_successful  2020-11-20 02:59:15 +1100  partially_successful   
62779  edit  2021-05-20 03:45:10 +1000         
62780  edit  2021-05-20 03:45:10 +1000         
62781  edit  2021-05-20 03:45:10 +1000         
62782  edit  2021-05-20 03:45:10 +1000         
62783  edit  2021-05-20 03:45:10 +1000         
62784  edit  2021-05-20 03:45:10 +1000         
62785  edit  2021-05-20 03:45:10 +1000         
62786  edit  2021-05-20 03:45:11 +1000         
62787  edit  2021-05-20 03:45:11 +1000         
62788  edit  2021-05-20 03:45:11 +1000         
62789  edit  2021-05-20 03:45:11 +1000         
62790  edit  2021-05-20 03:45:11 +1000         
62791  edit  2021-05-20 03:45:11 +1000         
62792  edit  2021-05-20 03:45:11 +1000         
62793  edit  2021-05-20 03:45:12 +1000         
62794  edit  2021-05-20 03:45:12 +1000         

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 Right to Know 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.