Details of request “Documents pertaining to recent explosion of debt recovery requests

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
21135 sent 2016-12-28 23:02:29 +1100 waiting_response 2016-12-28 23:02:29 +1100 waiting_response outgoing
21136 response 2016-12-28 23:02:58 +1100 2016-12-28 23:11:12 +1100 waiting_response incoming
21137 status_update 2016-12-28 23:11:12 +1100 waiting_response 2016-12-28 23:11:12 +1100 waiting_response
21238 response 2017-01-04 16:27:36 +1100 2017-01-04 17:20:58 +1100 waiting_response incoming
21239 followup_sent 2017-01-04 17:20:53 +1100 outgoing
21240 status_update 2017-01-04 17:20:58 +1100 waiting_response 2017-01-04 17:20:58 +1100 waiting_response
21268 response 2017-01-05 14:23:01 +1100 2017-01-05 14:57:24 +1100 waiting_response incoming
21271 followup_sent 2017-01-05 14:57:21 +1100 outgoing
21272 status_update 2017-01-05 14:57:24 +1100 waiting_response 2017-01-05 14:57:24 +1100 waiting_response
21423 response 2017-01-11 14:15:19 +1100 incoming
21476 response 2017-01-12 17:28:16 +1100 2017-01-16 10:44:27 +1100 waiting_response incoming
21484 followup_sent 2017-01-12 20:30:10 +1100 outgoing
21485 status_update 2017-01-12 20:30:17 +1100 waiting_clarification 2017-01-12 20:30:18 +1100 waiting_clarification
21579 status_update 2017-01-16 10:44:27 +1100 waiting_response 2017-01-16 10:44:27 +1100 waiting_response
21610 response 2017-01-16 17:56:52 +1100 2017-01-17 11:44:36 +1100 waiting_response incoming
21628 followup_sent 2017-01-17 11:44:32 +1100 outgoing
21629 status_update 2017-01-17 11:44:36 +1100 waiting_response 2017-01-17 11:44:36 +1100 waiting_response
21630 response 2017-01-17 11:45:00 +1100 2017-01-18 16:58:09 +1100 waiting_response incoming
21715 status_update 2017-01-18 16:58:09 +1100 waiting_response 2017-01-18 16:58:09 +1100 waiting_response
21770 response 2017-01-19 15:01:07 +1100 2017-01-20 01:33:53 +1100 waiting_response incoming
21802 status_update 2017-01-20 01:33:52 +1100 waiting_response 2017-01-20 01:33:53 +1100 waiting_response
22798 response 2017-02-17 16:57:30 +1100 2017-02-17 17:42:27 +1100 rejected incoming
22800 status_update 2017-02-17 17:42:26 +1100 rejected 2017-02-17 17:42:27 +1100 rejected
22812 comment 2017-02-17 20:42:17 +1100

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.