Details of request “Baylink project, Tauranga – decision to remove Bayfair underpass from project scope

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
78701 sent 2019-08-16 13:45:53 +1200 waiting_response 2019-08-16 13:45:53 +1200 waiting_response outgoing
78799 response 2019-08-19 17:15:36 +1200 2019-08-20 09:28:10 +1200 waiting_response incoming
78847 status_update 2019-08-20 09:28:10 +1200 waiting_response 2019-08-20 09:28:10 +1200 waiting_response
78996 response 2019-08-22 10:35:36 +1200 incoming
78998 response 2019-08-22 10:45:36 +1200 2019-08-22 11:04:49 +1200 waiting_response incoming
79001 status_update 2019-08-22 11:04:49 +1200 waiting_response 2019-08-22 11:04:49 +1200 waiting_response
80625 response 2019-09-13 15:15:40 +1200 incoming
80746 followup_sent 2019-09-16 13:03:10 +1200 outgoing
80843 response 2019-09-17 10:05:38 +1200 2019-09-17 13:28:10 +1200 waiting_response incoming
80864 followup_sent 2019-09-17 13:27:58 +1200 outgoing
80865 status_update 2019-09-17 13:28:10 +1200 waiting_response 2019-09-17 13:28:10 +1200 waiting_response
80870 response 2019-09-17 14:45:36 +1200 incoming
80938 response 2019-09-18 14:05:36 +1200 incoming
81310 response 2019-09-25 16:25:36 +1200 incoming
81311 response 2019-09-25 16:25:40 +1200 incoming
81329 response 2019-09-25 19:45:36 +1200 2019-09-30 12:07:57 +1300 waiting_response incoming
82031 followup_sent 2019-09-30 12:07:31 +1300 outgoing
82032 status_update 2019-09-30 12:07:57 +1300 waiting_response 2019-09-30 12:07:57 +1300 waiting_response
82142 response 2019-10-01 17:05:36 +1300 2019-10-02 09:09:08 +1300 waiting_response incoming
82162 followup_sent 2019-10-02 09:07:40 +1300 outgoing
82163 status_update 2019-10-02 09:09:08 +1300 waiting_response 2019-10-02 09:09:08 +1300 waiting_response
82195 response 2019-10-02 15:15:36 +1300 2019-10-02 15:21:13 +1300 waiting_response incoming
82198 followup_sent 2019-10-02 15:20:47 +1300 outgoing
82199 status_update 2019-10-02 15:21:13 +1300 waiting_response 2019-10-02 15:21:13 +1300 waiting_response
82612 response 2019-10-10 08:49:35 +1300 incoming
82635 followup_sent 2019-10-10 13:51:12 +1300 outgoing
82641 response 2019-10-10 14:49:37 +1300 incoming
82688 followup_sent 2019-10-11 11:07:50 +1300 outgoing
82753 response 2019-10-11 16:59:35 +1300 incoming
85689 response 2019-11-23 10:17:36 +1300 incoming
85695 response 2019-11-23 10:18:25 +1300 incoming
86571 response 2019-12-05 12:50:34 +1300 incoming
86572 response 2019-12-05 12:50:35 +1300 incoming
86711 response 2019-12-05 13:13:27 +1300 incoming
87748 response 2019-12-14 03:51:10 +1300 incoming
87818 response 2019-12-14 06:09:36 +1300 incoming
88398 response 2019-12-29 15:38:15 +1300 incoming
88473 response 2019-12-29 17:55:29 +1300 incoming
89754 response 2020-02-01 14:06:42 +1300 incoming
90221 response 2020-02-05 17:13:52 +1300 incoming

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.