Details of request “Crown Resorts visa applications agreement

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
40976  sent  2019-07-30 23:12:26 +1000  waiting_response  2019-07-30 23:12:26 +1000  waiting_response  outgoing  
40977  response  2019-07-30 23:13:42 +1000    2019-07-30 23:16:08 +1000  waiting_response  incoming  
40978  status_update  2019-07-30 23:16:08 +1000  waiting_response  2019-07-30 23:16:08 +1000  waiting_response   
40979  response  2019-07-31 08:56:06 +1000    2019-08-01 19:11:19 +1000  waiting_response  incoming  
41038  status_update  2019-08-01 19:11:19 +1000  waiting_response  2019-08-01 19:11:19 +1000  waiting_response   
41421  response  2019-08-29 08:55:36 +1000    2019-08-31 20:06:14 +1000  waiting_response  incoming  
54639  overdue  2019-08-30 00:00:00 +1000         
41496  status_update  2019-08-31 20:06:14 +1000  waiting_response  2019-08-31 20:06:14 +1000  waiting_response   
41497  followup_sent  2019-08-31 23:45:21 +1000        outgoing  
41498  status_update  2019-08-31 23:45:41 +1000  waiting_response  2019-08-31 23:45:41 +1000  waiting_response   
41857  followup_sent  2019-09-25 22:18:59 +1000        outgoing  
41873  response  2019-09-26 16:15:40 +1000    2019-09-30 13:58:03 +1000  waiting_response  incoming  
41917  status_update  2019-09-30 13:58:03 +1000  waiting_response  2019-09-30 13:58:03 +1000  waiting_response   
56331  very_overdue  2019-10-02 00:00:00 +1000         
42629  followup_sent  2019-10-29 19:17:18 +1100        outgoing  
43533  followup_sent  2019-12-03 00:37:16 +1100        outgoing  
43785  response  2019-12-13 11:24:36 +1100    2019-12-14 16:48:11 +1100  waiting_response  incoming  
43811  status_update  2019-12-14 16:48:11 +1100  waiting_response  2019-12-14 16:48:11 +1100  waiting_response   
44762  followup_sent  2020-02-01 15:56:00 +1100        outgoing  
44842  response  2020-02-05 16:13:27 +1100    2020-02-08 17:54:25 +1100  partially_successful  incoming  
44903  status_update  2020-02-08 17:54:25 +1100  partially_successful  2020-02-08 17:54:25 +1100  partially_successful   
44904  followup_sent  2020-02-08 18:48:56 +1100  internal_review  2020-02-08 18:48:56 +1100  internal_review  outgoing  
44905  response  2020-02-08 18:50:22 +1100    2020-02-08 18:57:33 +1100  internal_review  incoming  
44906  status_update  2020-02-08 18:57:32 +1100  internal_review  2020-02-08 18:57:33 +1100  internal_review   
44927  response  2020-02-10 13:44:07 +1100    2020-02-11 23:19:34 +1100  internal_review  incoming  
44950  status_update  2020-02-11 23:19:34 +1100  internal_review  2020-02-11 23:19:34 +1100  internal_review   
45091  response  2020-02-18 15:38:10 +1100    2020-02-19 14:23:57 +1100  internal_review  incoming  
45119  status_update  2020-02-19 14:23:57 +1100  internal_review  2020-02-19 14:23:57 +1100  internal_review   
45120  followup_sent  2020-02-19 14:29:32 +1100        outgoing  
61396  comment  2021-04-28 00:57:50 +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.