Details of request “Participant Planning Questions

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
81798  sent  2022-02-14 09:43:35 +1100  waiting_response  2022-02-14 09:43:35 +1100  waiting_response  outgoing  
81799  response  2022-02-14 09:43:52 +1100    2022-02-22 19:06:57 +1100  waiting_response  incoming  
83038  status_update  2022-02-22 19:06:57 +1100  waiting_response  2022-02-22 19:06:57 +1100  waiting_response   
84063  response  2022-02-28 14:20:18 +1100    2022-03-15 10:58:07 +1100  waiting_response  incoming  
87550  status_update  2022-03-15 10:58:07 +1100  waiting_response  2022-03-15 10:58:07 +1100  waiting_response   
87940  overdue  2022-03-17 00:00:00 +1100         
88562  response  2022-03-23 16:17:36 +1100    2022-03-28 09:47:07 +1100  waiting_response  incoming  
89101  status_update  2022-03-28 09:47:07 +1100  waiting_response  2022-03-28 09:47:07 +1100  waiting_response   
89325  response  2022-03-30 15:24:34 +1100    2024-10-01 01:38:11 +1000  partially_successful  incoming  
117830  edit  2022-10-01 03:45:15 +1000         
117831  edit  2022-10-01 03:45:15 +1000         
117832  edit  2022-10-01 03:45:15 +1000         
117833  edit  2022-10-01 03:45:15 +1000         
117834  edit  2022-10-01 03:45:15 +1000         
117835  edit  2022-10-01 03:45:15 +1000         
117836  edit  2022-10-01 03:45:15 +1000         
117837  edit  2022-10-01 03:45:15 +1000         
117838  edit  2022-10-01 03:45:15 +1000         
244420  edit  2024-03-31 03:45:14 +1100         
244421  edit  2024-03-31 03:45:14 +1100         
244422  edit  2024-03-31 03:45:14 +1100         
244423  edit  2024-03-31 03:45:14 +1100         
244424  edit  2024-03-31 03:45:14 +1100         
244425  edit  2024-03-31 03:45:14 +1100         
244426  edit  2024-03-31 03:45:14 +1100         
244427  edit  2024-03-31 03:45:14 +1100         
244428  edit  2024-03-31 03:45:14 +1100         
244429  edit  2024-03-31 03:45:14 +1100         
244430  edit  2024-03-31 03:45:14 +1100         
244431  edit  2024-03-31 03:45:14 +1100         
244432  edit  2024-03-31 03:45:14 +1100         
244433  edit  2024-03-31 03:45:14 +1100         
244434  edit  2024-03-31 03:45:15 +1100         
244435  edit  2024-03-31 03:45:15 +1100         
244436  edit  2024-03-31 03:45:15 +1100         
244437  edit  2024-03-31 03:45:15 +1100         
301006  status_update  2024-10-01 01:38:11 +1000  partially_successful  2024-10-01 01:38:11 +1000  partially_successful   

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.