Details of request “Historical Debts Potentially Affected by Income Apportionment

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
309000  sent  2024-10-28 14:21:12 +1100  waiting_response  2024-10-28 14:21:12 +1100  waiting_response  outgoing  
309001  response  2024-10-28 14:21:41 +1100    2024-11-05 19:29:37 +1100  waiting_response  incoming  
311001  status_update  2024-11-05 19:29:37 +1100  waiting_response  2024-11-05 19:29:37 +1100  waiting_response   
311272  response  2024-11-06 16:52:37 +1100    2024-11-06 19:09:35 +1100  waiting_clarification  incoming  
311277  followup_sent  2024-11-06 19:09:27 +1100        outgoing  
311278  status_update  2024-11-06 19:09:35 +1100  waiting_clarification  2024-11-06 19:09:35 +1100  waiting_clarification   
311279  response  2024-11-06 19:10:13 +1100        incoming  
311817  response  2024-11-08 10:08:46 +1100    2024-11-17 15:41:19 +1100  waiting_response  incoming  
313783  status_update  2024-11-17 15:41:19 +1100  waiting_response  2024-11-17 15:41:19 +1100  waiting_response   
313784  followup_sent  2024-11-17 15:42:43 +1100        outgoing  
313785  response  2024-11-17 15:43:18 +1100        incoming  
317143  response  2024-11-27 14:47:01 +1100    2024-11-27 15:34:47 +1100  successful  incoming  
317144  status_update  2024-11-27 15:34:47 +1100  successful  2024-11-27 15:34:47 +1100  successful   
386713  destroy_incoming  2025-05-29 10:26:30 +1000         
386714  destroy_incoming  2025-05-29 10:26:30 +1000         
386715  destroy_incoming  2025-05-29 10:26:30 +1000         
386716  destroy_incoming  2025-05-29 10:26:31 +1000         
386717  destroy_incoming  2025-05-29 10:26:31 +1000         
386718  destroy_incoming  2025-05-29 10:26:31 +1000         
386719  destroy_incoming  2025-05-29 10:26:31 +1000         
386875  edit  2025-05-29 15:38:38 +1000         
386876  destroy_incoming  2025-05-29 15:38:56 +1000         
386877  destroy_incoming  2025-05-29 15:38:56 +1000         
386878  destroy_incoming  2025-05-29 15:38:56 +1000         
386879  destroy_incoming  2025-05-29 15:38:57 +1000         
386880  destroy_incoming  2025-05-29 15:38:57 +1000         
386881  destroy_incoming  2025-05-29 15:38:57 +1000         
386882  destroy_incoming  2025-05-29 15:38:57 +1000         
386883  destroy_incoming  2025-05-29 15:38:57 +1000         
386884  destroy_incoming  2025-05-29 15:38:57 +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.