Details of request “communication with DSS over National Autism Strategy

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
394679  sent  2025-06-19 14:31:39 +1000  waiting_response  2025-06-19 14:31:39 +1000  waiting_response  outgoing  
394680  response  2025-06-19 14:32:05 +1000        incoming  
394681  response  2025-06-19 14:32:06 +1000    2025-06-19 16:53:10 +1000  waiting_response  incoming  
394687  status_update  2025-06-19 16:53:10 +1000  waiting_response  2025-06-19 16:53:10 +1000  waiting_response   
399180  response  2025-07-02 10:45:47 +1000    2025-07-02 10:58:12 +1000  waiting_response  incoming  
399182  status_update  2025-07-02 10:58:12 +1000  waiting_response  2025-07-02 10:58:12 +1000  waiting_response   
402878  response  2025-07-09 17:18:10 +1000    2025-07-09 17:31:03 +1000  waiting_response  incoming  
402881  followup_sent  2025-07-09 17:30:57 +1000        outgoing  
402882  status_update  2025-07-09 17:31:02 +1000  waiting_response  2025-07-09 17:31:02 +1000  waiting_response   
402883  response  2025-07-09 17:31:35 +1000        incoming  
402884  response  2025-07-09 17:31:37 +1000    2025-07-09 18:26:32 +1000  waiting_response  incoming  
402888  status_update  2025-07-09 18:26:31 +1000  waiting_response  2025-07-09 18:26:32 +1000  waiting_response   
403408  response  2025-07-11 17:05:24 +1000    2025-07-17 16:00:26 +1000  waiting_response  incoming  
405822  followup_sent  2025-07-17 16:00:06 +1000        outgoing  
405823  status_update  2025-07-17 16:00:25 +1000  waiting_response  2025-07-17 16:00:26 +1000  waiting_response   
405824  response  2025-07-17 16:00:28 +1000    2025-07-17 16:00:51 +1000  waiting_response  incoming  
405825  status_update  2025-07-17 16:00:51 +1000  waiting_response  2025-07-17 16:00:51 +1000  waiting_response   
406018  response  2025-07-18 10:56:10 +1000    2025-08-12 07:49:19 +1000  waiting_response  incoming  
416107  overdue  2025-07-22 00:00:00 +1000         
415009  followup_sent  2025-08-12 07:49:13 +1000        outgoing  
415010  status_update  2025-08-12 07:49:19 +1000  waiting_response  2025-08-12 07:49:19 +1000  waiting_response   
415011  response  2025-08-12 07:49:37 +1000    2025-08-12 07:50:15 +1000  waiting_response  incoming  
415012  status_update  2025-08-12 07:50:15 +1000  waiting_response  2025-08-12 07:50:15 +1000  waiting_response   
417381  response  2025-08-14 17:34:53 +1000        incoming  
417383  response  2025-08-14 17:53:06 +1000    2025-08-15 08:40:20 +1000  successful  incoming  
417649  status_update  2025-08-15 08:40:19 +1000  successful  2025-08-15 08:40:20 +1000  successful   

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.