Details of request “Communication and documentation regarding process, consultation and decision making with respect to the staging on the New Year’s Eve Party

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
434073  sent  2025-10-09 08:13:00 +1100  waiting_response  2025-10-09 08:13:00 +1100  waiting_response  outgoing  
434074  response  2025-10-09 08:13:35 +1100        incoming  
435191  response  2025-10-14 17:41:17 +1100        incoming  
440263  response  2025-10-30 17:10:12 +1100    2025-12-05 20:03:15 +1100  waiting_response  incoming  
452487  overdue  2025-11-07 00:00:00 +1100         
452713  overdue  2025-11-07 00:00:00 +1100         
452945  overdue  2025-11-07 00:00:00 +1100         
453239  overdue  2025-11-07 00:00:00 +1100         
453460  overdue  2025-11-07 00:00:00 +1100         
453698  overdue  2025-11-07 00:00:00 +1100         
453906  overdue  2025-11-07 00:00:00 +1100         
454188  overdue  2025-11-07 00:00:00 +1100         
454418  overdue  2025-11-07 00:00:00 +1100         
454784  overdue  2025-11-07 00:00:00 +1100         
455005  overdue  2025-11-07 00:00:00 +1100         
455185  overdue  2025-11-07 00:00:00 +1100         
455403  overdue  2025-11-07 00:00:00 +1100         
455839  overdue  2025-11-07 00:00:00 +1100         
456014  overdue  2025-11-07 00:00:00 +1100         
456260  overdue  2025-11-07 00:00:00 +1100         
456490  overdue  2025-11-07 00:00:00 +1100         
456666  overdue  2025-11-07 00:00:00 +1100         
456856  overdue  2025-11-07 00:00:00 +1100         
457031  overdue  2025-11-07 00:00:00 +1100         
457330  overdue  2025-11-07 00:00:00 +1100         
457658  overdue  2025-11-07 00:00:00 +1100         
457814  overdue  2025-11-07 00:00:00 +1100         
457990  overdue  2025-11-07 00:00:00 +1100         
458398  overdue  2025-11-07 00:00:00 +1100         
458610  overdue  2025-11-07 00:00:00 +1100         
458825  overdue  2025-11-07 00:00:00 +1100         
459103  overdue  2025-11-07 00:00:00 +1100         
459468  overdue  2025-11-07 00:00:00 +1100         
459622  overdue  2025-11-07 00:00:00 +1100         
460004  overdue  2025-11-07 00:00:00 +1100         
460243  overdue  2025-11-07 00:00:00 +1100         
460470  overdue  2025-11-07 00:00:00 +1100         
460645  overdue  2025-11-07 00:00:00 +1100         
461822  overdue  2025-11-07 00:00:00 +1100         
462060  overdue  2025-11-07 00:00:00 +1100         
452257  status_update  2025-12-05 20:03:15 +1100  waiting_response  2025-12-05 20:03:15 +1100  waiting_response   
453241  very_overdue  2025-12-09 00:00:00 +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.