Details of request “Report on the operations of APSC

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
200989  sent  2023-10-19 14:10:59 +1100  waiting_response  2023-10-19 14:10:59 +1100  waiting_response  outgoing  
202144  response  2023-10-20 14:07:43 +1100        incoming  
211145  response  2023-11-20 11:56:25 +1100        incoming  
216312  followup_sent  2023-12-16 10:16:48 +1100  internal_review  2023-12-16 10:16:49 +1100  internal_review  outgoing  
218011  response  2023-12-22 10:53:43 +1100        incoming  
224354  response  2024-01-18 21:45:16 +1100        incoming  
226675  response  2024-01-29 11:32:16 +1100    2024-02-13 12:00:31 +1100  rejected  incoming  
229880  status_update  2024-02-13 12:00:31 +1100  rejected  2024-02-13 12:00:31 +1100  rejected   
229881  response  2024-02-13 12:13:00 +1100    2024-02-13 12:16:21 +1100  rejected  incoming  
229882  status_update  2024-02-13 12:16:21 +1100  rejected  2024-02-13 12:16:21 +1100  rejected   
229884  response  2024-02-13 12:20:18 +1100    2024-02-13 12:22:00 +1100  rejected  incoming  
229885  status_update  2024-02-13 12:21:59 +1100  rejected  2024-02-13 12:22:00 +1100  rejected   
229886  followup_sent  2024-02-13 12:23:55 +1100        outgoing  
238952  response  2024-03-08 14:06:46 +1100    2024-03-14 17:17:08 +1100  rejected  incoming  
240061  status_update  2024-03-14 17:17:08 +1100  rejected  2024-03-14 17:17:08 +1100  rejected   
261431  response  2024-05-27 17:53:28 +1000        incoming  
263306  response  2024-06-06 10:43:14 +1000        incoming  
266420  response  2024-06-12 16:11:10 +1000    2024-06-12 18:39:37 +1000  rejected  incoming  
266435  followup_sent  2024-06-12 18:39:06 +1000        outgoing  
266436  status_update  2024-06-12 18:39:37 +1000  rejected  2024-06-12 18:39:37 +1000  rejected   
266437  followup_sent  2024-06-12 18:48:27 +1000        outgoing  
269629  response  2024-06-27 19:17:33 +1000        incoming  
273923  response  2024-07-12 14:53:57 +1000    2024-07-20 17:03:29 +1000  partially_successful  incoming  
275671  status_update  2024-07-20 17:03:29 +1000  partially_successful  2024-07-20 17:03:29 +1000  partially_successful   
308033  response  2024-10-25 14:57:21 +1100        incoming  
309022  followup_sent  2024-10-28 18:20:03 +1100        outgoing  
309480  response  2024-10-30 10:23:12 +1100    2024-11-05 20:24:50 +1100  partially_successful  incoming  
311005  followup_sent  2024-11-05 20:24:05 +1100        outgoing  
311006  status_update  2024-11-05 20:24:50 +1100  partially_successful  2024-11-05 20:24:50 +1100  partially_successful   
311839  response  2024-11-08 14:11:56 +1100        incoming  

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.