Details of request “Request for Benefit Cost Calculations for the Island Bay Cycleway

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
26867 sent 2016-06-27 13:17:14 +1200 waiting_response 2016-06-27 13:17:14 +1200 waiting_response outgoing
26868 response 2016-06-27 13:17:36 +1200 incoming
27389 response 2016-07-13 11:17:36 +1200 2016-07-13 12:43:41 +1200 waiting_clarification incoming
27397 status_update 2016-07-13 12:43:41 +1200 waiting_clarification 2016-07-13 12:43:41 +1200 waiting_clarification
27399 followup_sent 2016-07-13 12:55:34 +1200 waiting_response 2016-07-13 12:55:34 +1200 waiting_response outgoing
27537 response 2016-07-18 09:47:39 +1200 2016-07-18 10:42:53 +1200 waiting_response incoming
27543 followup_sent 2016-07-18 10:42:19 +1200 outgoing
27544 status_update 2016-07-18 10:42:53 +1200 waiting_response 2016-07-18 10:42:53 +1200 waiting_response
27669 comment 2016-07-21 11:16:49 +1200
27747 response 2016-07-25 09:37:36 +1200 2016-07-25 10:15:47 +1200 waiting_response incoming
27750 status_update 2016-07-25 10:15:47 +1200 waiting_response 2016-07-25 10:15:47 +1200 waiting_response
27754 followup_sent 2016-07-25 10:53:24 +1200 outgoing
27841 comment 2016-07-27 10:12:41 +1200
27855 followup_sent 2016-07-27 16:32:53 +1200 outgoing
28031 followup_sent 2016-08-02 12:12:28 +1200 outgoing
28033 response 2016-08-02 12:47:35 +1200 2016-08-02 13:04:09 +1200 waiting_response incoming
28034 status_update 2016-08-02 13:04:09 +1200 waiting_response 2016-08-02 13:04:09 +1200 waiting_response
28036 response 2016-08-02 13:17:35 +1200 2016-08-02 13:32:35 +1200 waiting_response incoming
28037 status_update 2016-08-02 13:32:35 +1200 waiting_response 2016-08-02 13:32:35 +1200 waiting_response
28044 followup_sent 2016-08-02 15:04:53 +1200 outgoing
28066 response 2016-08-03 08:47:36 +1200 2016-08-03 09:56:50 +1200 waiting_response incoming
28073 status_update 2016-08-03 09:56:49 +1200 waiting_response 2016-08-03 09:56:50 +1200 waiting_response
28519 followup_sent 2016-08-12 14:44:46 +1200 outgoing
28793 response 2016-08-19 09:27:36 +1200 2016-08-19 10:34:10 +1200 waiting_response incoming
28797 status_update 2016-08-19 10:34:10 +1200 waiting_response 2016-08-19 10:34:10 +1200 waiting_response
28827 followup_sent 2016-08-19 16:34:43 +1200 outgoing
29081 response 2016-08-26 08:57:35 +1200 2016-09-27 22:47:12 +1300 rejected incoming
29083 status_update 2016-08-26 09:24:03 +1200 waiting_response 2016-08-26 09:24:03 +1200 waiting_response
29684 status_update 2016-09-09 14:35:50 +1200 waiting_response 2016-09-09 14:35:50 +1200 waiting_response
30309 status_update 2016-09-27 22:47:12 +1300 rejected 2016-09-27 22:47:12 +1300 rejected

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.