Details of request “Budget preparation

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
161535  sent  2023-05-30 15:04:57 +1000  waiting_response  2023-05-30 15:04:57 +1000  waiting_response  outgoing  
161536  response  2023-05-30 15:05:29 +1000    2023-06-01 09:56:01 +1000  waiting_response  incoming  
161758  status_update  2023-06-01 09:56:01 +1000  waiting_response  2023-06-01 09:56:01 +1000  waiting_response   
161962  response  2023-06-02 14:04:53 +1000    2023-06-05 15:36:57 +1000  waiting_response  incoming  
162601  status_update  2023-06-05 15:36:56 +1000  waiting_response  2023-06-05 15:36:57 +1000  waiting_response   
164192  response  2023-06-14 13:17:55 +1000    2023-06-19 16:57:55 +1000  waiting_response  incoming  
165024  followup_sent  2023-06-19 16:57:40 +1000        outgoing  
165025  status_update  2023-06-19 16:57:55 +1000  waiting_response  2023-06-19 16:57:55 +1000  waiting_response   
165636  response  2023-06-22 17:52:36 +1000    2023-07-04 16:12:45 +1000  waiting_clarification  incoming  
167198  status_update  2023-07-04 16:12:45 +1000  waiting_clarification  2023-07-04 16:12:45 +1000  waiting_clarification   
167199  followup_sent  2023-07-04 16:14:53 +1000  internal_review  2023-07-04 16:14:53 +1000  internal_review  outgoing  
167200  response  2023-07-04 16:16:21 +1000    2023-07-06 11:56:40 +1000  waiting_response  incoming  
167695  status_update  2023-07-06 11:56:40 +1000  waiting_response  2023-07-06 11:56:40 +1000  waiting_response   
173074  response  2023-08-02 16:16:55 +1000    2023-08-16 10:47:17 +1000  user_withdrawn  incoming  
177131  status_update  2023-08-16 10:46:22 +1000  waiting_response  2023-08-16 10:46:22 +1000  waiting_response   
177132  followup_sent  2023-08-16 10:46:52 +1000        outgoing  
177133  status_update  2023-08-16 10:47:17 +1000  user_withdrawn  2023-08-16 10:47:17 +1000  user_withdrawn   
177150  response  2023-08-16 17:14:23 +1000        incoming  
230844  edit  2024-02-17 03:45:15 +1100         
230845  edit  2024-02-17 03:45:15 +1100         
230846  edit  2024-02-17 03:45:15 +1100         
230847  edit  2024-02-17 03:45:15 +1100         
230848  edit  2024-02-17 03:45:15 +1100         
230849  edit  2024-02-17 03:45:16 +1100         
230850  edit  2024-02-17 03:45:16 +1100         
230851  edit  2024-02-17 03:45:16 +1100         
230852  edit  2024-02-17 03:45:16 +1100         
230853  edit  2024-02-17 03:45:16 +1100         
230854  edit  2024-02-17 03:45:16 +1100         
230855  edit  2024-02-17 03:45:16 +1100         
230856  edit  2024-02-17 03:45:16 +1100         
230857  edit  2024-02-17 03:45:16 +1100         
230858  edit  2024-02-17 03:45:16 +1100         
230859  edit  2024-02-17 03:45:16 +1100         
230860  edit  2024-02-17 03:45:16 +1100         
230861  edit  2024-02-17 03:45:16 +1100         

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.