Details of request “recorded audio/visual proceedings of morning and afternoon forums by PBA on 29/09 21

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
72734  sent  2021-10-15 17:39:59 +1100  waiting_response  2021-10-15 17:39:59 +1100  waiting_response  outgoing  
72970  response  2021-10-18 17:50:16 +1100    2021-10-22 09:30:19 +1100  waiting_response  incoming  
73224  status_update  2021-10-22 09:30:19 +1100  waiting_response  2021-10-22 09:30:19 +1100  waiting_response   
73588  response  2021-10-28 18:39:15 +1100    2021-10-30 20:05:00 +1100  waiting_response  incoming  
73698  status_update  2021-10-30 20:04:59 +1100  waiting_response  2021-10-30 20:05:00 +1100  waiting_response   
74626  response  2021-11-15 13:00:06 +1100    2021-11-17 16:16:50 +1100  requires_admin  incoming  
74842  status_update  2021-11-17 16:03:44 +1100  waiting_response  2021-11-17 16:03:44 +1100  waiting_response   
74843  status_update  2021-11-17 16:16:49 +1100  requires_admin  2021-11-17 16:16:50 +1100  requires_admin   
76608  response  2021-12-13 13:14:03 +1100    2021-12-16 08:30:29 +1100  successful  incoming  
76872  status_update  2021-12-16 08:28:14 +1100  rejected  2021-12-16 08:28:14 +1100  rejected   
76873  status_update  2021-12-16 08:30:29 +1100  successful  2021-12-16 08:30:29 +1100  successful   
99458  edit  2022-06-16 03:45:15 +1000         
99459  edit  2022-06-16 03:45:15 +1000         
99460  edit  2022-06-16 03:45:15 +1000         
99461  edit  2022-06-16 03:45:15 +1000         
99462  edit  2022-06-16 03:45:15 +1000         
99463  edit  2022-06-16 03:45:15 +1000         
99464  edit  2022-06-16 03:45:15 +1000         
99465  edit  2022-06-16 03:45:15 +1000         
99466  edit  2022-06-16 03:45:15 +1000         
99467  edit  2022-06-16 03:45:15 +1000         
99468  edit  2022-06-16 03:45:15 +1000         
216183  edit  2023-12-16 03:45:22 +1100         
216184  edit  2023-12-16 03:45:22 +1100         
216185  edit  2023-12-16 03:45:22 +1100         
216186  edit  2023-12-16 03:45:22 +1100         
216187  edit  2023-12-16 03:45:22 +1100         
216188  edit  2023-12-16 03:45:22 +1100         
216189  edit  2023-12-16 03:45:22 +1100         
216190  edit  2023-12-16 03:45:23 +1100         
216191  edit  2023-12-16 03:45:23 +1100         
216192  edit  2023-12-16 03:45:23 +1100         
216193  edit  2023-12-16 03:45:23 +1100         
216194  edit  2023-12-16 03:45:23 +1100         
216195  edit  2023-12-16 03:45:23 +1100         
216196  edit  2023-12-16 03:45:23 +1100         
216197  edit  2023-12-16 03:45:23 +1100         
216198  edit  2023-12-16 03:45:23 +1100         
216199  edit  2023-12-16 03:45:23 +1100         
216200  edit  2023-12-16 03:45:23 +1100         
216201  edit  2023-12-16 03:45:23 +1100         
216202  edit  2023-12-16 03:45:23 +1100         
216203  edit  2023-12-16 03:45:23 +1100         
216204  edit  2023-12-16 03:45:23 +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.