Details of request “Priorities in relation to Australia’s offshore humanitarian 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
39090 sent 2019-03-22 10:35:45 +1100 waiting_response 2019-03-22 10:35:45 +1100 waiting_response outgoing
39091 response 2019-03-22 10:37:03 +1100 2019-03-22 10:51:38 +1100 waiting_response incoming
39105 status_update 2019-03-22 10:51:38 +1100 waiting_response 2019-03-22 10:51:38 +1100 waiting_response
39142 response 2019-03-26 13:17:01 +1100 2019-03-26 13:52:30 +1100 waiting_response incoming
39144 status_update 2019-03-26 13:52:30 +1100 waiting_response 2019-03-26 13:52:30 +1100 waiting_response
39686 followup_sent 2019-04-25 10:42:47 +1000 outgoing
40195 followup_sent 2019-05-22 08:49:53 +1000 outgoing
40786 followup_sent 2019-07-15 16:43:43 +1000 internal_review 2019-07-15 16:43:43 +1000 internal_review outgoing
40791 response 2019-07-15 16:45:19 +1000 2019-07-31 11:19:40 +1000 waiting_response incoming
40983 status_update 2019-07-31 11:17:01 +1000 rejected 2019-07-31 11:17:01 +1000 rejected
40985 status_update 2019-07-31 11:19:39 +1000 waiting_response 2019-07-31 11:19:39 +1000 waiting_response
40994 followup_sent 2019-07-31 11:28:26 +1000 outgoing
40998 response 2019-07-31 11:30:48 +1000 2019-07-31 11:33:10 +1000 waiting_response incoming
41006 status_update 2019-07-31 11:33:10 +1000 waiting_response 2019-07-31 11:33:10 +1000 waiting_response
42531 response 2019-10-26 11:56:31 +1100 incoming
42532 response 2019-10-26 11:57:33 +1100 incoming
42533 response 2019-10-26 11:58:19 +1100 2019-11-06 15:06:09 +1100 partially_successful incoming
42853 status_update 2019-11-06 15:06:09 +1100 partially_successful 2019-11-06 15:06:09 +1100 partially_successful
43415 response 2019-11-26 10:35:09 +1100 incoming
43417 response 2019-11-26 10:57:05 +1100 incoming
43722 followup_sent 2019-12-11 12:45:05 +1100 internal_review 2019-12-11 12:45:05 +1100 internal_review outgoing
43723 response 2019-12-11 12:46:38 +1100 2019-12-11 13:37:47 +1100 internal_review incoming
43728 status_update 2019-12-11 13:37:47 +1100 internal_review 2019-12-11 13:37:47 +1100 internal_review
43760 response 2019-12-12 11:04:19 +1100 2019-12-12 16:55:21 +1100 internal_review incoming
43772 status_update 2019-12-12 16:55:21 +1100 internal_review 2019-12-12 16:55:21 +1100 internal_review
43774 followup_sent 2019-12-12 16:57:50 +1100 outgoing
43789 response 2019-12-13 12:28:47 +1100 2020-06-09 12:23:30 +1000 partially_successful incoming
43908 status_update 2019-12-17 19:07:26 +1100 internal_review 2019-12-17 19:07:26 +1100 internal_review
46881 status_update 2020-06-09 12:23:30 +1000 partially_successful 2020-06-09 12:23:30 +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.