Details of request “NDIA Risk Management Declaration: 2014

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
63771  sent  2021-06-09 02:44:56 +1000  waiting_response  2021-06-09 02:44:56 +1000  waiting_response  outgoing  
63772  response  2021-06-09 02:45:10 +1000    2021-06-09 03:28:59 +1000  waiting_response  incoming  
63773  status_update  2021-06-09 03:28:59 +1000  waiting_response  2021-06-09 03:28:59 +1000  waiting_response   
64792  response  2021-06-23 17:34:17 +1000        incoming  
64793  response  2021-06-23 17:34:17 +1000        incoming  
64795  response  2021-06-23 17:34:17 +1000        incoming  
64801  response  2021-06-23 17:34:17 +1000        incoming  
64802  response  2021-06-23 17:34:17 +1000    2021-10-17 18:03:27 +1100  rejected  incoming  
64868  status_update  2021-06-24 17:09:48 +1000  waiting_response  2021-06-24 17:09:48 +1000  waiting_response   
65848  overdue  2021-07-10 00:00:00 +1000         
68213  very_overdue  2021-08-10 00:00:00 +1000         
72876  status_update  2021-10-17 18:03:27 +1100  rejected  2021-10-17 18:03:27 +1100  rejected   
91728  edit  2022-04-18 03:45:17 +1000         
91729  edit  2022-04-18 03:45:17 +1000         
91730  edit  2022-04-18 03:45:17 +1000         
91731  edit  2022-04-18 03:45:17 +1000         
91732  edit  2022-04-18 03:45:17 +1000         
91733  edit  2022-04-18 03:45:17 +1000         
91734  edit  2022-04-18 03:45:17 +1000         
91735  edit  2022-04-18 03:45:17 +1000         
91736  edit  2022-04-18 03:45:17 +1000         
91737  edit  2022-04-18 03:45:18 +1000         
91738  edit  2022-04-18 03:45:18 +1000         
91739  edit  2022-04-18 03:45:18 +1000         
200236  edit  2023-10-18 03:45:22 +1100         
200237  edit  2023-10-18 03:45:23 +1100         
200238  edit  2023-10-18 03:45:23 +1100         
200239  edit  2023-10-18 03:45:23 +1100         
200240  edit  2023-10-18 03:45:23 +1100         
200241  edit  2023-10-18 03:45:23 +1100         
200242  edit  2023-10-18 03:45:23 +1100         
200243  edit  2023-10-18 03:45:23 +1100         
200244  edit  2023-10-18 03:45:23 +1100         
200245  edit  2023-10-18 03:45:23 +1100         
200246  edit  2023-10-18 03:45:23 +1100         
200247  edit  2023-10-18 03:45:23 +1100         
200248  edit  2023-10-18 03:45:23 +1100         
200249  edit  2023-10-18 03:45:23 +1100         
200250  edit  2023-10-18 03:45:23 +1100         
200251  edit  2023-10-18 03:45:23 +1100         
200252  edit  2023-10-18 03:45:23 +1100         
200253  edit  2023-10-18 03:45:23 +1100         
200254  edit  2023-10-18 03:45:23 +1100         
200255  edit  2023-10-18 03:45:23 +1100         
200256  edit  2023-10-18 03:45:23 +1100         
200257  edit  2023-10-18 03:45:23 +1100         
200258  edit  2023-10-18 03:45:23 +1100         
200259  edit  2023-10-18 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.