Details of request “MATES program

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
215702  sent  2023-12-13 11:34:35 +1100  waiting_response  2023-12-13 11:34:35 +1100  waiting_response  outgoing  
215703  response  2023-12-13 11:34:48 +1100    2023-12-13 13:00:40 +1100  waiting_response  incoming  
215707  status_update  2023-12-13 13:00:40 +1100  waiting_response  2023-12-13 13:00:40 +1100  waiting_response   
215922  response  2023-12-14 13:55:59 +1100    2023-12-14 14:14:20 +1100  waiting_response  incoming  
215923  status_update  2023-12-14 14:14:19 +1100  waiting_response  2023-12-14 14:14:20 +1100  waiting_response   
215924  followup_sent  2023-12-14 14:17:08 +1100        outgoing  
215925  response  2023-12-14 14:17:22 +1100    2023-12-14 14:54:29 +1100  waiting_response  incoming  
215927  status_update  2023-12-14 14:54:29 +1100  waiting_response  2023-12-14 14:54:29 +1100  waiting_response   
222178  overdue  2024-01-13 00:00:00 +1100         
222179  followup_sent  2024-01-13 13:13:12 +1100        outgoing  
225793  response  2024-01-23 15:57:18 +1100    2024-02-03 18:15:33 +1100  successful  incoming  
227810  status_update  2024-02-03 18:15:33 +1100  successful  2024-02-03 18:15:33 +1100  successful   
229583  response  2024-02-12 16:43:31 +1100    2024-02-23 23:08:53 +1100  attention_requested  incoming  
234271  status_update  2024-02-23 15:47:13 +1100  rejected  2024-02-23 15:47:13 +1100  rejected   
234277  report_request  2024-02-23 23:08:53 +1100  attention_requested       
235712  response  2024-02-27 10:31:35 +1100    2024-02-27 11:09:11 +1100  rejected  incoming  
235713  status_update  2024-02-27 11:09:11 +1100  rejected  2024-02-27 11:09:11 +1100  rejected   
291354  edit  2024-08-28 03:45:15 +1000         
291355  edit  2024-08-28 03:45:15 +1000         
291356  edit  2024-08-28 03:45:15 +1000         
291357  edit  2024-08-28 03:45:15 +1000         
291358  edit  2024-08-28 03:45:15 +1000         
291359  edit  2024-08-28 03:45:15 +1000         
291360  edit  2024-08-28 03:45:15 +1000         
291361  edit  2024-08-28 03:45:15 +1000         
291362  edit  2024-08-28 03:45:15 +1000         
291363  edit  2024-08-28 03:45:15 +1000         
291364  edit  2024-08-28 03:45:15 +1000         
291365  edit  2024-08-28 03:45:15 +1000         
291366  edit  2024-08-28 03:45:15 +1000         
291367  edit  2024-08-28 03:45:15 +1000         
291368  edit  2024-08-28 03:45:15 +1000         
291369  edit  2024-08-28 03:45:15 +1000         
291370  edit  2024-08-28 03:45:15 +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.