Details of request “Number of protection claims before or at immigration clearance

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
37078  sent  2018-11-28 09:29:24 +1100  waiting_response  2018-11-28 09:29:24 +1100  waiting_response  outgoing  
37079  response  2018-11-28 09:30:07 +1100    2018-11-28 09:31:08 +1100  waiting_response  incoming  
37081  status_update  2018-11-28 09:31:08 +1100  waiting_response  2018-11-28 09:31:08 +1100  waiting_response   
54492  overdue  2018-12-29 00:00:00 +1100         
37758  followup_sent  2019-01-02 05:28:14 +1100        outgoing  
37759  response  2019-01-02 05:30:17 +1100    2019-01-02 05:31:27 +1100  waiting_response  incoming  
37760  status_update  2019-01-02 05:31:27 +1100  waiting_response  2019-01-02 05:31:27 +1100  waiting_response   
37761  response  2019-01-02 09:47:17 +1100    2019-01-19 08:35:01 +1100  waiting_response  incoming  
38105  status_update  2019-01-19 08:35:00 +1100  waiting_response  2019-01-19 08:35:01 +1100  waiting_response   
38106  followup_sent  2019-01-19 08:36:08 +1100        outgoing  
38107  response  2019-01-19 08:38:02 +1100        incoming  
38115  response  2019-01-21 09:17:43 +1100    2019-02-01 07:44:42 +1100  waiting_response  incoming  
56244  very_overdue  2019-01-30 00:00:00 +1100         
38255  status_update  2019-02-01 07:44:42 +1100  waiting_response  2019-02-01 07:44:42 +1100  waiting_response   
38274  followup_sent  2019-02-02 07:23:42 +1100  internal_review  2019-02-02 07:23:42 +1100  internal_review  outgoing  
38275  response  2019-02-02 07:24:47 +1100    2019-03-14 10:52:33 +1100  internal_review  incoming  
38977  status_update  2019-03-14 10:52:33 +1100  internal_review  2019-03-14 10:52:33 +1100  internal_review   
39243  followup_sent  2019-04-01 12:32:22 +1100        outgoing  
39244  response  2019-04-01 12:35:35 +1100    2019-04-03 12:07:31 +1100  internal_review  incoming  
39254  comment  2019-04-01 22:48:40 +1100         
39306  status_update  2019-04-03 12:07:31 +1100  internal_review  2019-04-03 12:07:31 +1100  internal_review   
39321  response  2019-04-04 09:21:09 +1100    2019-05-06 14:49:00 +1000  internal_review  incoming  
39967  status_update  2019-05-06 14:49:00 +1000  internal_review  2019-05-06 14:49:00 +1000  internal_review   
39968  comment  2019-05-06 14:50:41 +1000         
40278  response  2019-05-28 09:17:51 +1000    2019-06-01 08:23:07 +1000  not_held  incoming  
40346  status_update  2019-06-01 08:23:07 +1000  not_held  2019-06-01 08:23:07 +1000  not_held   

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.