Details of request “I am wanting all information held on myself by council.

Event history

This table shows the technical details of the internal events that happened to this request on FYI. 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 FYI. 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 OIA 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
82698 sent 2019-10-11 12:17:17 +1300 waiting_response 2019-10-11 12:17:17 +1300 waiting_response outgoing
82700 response 2019-10-11 12:29:35 +1300 incoming
82881 response 2019-10-15 08:49:35 +1300 incoming
85025 response 2019-11-11 14:22:42 +1300 2022-02-12 15:42:20 +1300 attention_requested incoming
85032 followup_sent 2019-11-11 16:50:21 +1300 outgoing
85231 followup_sent 2019-11-14 13:24:47 +1300 outgoing
85232 status_update 2019-11-14 13:24:56 +1300 waiting_response 2019-11-14 13:24:56 +1300 waiting_response
85536 comment 2019-11-20 15:57:49 +1300
85569 status_update 2019-11-21 00:35:06 +1300 waiting_response 2019-11-21 00:35:06 +1300 waiting_response
85570 followup_sent 2019-11-21 00:40:02 +1300 outgoing
85598 comment 2019-11-21 11:56:34 +1300
85806 comment 2019-11-23 12:47:31 +1300
85809 comment 2019-11-23 17:07:23 +1300
85898 followup_sent 2019-11-25 16:18:38 +1300 outgoing
85899 comment 2019-11-25 16:21:33 +1300
86257 comment 2019-11-29 18:18:26 +1300
86258 comment 2019-11-29 18:20:38 +1300
87415 comment 2019-12-09 14:54:20 +1300 attention_requested

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 FYI 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.