Details of request “Information related to employment of 457 visa holders

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
24655  sent  2017-04-06 11:50:28 +1000  waiting_response  2017-04-06 11:50:28 +1000  waiting_response  outgoing  
24676  comment  2017-04-06 22:05:02 +1000         
24779  response  2017-04-10 18:01:10 +1000    2017-04-10 18:37:08 +1000  waiting_response  incoming  
24780  followup_sent  2017-04-10 18:35:48 +1000        outgoing  
24781  status_update  2017-04-10 18:36:03 +1000  waiting_clarification  2017-04-10 18:36:03 +1000  waiting_clarification   
24782  status_update  2017-04-10 18:36:53 +1000  waiting_clarification  2017-04-10 18:36:53 +1000  waiting_clarification   
24783  status_update  2017-04-10 18:37:08 +1000  waiting_response  2017-04-10 18:37:08 +1000  waiting_response   
24786  followup_sent  2017-04-10 18:40:20 +1000        outgoing  
24832  response  2017-04-11 18:58:49 +1000    2017-04-12 07:49:15 +1000  waiting_clarification  incoming  
24838  status_update  2017-04-12 07:49:15 +1000  waiting_clarification  2017-04-12 07:49:15 +1000  waiting_clarification   
24839  followup_sent  2017-04-12 07:57:03 +1000  waiting_response  2017-04-12 07:57:03 +1000  waiting_response  outgoing  
24840  response  2017-04-12 07:57:49 +1000    2017-04-12 08:06:06 +1000  waiting_response  incoming  
24841  status_update  2017-04-12 08:06:06 +1000  waiting_response  2017-04-12 08:06:06 +1000  waiting_response   
25043  response  2017-04-18 18:13:17 +1000    2017-04-29 15:22:41 +1000  waiting_clarification  incoming  
25366  status_update  2017-04-29 15:22:41 +1000  waiting_clarification  2017-04-29 15:22:41 +1000  waiting_clarification   
25367  followup_sent  2017-04-29 15:27:25 +1000  waiting_response  2017-04-29 15:27:25 +1000  waiting_response  outgoing  
25442  response  2017-05-03 08:21:08 +1000    2017-05-09 10:28:15 +1000  waiting_response  incoming  
25603  followup_sent  2017-05-09 10:28:06 +1000        outgoing  
25604  status_update  2017-05-09 10:28:15 +1000  waiting_response  2017-05-09 10:28:15 +1000  waiting_response   
25908  followup_sent  2017-05-17 18:01:21 +1000        outgoing  
26126  followup_sent  2017-05-23 10:51:30 +1000        outgoing  
26129  response  2017-05-23 11:05:39 +1000    2017-07-12 12:10:38 +1000  partially_successful  incoming  
26132  status_update  2017-05-23 11:20:06 +1000  waiting_response  2017-05-23 11:20:06 +1000  waiting_response   
53921  overdue  2017-05-30 00:00:00 +1000         
55831  very_overdue  2017-06-29 00:00:00 +1000         
27435  status_update  2017-07-12 12:10:38 +1000  partially_successful  2017-07-12 12:10:38 +1000  partially_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.