Details of request “NDIA’s ‘risk management framework’ for the financial year 2019-20

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
64291  sent  2021-06-14 12:03:14 +1000  waiting_response  2021-06-14 12:03:14 +1000  waiting_response  outgoing  
64292  response  2021-06-14 12:03:27 +1000    2021-06-14 12:03:43 +1000  waiting_response  incoming  
64293  status_update  2021-06-14 12:03:43 +1000  waiting_response  2021-06-14 12:03:43 +1000  waiting_response   
65046  response  2021-06-28 18:46:22 +1000        incoming  
65048  response  2021-06-28 18:46:22 +1000        incoming  
65050  response  2021-06-28 18:46:22 +1000        incoming  
65052  response  2021-06-28 18:46:22 +1000        incoming  
65054  response  2021-06-28 18:46:22 +1000        incoming  
65081  response  2021-06-28 18:46:31 +1000        incoming  
65088  response  2021-06-28 18:46:32 +1000        incoming  
65089  response  2021-06-28 18:46:32 +1000    2021-07-06 17:20:57 +1000  waiting_response  incoming  
65706  followup_sent  2021-07-06 17:20:53 +1000        outgoing  
65707  status_update  2021-07-06 17:20:57 +1000  waiting_response  2021-07-06 17:20:57 +1000  waiting_response   
65712  comment  2021-07-06 22:45:56 +1000         
65931  response  2021-07-11 17:39:10 +1000    2022-05-08 15:56:54 +1000  rejected  incoming  
66410  status_update  2021-07-17 16:14:51 +1000  error_message  2021-07-17 16:14:51 +1000  error_message   
68581  status_update  2021-08-15 18:42:07 +1000  error_message  2021-08-15 18:42:07 +1000  error_message   
72902  status_update  2021-10-17 18:15:35 +1100  error_message  2021-10-17 18:15:35 +1100  error_message   
79524  edit  2022-01-18 03:45:26 +1100         
79525  edit  2022-01-18 03:45:26 +1100         
79526  edit  2022-01-18 03:45:26 +1100         
79527  edit  2022-01-18 03:45:26 +1100         
79528  edit  2022-01-18 03:45:26 +1100         
79529  edit  2022-01-18 03:45:26 +1100         
79530  edit  2022-01-18 03:45:26 +1100         
79531  edit  2022-01-18 03:45:26 +1100         
79532  edit  2022-01-18 03:45:26 +1100         
79533  edit  2022-01-18 03:45:26 +1100         
79534  edit  2022-01-18 03:45:26 +1100         
79535  edit  2022-01-18 03:45:26 +1100         
79536  edit  2022-01-18 03:45:26 +1100         
79537  edit  2022-01-18 03:45:26 +1100         
79538  edit  2022-01-18 03:45:26 +1100         
79539  edit  2022-01-18 03:45:26 +1100         
79540  edit  2022-01-18 03:45:26 +1100         
79541  edit  2022-01-18 03:45:26 +1100         
94852  status_update  2022-05-08 15:56:54 +1000  rejected  2022-05-08 15:56:54 +1000  rejected   

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.