Details of request “Wastewater connection to the Russell Wharf

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
70822 sent 2019-04-26 20:51:06 +1200 waiting_response 2019-04-26 20:51:06 +1200 waiting_response outgoing
70824 response 2019-04-26 21:01:09 +1200 incoming
70887 response 2019-04-29 15:01:09 +1200 2019-04-29 15:28:21 +1200 waiting_response incoming
70897 status_update 2019-04-29 15:28:21 +1200 waiting_response 2019-04-29 15:28:21 +1200 waiting_response
72446 status_update 2019-05-29 21:25:29 +1200 waiting_response 2019-05-29 21:25:29 +1200 waiting_response
73349 response 2019-06-17 17:21:45 +1200 2019-06-17 21:06:51 +1200 waiting_response incoming
73354 status_update 2019-06-17 21:06:51 +1200 waiting_response 2019-06-17 21:06:51 +1200 waiting_response
73441 followup_sent 2019-06-19 13:31:35 +1200 outgoing
75059 followup_sent 2019-07-05 19:19:12 +1200 outgoing
77882 followup_sent 2019-08-06 09:31:05 +1200 outgoing
79584 followup_sent 2019-08-28 08:31:52 +1200 outgoing
79598 response 2019-08-28 10:45:36 +1200 incoming
79762 response 2019-08-30 17:05:36 +1200 2019-08-30 17:20:34 +1200 waiting_response incoming
79766 status_update 2019-08-30 17:20:34 +1200 waiting_response 2019-08-30 17:20:34 +1200 waiting_response
82248 followup_sent 2019-10-02 20:57:03 +1300 outgoing
82383 response 2019-10-04 17:35:36 +1300 incoming
82729 response 2019-10-11 14:29:41 +1300 incoming
85264 response 2019-11-14 17:57:04 +1300 incoming
85265 response 2019-11-14 17:57:07 +1300 incoming
85290 response 2019-11-15 12:07:06 +1300 2019-11-15 13:25:23 +1300 successful incoming
85298 status_update 2019-11-15 13:25:23 +1300 successful 2019-11-15 13:25:23 +1300 successful
85299 followup_sent 2019-11-15 13:26:28 +1300 outgoing
85300 response 2019-11-15 13:27:04 +1300 incoming
85301 response 2019-11-15 13:27:06 +1300 2019-11-15 21:15:39 +1300 successful incoming
85317 status_update 2019-11-15 21:15:39 +1300 successful 2019-11-15 21:15:39 +1300 successful
85424 response 2019-11-18 21:31:18 +1300 incoming
85554 response 2019-11-20 18:00:45 +1300 incoming
85633 response 2019-11-21 17:57:35 +1300 2019-12-06 12:59:00 +1300 successful incoming
86840 status_update 2019-12-06 12:59:00 +1300 successful 2019-12-06 12:59:00 +1300 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 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.