Details of request “Accident report and apology

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
52301  sent  2020-12-20 12:14:30 +1100  waiting_response  2020-12-20 12:14:30 +1100  waiting_response  outgoing  
52302  response  2020-12-20 12:14:54 +1100    2020-12-20 12:28:50 +1100  waiting_response  incoming  
52303  status_update  2020-12-20 12:28:50 +1100  waiting_response  2020-12-20 12:28:50 +1100  waiting_response   
52305  comment  2020-12-20 12:32:47 +1100         
52359  response  2020-12-23 16:00:27 +1100    2022-09-16 13:50:03 +1000  waiting_response  incoming  
52419  status_update  2020-12-25 13:43:02 +1100  not_held  2020-12-25 13:43:02 +1100  not_held   
64916  edit  2021-06-26 03:45:11 +1000         
64917  edit  2021-06-26 03:45:11 +1000         
64918  edit  2021-06-26 03:45:11 +1000         
64919  edit  2021-06-26 03:45:11 +1000         
64920  edit  2021-06-26 03:45:11 +1000         
64921  edit  2021-06-26 03:45:11 +1000         
115279  status_update  2022-09-16 13:50:02 +1000  waiting_response  2022-09-16 13:50:03 +1000  waiting_response   
115280  followup_sent  2022-09-16 13:57:52 +1000  internal_review  2022-09-16 13:57:52 +1000  internal_review  outgoing  
115281  response  2022-09-16 13:58:18 +1000    2022-09-20 08:21:09 +1000  waiting_response  incoming  
115283  followup_sent  2022-09-16 14:28:29 +1000        outgoing  
116025  status_update  2022-09-20 08:21:09 +1000  waiting_response  2022-09-20 08:21:09 +1000  waiting_response   
117800  response  2022-09-30 12:39:27 +1000    2022-10-01 09:04:56 +1000  not_held  incoming  
117997  status_update  2022-10-01 09:04:56 +1000  not_held  2022-10-01 09:04:56 +1000  not_held   
117998  status_update  2022-10-01 09:06:18 +1000  not_held  2022-10-01 09:06:18 +1000  not_held   
151507  edit  2023-04-01 03:45:14 +1100         
151508  edit  2023-04-01 03:45:15 +1100         
151509  edit  2023-04-01 03:45:15 +1100         
151510  edit  2023-04-01 03:45:15 +1100         
151511  edit  2023-04-01 03:45:15 +1100         
151512  edit  2023-04-01 03:45:15 +1100         
151513  edit  2023-04-01 03:45:15 +1100         
151514  edit  2023-04-01 03:45:15 +1100         
151515  edit  2023-04-01 03:45:15 +1100         
151516  edit  2023-04-01 03:45:15 +1100         
151517  edit  2023-04-01 03:45:15 +1100         
151518  edit  2023-04-01 03:45:15 +1100         
151519  edit  2023-04-01 03:45:15 +1100         
151520  edit  2023-04-01 03:45:15 +1100         
151521  edit  2023-04-01 03:45:15 +1100         
151522  edit  2023-04-01 03:45:15 +1100         
151523  edit  2023-04-01 03:45:15 +1100         
151524  edit  2023-04-01 03:45:15 +1100         
151525  edit  2023-04-01 03:45:15 +1100         
151526  edit  2023-04-01 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.