Details of request “Privacy Impact Assessment ref 43996 Document Lodgement Machine Learning System Pilots

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
90962  sent  2022-04-11 10:22:29 +1000  waiting_response  2022-04-11 10:22:30 +1000  waiting_response  outgoing  
90963  response  2022-04-11 10:22:42 +1000    2022-04-11 10:27:31 +1000  waiting_response  incoming  
90964  status_update  2022-04-11 10:27:31 +1000  waiting_response  2022-04-11 10:27:31 +1000  waiting_response   
90968  followup_sent  2022-04-11 10:47:04 +1000        outgoing  
91098  response  2022-04-12 17:18:24 +1000    2022-04-12 17:40:21 +1000  waiting_response  incoming  
91101  status_update  2022-04-12 17:40:21 +1000  waiting_response  2022-04-12 17:40:21 +1000  waiting_response   
93482  response  2022-04-29 16:38:46 +1000    2022-05-03 08:44:43 +1000  waiting_response  incoming  
94133  status_update  2022-05-03 08:44:42 +1000  waiting_response  2022-05-03 08:44:43 +1000  waiting_response   
95383  overdue  2022-05-12 00:00:00 +1000         
98902  response  2022-06-10 16:49:26 +1000    2022-06-13 08:39:39 +1000  rejected  incoming  
99250  very_overdue  2022-06-11 00:00:00 +1000         
99152  status_update  2022-06-13 08:39:38 +1000  rejected  2022-06-13 08:39:39 +1000  rejected   
99153  followup_sent  2022-06-13 08:53:10 +1000  internal_review  2022-06-13 08:53:10 +1000  internal_review  outgoing  
99154  response  2022-06-13 08:53:22 +1000    2022-06-14 10:02:39 +1000  internal_review  incoming  
99156  status_update  2022-06-13 08:55:30 +1000  waiting_response  2022-06-13 08:55:30 +1000  waiting_response   
99263  status_update  2022-06-14 10:02:38 +1000  internal_review  2022-06-14 10:02:39 +1000  internal_review   
103702  response  2022-07-13 17:06:19 +1000    2022-07-13 18:41:08 +1000  rejected  incoming  
103707  status_update  2022-07-13 18:41:08 +1000  rejected  2022-07-13 18:41:08 +1000  rejected   
135633  edit  2023-01-14 03:45:15 +1100         
135634  edit  2023-01-14 03:45:15 +1100         
135635  edit  2023-01-14 03:45:15 +1100         
135636  edit  2023-01-14 03:45:15 +1100         
135637  edit  2023-01-14 03:45:15 +1100         
135638  edit  2023-01-14 03:45:15 +1100         
135639  edit  2023-01-14 03:45:15 +1100         
135640  edit  2023-01-14 03:45:15 +1100         
135641  edit  2023-01-14 03:45:15 +1100         
135642  edit  2023-01-14 03:45:15 +1100         
135643  edit  2023-01-14 03:45:15 +1100         
135644  edit  2023-01-14 03:45:15 +1100         
135645  edit  2023-01-14 03:45:15 +1100         
135646  edit  2023-01-14 03:45:15 +1100         
135647  edit  2023-01-14 03:45:15 +1100         
135648  edit  2023-01-14 03:45:15 +1100         
135649  edit  2023-01-14 03:45:15 +1100         
135650  edit  2023-01-14 03:45:15 +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.