Details of request “Requests for amendment to 2015-16 financial disclosures

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
21906 sent 2017-01-24 17:51:42 +1100 waiting_response 2017-01-24 17:51:42 +1100 waiting_response outgoing
21907 response 2017-01-24 17:52:11 +1100 2017-01-24 17:53:04 +1100 waiting_response incoming
21908 status_update 2017-01-24 17:53:04 +1100 waiting_response 2017-01-24 17:53:04 +1100 waiting_response
21917 response 2017-01-25 08:41:17 +1100 incoming
21919 comment 2017-01-25 10:29:59 +1100
21928 comment 2017-01-25 11:38:25 +1100
21956 response 2017-01-25 17:16:23 +1100 2017-01-25 17:39:10 +1100 waiting_response incoming
21959 followup_sent 2017-01-25 17:39:04 +1100 outgoing
21960 status_update 2017-01-25 17:39:10 +1100 waiting_response 2017-01-25 17:39:10 +1100 waiting_response
21968 response 2017-01-26 11:30:42 +1100 2017-01-26 11:35:05 +1100 waiting_response incoming
21969 status_update 2017-01-26 11:35:05 +1100 waiting_response 2017-01-26 11:35:05 +1100 waiting_response
23051 followup_sent 2017-02-24 11:43:47 +1100 outgoing
23070 response 2017-02-24 15:35:20 +1100 2017-02-24 16:29:16 +1100 waiting_response incoming
23080 status_update 2017-02-24 16:29:16 +1100 waiting_response 2017-02-24 16:29:16 +1100 waiting_response
23088 followup_sent 2017-02-24 17:07:01 +1100 outgoing
23180 response 2017-02-28 11:21:18 +1100 incoming
23181 response 2017-02-28 11:23:34 +1100 incoming
23182 response 2017-02-28 11:24:27 +1100 2017-02-28 12:28:53 +1100 partially_successful incoming
23190 status_update 2017-02-28 12:28:53 +1100 partially_successful 2017-02-28 12:28:53 +1100 partially_successful
23192 followup_sent 2017-02-28 12:45:48 +1100 outgoing
23194 response 2017-02-28 13:20:29 +1100 2017-03-01 11:37:54 +1100 successful incoming
23247 status_update 2017-03-01 11:37:53 +1100 successful 2017-03-01 11:37:54 +1100 successful
23893 response 2017-03-20 10:45:49 +1100 2017-03-20 12:25:22 +1100 successful incoming
23898 edit 2017-03-20 11:22:35 +1100
23899 destroy_incoming 2017-03-20 11:27:18 +1100
23900 edit 2017-03-20 11:36:30 +1100
23902 edit_incoming 2017-03-20 12:07:44 +1100 incoming
23903 status_update 2017-03-20 12:25:22 +1100 successful 2017-03-20 12:25:22 +1100 successful
23904 followup_sent 2017-03-20 12:31:58 +1100 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.