Details of request “Correspondence

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
127945  sent  2022-11-28 17:24:17 +1100  waiting_response  2022-11-28 17:24:17 +1100  waiting_response  outgoing  
127946  response  2022-11-28 17:24:23 +1100    2022-11-30 15:46:42 +1100  waiting_response  incoming  
127948  status_update  2022-11-28 17:40:23 +1100  error_message  2022-11-28 17:40:23 +1100  error_message   
128157  resent  2022-11-30 15:46:42 +1100  waiting_response      outgoing  
128158  resent  2022-11-30 15:47:19 +1100  waiting_response      outgoing  
128654  response  2022-12-02 18:19:30 +1100    2022-12-05 12:06:00 +1100  waiting_clarification  incoming  
129098  status_update  2022-12-05 12:06:00 +1100  waiting_clarification  2022-12-05 12:06:00 +1100  waiting_clarification   
129099  followup_sent  2022-12-05 12:06:55 +1100  waiting_response  2022-12-05 12:06:55 +1100  waiting_response  outgoing  
134193  overdue  2023-01-05 00:00:00 +1100         
141736  very_overdue  2023-02-04 00:00:00 +1100         
162846  edit  2023-06-06 03:45:23 +1000         
162847  edit  2023-06-06 03:45:23 +1000         
162848  edit  2023-06-06 03:45:23 +1000         
162849  edit  2023-06-06 03:45:23 +1000         
162850  edit  2023-06-06 03:45:23 +1000         
162851  edit  2023-06-06 03:45:23 +1000         
162852  edit  2023-06-06 03:45:23 +1000         
162853  edit  2023-06-06 03:45:23 +1000         
162854  edit  2023-06-06 03:45:23 +1000         
162855  edit  2023-06-06 03:45:24 +1000         
322337  edit  2024-12-06 03:46:21 +1100         
322338  edit  2024-12-06 03:46:21 +1100         
322339  edit  2024-12-06 03:46:22 +1100         
322340  edit  2024-12-06 03:46:22 +1100         
322341  edit  2024-12-06 03:46:22 +1100         
322342  edit  2024-12-06 03:46:22 +1100         
322343  edit  2024-12-06 03:46:22 +1100         
322344  edit  2024-12-06 03:46:22 +1100         
322345  edit  2024-12-06 03:46:22 +1100         
322346  edit  2024-12-06 03:46:22 +1100         
322347  edit  2024-12-06 03:46:22 +1100         
322348  edit  2024-12-06 03:46:22 +1100         
322349  edit  2024-12-06 03:46:22 +1100         
322350  edit  2024-12-06 03:46:22 +1100         
322351  edit  2024-12-06 03:46:22 +1100         
322352  edit  2024-12-06 03:46:22 +1100         
322353  edit  2024-12-06 03:46:22 +1100         
322354  edit  2024-12-06 03:46:22 +1100         
322355  edit  2024-12-06 03:46:22 +1100         
322356  edit  2024-12-06 03:46: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.