Details of request “Documentation provided to schools for My Mind Check

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
392880  sent  2025-06-16 12:40:36 +1000  waiting_response  2025-06-16 12:40:36 +1000  waiting_response  outgoing  
392881  response  2025-06-16 12:40:59 +1000        incoming  
392882  response  2025-06-16 12:41:02 +1000        incoming  
397496  response  2025-06-26 14:42:51 +1000    2025-06-30 09:41:33 +1000  waiting_response  incoming  
398548  status_update  2025-06-30 09:41:33 +1000  waiting_response  2025-06-30 09:41:33 +1000  waiting_response   
400452  response  2025-07-04 16:13:28 +1000    2025-07-04 17:04:28 +1000  waiting_response  incoming  
400458  status_update  2025-07-04 17:04:28 +1000  waiting_response  2025-07-04 17:04:28 +1000  waiting_response   
403404  response  2025-07-11 15:39:56 +1000    2025-07-12 10:31:35 +1000  waiting_response  incoming  
404459  status_update  2025-07-12 10:31:35 +1000  waiting_response  2025-07-12 10:31:35 +1000  waiting_response   
404460  followup_sent  2025-07-12 10:36:13 +1000        outgoing  
404461  response  2025-07-12 10:36:35 +1000        incoming  
404462  response  2025-07-12 10:36:41 +1000    2025-07-12 10:45:11 +1000  waiting_response  incoming  
404463  status_update  2025-07-12 10:45:11 +1000  waiting_response  2025-07-12 10:45:11 +1000  waiting_response   
404635  status_update  2025-07-13 08:55:55 +1000  waiting_response  2025-07-13 08:55:55 +1000  waiting_response   
405799  overdue  2025-07-17 00:00:00 +1000         
409876  response  2025-07-25 13:56:07 +1000    2025-07-26 14:40:36 +1000  waiting_response  incoming  
410015  status_update  2025-07-26 14:40:34 +1000  waiting_response  2025-07-26 14:40:36 +1000  waiting_response   
410793  followup_sent  2025-07-28 09:27:31 +1000        outgoing  
410794  response  2025-07-28 09:27:55 +1000        incoming  
411253  response  2025-07-30 16:11:19 +1000    2025-07-30 16:49:03 +1000  waiting_response  incoming  
411258  status_update  2025-07-30 16:49:03 +1000  waiting_response  2025-07-30 16:49:03 +1000  waiting_response   
415044  followup_sent  2025-08-12 17:29:51 +1000        outgoing  
415045  response  2025-08-12 17:30:27 +1000    2025-08-12 17:35:33 +1000  waiting_response  incoming  
415046  status_update  2025-08-12 17:35:33 +1000  waiting_response  2025-08-12 17:35:33 +1000  waiting_response   
416112  response  2025-08-13 11:12:38 +1000    2025-08-19 09:59:02 +1000  waiting_response  incoming  
419732  very_overdue  2025-08-16 00:00:00 +1000         
419555  status_update  2025-08-19 09:59:02 +1000  waiting_response  2025-08-19 09:59:02 +1000  waiting_response   
423071  response  2025-08-29 15:56:09 +1000    2025-09-02 08:19:17 +1000  successful  incoming  
423932  status_update  2025-09-02 08:19:17 +1000  successful  2025-09-02 08:19:17 +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.