Details of request “List of information requests to the department

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
20169 sent 2016-12-02 09:49:04 +1100 waiting_response 2016-12-02 09:49:05 +1100 waiting_response outgoing
20338 response 2016-12-07 16:21:25 +1100 incoming
20504 response 2016-12-09 11:44:47 +1100 2016-12-31 17:59:19 +1100 waiting_clarification incoming
21165 status_update 2016-12-31 17:59:19 +1100 waiting_clarification 2016-12-31 17:59:19 +1100 waiting_clarification
21166 comment 2016-12-31 18:07:58 +1100
21877 followup_sent 2017-01-23 17:38:25 +1100 waiting_response 2017-01-23 17:38:25 +1100 waiting_response outgoing
22041 response 2017-01-30 13:35:04 +1100 2017-01-31 08:20:32 +1100 waiting_clarification incoming
22072 status_update 2017-01-31 08:20:32 +1100 waiting_clarification 2017-01-31 08:20:32 +1100 waiting_clarification
22074 followup_sent 2017-01-31 08:24:44 +1100 waiting_response 2017-01-31 08:24:44 +1100 waiting_response outgoing
22075 response 2017-01-31 08:25:12 +1100 2017-02-08 14:33:42 +1100 waiting_response incoming
22226 status_update 2017-02-03 11:38:07 +1100 error_message 2017-02-03 11:38:07 +1100 error_message
22357 comment 2017-02-07 18:12:43 +1100
22383 followup_resent 2017-02-08 14:33:01 +1100 outgoing
22384 edit 2017-02-08 14:33:42 +1100 waiting_response 2017-02-08 14:33:42 +1100 waiting_response
22385 response 2017-02-08 14:41:16 +1100 2017-02-21 11:52:25 +1100 waiting_clarification incoming
22386 comment 2017-02-08 14:50:06 +1100
22912 status_update 2017-02-21 11:52:24 +1100 waiting_clarification 2017-02-21 11:52:25 +1100 waiting_clarification
23722 followup_sent 2017-03-15 16:34:41 +1100 waiting_response 2017-03-15 16:34:41 +1100 waiting_response outgoing
23805 response 2017-03-17 10:46:36 +1100 2017-03-17 11:36:46 +1100 waiting_response incoming
23812 followup_sent 2017-03-17 11:36:40 +1100 outgoing
23813 status_update 2017-03-17 11:36:46 +1100 waiting_response 2017-03-17 11:36:46 +1100 waiting_response
24351 followup_sent 2017-03-30 12:03:04 +1100 outgoing
24695 response 2017-04-07 12:46:07 +1000 2017-04-08 20:33:55 +1000 waiting_response incoming
24723 followup_sent 2017-04-08 20:33:47 +1000 outgoing
24724 status_update 2017-04-08 20:33:55 +1000 waiting_response 2017-04-08 20:33:55 +1000 waiting_response
24882 response 2017-04-13 13:46:29 +1000 2017-04-14 13:57:22 +1000 successful incoming
24912 status_update 2017-04-14 13:57:22 +1000 successful 2017-04-14 13:57:22 +1000 successful
24913 followup_sent 2017-04-14 14:15:38 +1000 outgoing

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.