Details of request “FOI charges letters

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
301343  sent  2024-10-01 17:59:25 +1000  waiting_response  2024-10-01 17:59:25 +1000  waiting_response  outgoing  
303121  response  2024-10-08 19:17:02 +1100    2024-10-08 20:22:30 +1100  waiting_response  incoming  
303122  status_update  2024-10-08 20:22:30 +1100  waiting_response  2024-10-08 20:22:30 +1100  waiting_response   
303125  followup_sent  2024-10-08 21:23:30 +1100        outgoing  
305644  response  2024-10-14 19:45:51 +1100    2024-10-14 23:35:09 +1100  waiting_response  incoming  
305647  followup_sent  2024-10-14 23:35:04 +1100        outgoing  
305648  status_update  2024-10-14 23:35:09 +1100  waiting_response  2024-10-14 23:35:09 +1100  waiting_response   
305879  response  2024-10-15 12:23:58 +1100    2024-10-15 12:49:15 +1100  waiting_response  incoming  
305881  followup_sent  2024-10-15 12:49:11 +1100        outgoing  
305882  status_update  2024-10-15 12:49:15 +1100  waiting_response  2024-10-15 12:49:15 +1100  waiting_response   
305900  response  2024-10-15 16:47:07 +1100    2024-10-15 17:36:50 +1100  waiting_response  incoming  
305903  followup_sent  2024-10-15 17:36:26 +1100        outgoing  
305904  status_update  2024-10-15 17:36:50 +1100  waiting_response  2024-10-15 17:36:50 +1100  waiting_response   
307370  response  2024-10-22 19:43:51 +1100        incoming  
307372  response  2024-10-22 20:49:01 +1100    2024-10-22 22:33:40 +1100  waiting_response  incoming  
307373  followup_sent  2024-10-22 22:33:35 +1100        outgoing  
307374  status_update  2024-10-22 22:33:39 +1100  waiting_response  2024-10-22 22:33:40 +1100  waiting_response   
307582  followup_sent  2024-10-23 23:10:17 +1100        outgoing  
308032  response  2024-10-25 13:40:37 +1100    2024-10-25 14:58:50 +1100  waiting_response  incoming  
308035  status_update  2024-10-25 14:58:50 +1100  waiting_response  2024-10-25 14:58:50 +1100  waiting_response   
309292  response  2024-10-29 19:30:31 +1100    2024-10-30 09:18:29 +1100  waiting_response  incoming  
309473  status_update  2024-10-30 09:18:29 +1100  waiting_response  2024-10-30 09:18:29 +1100  waiting_response   
310014  overdue  2024-11-01 00:00:00 +1100         
311634  response  2024-11-07 21:26:20 +1100        incoming  
311635  response  2024-11-07 22:03:59 +1100        incoming  
311810  response  2024-11-08 08:58:25 +1100    2024-11-08 09:16:47 +1100  successful  incoming  
311813  status_update  2024-11-08 09:16:47 +1100  successful  2024-11-08 09:16:47 +1100  successful   
311814  followup_sent  2024-11-08 09:56:54 +1100        outgoing  

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.