Details of request “Submissions & Outcomes arising from the Proposed Pilot of a Private/Community Refugee Sponsorship Program Discussion Paper

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
32902  sent  2018-05-02 17:33:46 +1000  waiting_response  2018-05-02 17:33:47 +1000  waiting_response  outgoing  
32903  response  2018-05-02 17:34:57 +1000    2018-05-02 17:36:02 +1000  waiting_response  incoming  
32904  status_update  2018-05-02 17:36:02 +1000  waiting_response  2018-05-02 17:36:02 +1000  waiting_response   
32990  response  2018-05-10 10:43:05 +1000    2018-05-10 12:23:08 +1000  waiting_response  incoming  
32991  status_update  2018-05-10 12:23:07 +1000  waiting_response  2018-05-10 12:23:08 +1000  waiting_response   
54294  overdue  2018-06-02 00:00:00 +1000         
33712  followup_sent  2018-06-21 15:47:28 +1000        outgoing  
56088  very_overdue  2018-07-03 00:00:00 +1000         
34888  response  2018-09-10 16:17:35 +1000    2018-09-20 09:05:22 +1000  waiting_clarification  incoming  
35028  followup_sent  2018-09-15 00:13:09 +1000        outgoing  
35137  status_update  2018-09-20 09:05:22 +1000  waiting_clarification  2018-09-20 09:05:22 +1000  waiting_clarification   
35201  followup_sent  2018-09-24 12:02:35 +1000  waiting_response  2018-09-24 12:02:35 +1000  waiting_response  outgoing  
35241  response  2018-09-26 16:47:54 +1000    2018-09-28 13:33:32 +1000  waiting_clarification  incoming  
35326  followup_sent  2018-09-28 13:33:21 +1000        outgoing  
35327  status_update  2018-09-28 13:33:32 +1000  waiting_clarification  2018-09-28 13:33:32 +1000  waiting_clarification   
35333  response  2018-09-28 16:08:28 +1000        incoming  
35335  response  2018-09-28 16:12:16 +1000    2018-10-23 12:35:00 +1100  waiting_clarification  incoming  
35859  status_update  2018-10-23 12:35:00 +1100  waiting_clarification  2018-10-23 12:35:00 +1100  waiting_clarification   
35863  followup_sent  2018-10-23 12:45:15 +1100  waiting_response  2018-10-23 12:45:15 +1100  waiting_response  outgoing  
36174  response  2018-11-05 09:18:56 +1100        incoming  
36732  response  2018-11-19 15:41:39 +1100        incoming  
36758  response  2018-11-20 09:21:05 +1100        incoming  
37212  response  2018-12-03 15:24:59 +1100        incoming  
37264  response  2018-12-05 10:32:33 +1100    2019-02-11 12:42:29 +1100  partially_successful  incoming  
38470  status_update  2019-02-11 12:42:29 +1100  partially_successful  2019-02-11 12:42:29 +1100  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.