Details of request “NDIA Risk Management Consultancies: 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
63767  sent  2021-06-09 02:27:32 +1000  waiting_response  2021-06-09 02:27:32 +1000  waiting_response  outgoing  
63768  response  2021-06-09 02:27:44 +1000    2021-06-09 02:29:28 +1000  waiting_response  incoming  
63769  status_update  2021-06-09 02:29:28 +1000  waiting_response  2021-06-09 02:29:28 +1000  waiting_response   
64787  response  2021-06-23 17:34:16 +1000        incoming  
64789  response  2021-06-23 17:34:17 +1000        incoming  
64790  response  2021-06-23 17:34:17 +1000        incoming  
64796  response  2021-06-23 17:34:17 +1000        incoming  
64799  response  2021-06-23 17:34:17 +1000    2021-10-17 18:02:20 +1100  rejected  incoming  
64869  status_update  2021-06-24 17:10:21 +1000  waiting_response  2021-06-24 17:10:21 +1000  waiting_response   
65847  overdue  2021-07-10 00:00:00 +1000         
68212  very_overdue  2021-08-10 00:00:00 +1000         
72875  status_update  2021-10-17 18:02:20 +1100  rejected  2021-10-17 18:02:20 +1100  rejected   
91716  edit  2022-04-18 03:45:17 +1000         
91717  edit  2022-04-18 03:45:17 +1000         
91718  edit  2022-04-18 03:45:17 +1000         
91719  edit  2022-04-18 03:45:17 +1000         
91720  edit  2022-04-18 03:45:17 +1000         
91721  edit  2022-04-18 03:45:17 +1000         
91722  edit  2022-04-18 03:45:17 +1000         
91723  edit  2022-04-18 03:45:17 +1000         
91724  edit  2022-04-18 03:45:17 +1000         
91725  edit  2022-04-18 03:45:17 +1000         
91726  edit  2022-04-18 03:45:17 +1000         
91727  edit  2022-04-18 03:45:17 +1000         
200212  edit  2023-10-18 03:45:21 +1100         
200213  edit  2023-10-18 03:45:21 +1100         
200214  edit  2023-10-18 03:45:21 +1100         
200215  edit  2023-10-18 03:45:22 +1100         
200216  edit  2023-10-18 03:45:22 +1100         
200217  edit  2023-10-18 03:45:22 +1100         
200218  edit  2023-10-18 03:45:22 +1100         
200219  edit  2023-10-18 03:45:22 +1100         
200220  edit  2023-10-18 03:45:22 +1100         
200221  edit  2023-10-18 03:45:22 +1100         
200222  edit  2023-10-18 03:45:22 +1100         
200223  edit  2023-10-18 03:45:22 +1100         
200224  edit  2023-10-18 03:45:22 +1100         
200225  edit  2023-10-18 03:45:22 +1100         
200226  edit  2023-10-18 03:45:22 +1100         
200227  edit  2023-10-18 03:45:22 +1100         
200228  edit  2023-10-18 03:45:22 +1100         
200229  edit  2023-10-18 03:45:22 +1100         
200230  edit  2023-10-18 03:45:22 +1100         
200231  edit  2023-10-18 03:45:22 +1100         
200232  edit  2023-10-18 03:45:22 +1100         
200233  edit  2023-10-18 03:45:22 +1100         
200234  edit  2023-10-18 03:45:22 +1100         
200235  edit  2023-10-18 03:45:22 +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.