Details of request “FOI Request: Perpetual Centrelink Calendar 107-03040000

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
21393 sent 2017-01-09 19:13:20 +1100 waiting_response 2017-01-09 19:13:20 +1100 waiting_response outgoing
21583 response 2017-01-16 11:35:00 +1100 2017-01-20 07:49:52 +1100 waiting_response incoming
21803 status_update 2017-01-20 07:49:51 +1100 waiting_response 2017-01-20 07:49:52 +1100 waiting_response
22087 response 2017-01-31 16:58:09 +1100 2017-02-07 18:45:28 +1100 waiting_response incoming
22358 status_update 2017-02-07 18:45:27 +1100 waiting_response 2017-02-07 18:45:28 +1100 waiting_response
22501 followup_sent 2017-02-10 21:28:19 +1100 outgoing
22516 comment 2017-02-11 18:48:34 +1100
23581 followup_sent 2017-03-12 14:27:33 +1100 internal_review 2017-03-12 14:27:33 +1100 internal_review outgoing
23779 response 2017-03-16 17:37:44 +1100 2017-03-17 07:33:21 +1100 internal_review incoming
23794 followup_sent 2017-03-16 22:16:39 +1100 outgoing
23795 followup_sent 2017-03-17 07:15:08 +1100 outgoing
23796 status_update 2017-03-17 07:33:20 +1100 internal_review 2017-03-17 07:33:21 +1100 internal_review
23862 response 2017-03-19 07:59:27 +1100 2017-03-26 18:50:44 +1100 internal_review incoming
23871 comment 2017-03-19 13:49:04 +1100
23879 comment 2017-03-19 15:32:14 +1100
23880 comment 2017-03-19 20:33:24 +1100
24147 comment 2017-03-25 16:13:53 +1100
24161 comment 2017-03-26 13:00:29 +1100
24165 status_update 2017-03-26 18:50:44 +1100 internal_review 2017-03-26 18:50:44 +1100 internal_review
25549 comment 2017-05-06 08:38:26 +1000
25827 response 2017-05-15 19:18:03 +1000 incoming
25868 followup_sent 2017-05-16 09:09:33 +1000 outgoing
25963 followup_sent 2017-05-19 07:05:51 +1000 outgoing
26009 response 2017-05-19 17:51:55 +1000 2017-05-19 19:10:46 +1000 internal_review incoming
26010 status_update 2017-05-19 19:10:46 +1000 internal_review 2017-05-19 19:10:46 +1000 internal_review
26012 followup_sent 2017-05-19 19:32:36 +1000 outgoing
26013 followup_sent 2017-05-19 20:30:08 +1000 outgoing
26110 comment 2017-05-22 20:49:13 +1000
26642 response 2017-06-09 12:26:45 +1000 2017-06-09 12:38:59 +1000 internal_review incoming
26644 followup_sent 2017-06-09 12:38:53 +1000 outgoing
26645 status_update 2017-06-09 12:38:59 +1000 internal_review 2017-06-09 12:38:59 +1000 internal_review
26648 response 2017-06-09 16:32:26 +1000 incoming
26656 comment 2017-06-10 10:46:01 +1000
26701 followup_sent 2017-06-14 07:51:01 +1000 outgoing
26703 comment 2017-06-14 07:53:04 +1000
27054 response 2017-06-26 14:11:43 +1000 incoming
27055 response 2017-06-26 14:12:47 +1000 incoming
27056 response 2017-06-26 14:13:21 +1000 incoming
27057 response 2017-06-26 14:13:51 +1000 incoming
27058 response 2017-06-26 14:14:16 +1000 incoming
27060 response 2017-06-26 14:15:00 +1000 incoming
27061 response 2017-06-26 14:19:03 +1000 incoming
27062 response 2017-06-26 14:19:43 +1000 incoming
27063 response 2017-06-26 14:20:42 +1000 incoming
27064 response 2017-06-26 14:21:22 +1000 incoming
27065 response 2017-06-26 14:21:59 +1000 2018-10-11 20:53:02 +1100 partially_successful incoming
27266 status_update 2017-07-04 10:18:07 +1000 internal_review 2017-07-04 10:18:08 +1000 internal_review
27270 followup_sent 2017-07-04 11:53:50 +1000 outgoing
31554 comment 2018-01-21 14:31:56 +1100
35597 status_update 2018-10-11 20:53:02 +1100 partially_successful 2018-10-11 20:53:02 +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.