Details of request “Does the NDIA’s proposed reliance on Salesforce guarantee PROTECTED data classification and ensure NDIS data remains exclusively restricted to Australia only?

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
64081  sent  2021-06-11 18:57:34 +1000  waiting_response  2021-06-11 18:57:34 +1000  waiting_response  outgoing  
64082  response  2021-06-11 18:57:56 +1000    2021-06-11 18:58:04 +1000  waiting_response  incoming  
64083  status_update  2021-06-11 18:58:04 +1000  waiting_response  2021-06-11 18:58:04 +1000  waiting_response   
65234  response  2021-06-28 18:49:00 +1000    2021-07-06 16:50:20 +1000  waiting_response  incoming  
65626  followup_sent  2021-07-06 16:50:16 +1000        outgoing  
65627  status_update  2021-07-06 16:50:20 +1000  waiting_response  2021-07-06 16:50:20 +1000  waiting_response   
65899  response  2021-07-11 17:09:24 +1000    2021-07-18 09:10:50 +1000  error_message  incoming  
66459  status_update  2021-07-18 09:10:50 +1000  error_message  2021-07-18 09:10:50 +1000  error_message   
67505  response  2021-07-30 16:43:11 +1000    2021-07-31 15:06:07 +1000  not_held  incoming  
67548  status_update  2021-07-31 15:06:07 +1000  not_held  2021-07-31 15:06:07 +1000  not_held   
68727  comment  2021-08-17 03:55:19 +1000         
80752  edit  2022-02-01 03:45:19 +1100         
80753  edit  2022-02-01 03:45:19 +1100         
80754  edit  2022-02-01 03:45:19 +1100         
80755  edit  2022-02-01 03:45:19 +1100         
80756  edit  2022-02-01 03:45:19 +1100         
80757  edit  2022-02-01 03:45:19 +1100         
80758  edit  2022-02-01 03:45:19 +1100         
80759  edit  2022-02-01 03:45:19 +1100         
80760  edit  2022-02-01 03:45:19 +1100         
80761  edit  2022-02-01 03:45:19 +1100         
80762  edit  2022-02-01 03:45:20 +1100         
172853  edit  2023-08-01 03:45:20 +1000         
172854  edit  2023-08-01 03:45:20 +1000         
172855  edit  2023-08-01 03:45:20 +1000         
172856  edit  2023-08-01 03:45:20 +1000         
172857  edit  2023-08-01 03:45:20 +1000         
172858  edit  2023-08-01 03:45:20 +1000         
172859  edit  2023-08-01 03:45:20 +1000         
172860  edit  2023-08-01 03:45:20 +1000         
172861  edit  2023-08-01 03:45:20 +1000         
172862  edit  2023-08-01 03:45:20 +1000         
172863  edit  2023-08-01 03:45:20 +1000         
172864  edit  2023-08-01 03:45:20 +1000         
172865  edit  2023-08-01 03:45:20 +1000         
172866  edit  2023-08-01 03:45:20 +1000         
172867  edit  2023-08-01 03:45:20 +1000         
172868  edit  2023-08-01 03:45:20 +1000         
172869  edit  2023-08-01 03:45:20 +1000         
172870  edit  2023-08-01 03:45:20 +1000         
172871  edit  2023-08-01 03:45:20 +1000         
172872  edit  2023-08-01 03:45:20 +1000         
172873  edit  2023-08-01 03:45:20 +1000         
172874  edit  2023-08-01 03:45:20 +1000         

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.