Details of request “Public Transport Funding Review reports

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
56937 sent 2018-07-23 21:45:39 +1200 waiting_response 2018-07-23 21:45:39 +1200 waiting_response outgoing
56950 response 2018-07-24 10:47:40 +1200 incoming
58131 response 2018-08-17 11:21:24 +1200 incoming
58133 response 2018-08-17 11:31:27 +1200 2018-08-27 15:57:40 +1200 waiting_response incoming
58479 status_update 2018-08-27 15:57:40 +1200 waiting_response 2018-08-27 15:57:40 +1200 waiting_response
58480 followup_sent 2018-08-27 15:59:27 +1200 outgoing
58501 response 2018-08-28 09:41:24 +1200 incoming
58506 response 2018-08-28 10:41:21 +1200 2018-09-24 07:34:39 +1200 waiting_response incoming
59526 status_update 2018-09-24 07:34:39 +1200 waiting_response 2018-09-24 07:34:39 +1200 waiting_response
59566 response 2018-09-24 17:04:11 +1200 2018-10-12 12:07:44 +1300 waiting_response incoming
60390 followup_sent 2018-10-12 12:07:37 +1300 outgoing
60391 status_update 2018-10-12 12:07:44 +1300 waiting_response 2018-10-12 12:07:44 +1300 waiting_response
60423 response 2018-10-12 16:26:11 +1300 incoming
60511 response 2018-10-15 07:16:10 +1300 incoming
60796 response 2018-10-19 16:46:03 +1300 incoming
61615 followup_sent 2018-10-31 11:07:49 +1300 outgoing
61806 response 2018-11-02 16:36:07 +1300 incoming
62478 response 2018-11-14 11:35:02 +1300 2018-11-22 14:44:57 +1300 waiting_response incoming
62955 followup_sent 2018-11-22 14:44:40 +1300 outgoing
62956 status_update 2018-11-22 14:44:57 +1300 waiting_response 2018-11-22 14:44:57 +1300 waiting_response
63240 response 2018-11-26 15:22:35 +1300 incoming
63262 response 2018-11-27 07:22:35 +1300 2018-12-14 15:36:19 +1300 waiting_response incoming
64297 status_update 2018-12-14 15:36:19 +1300 waiting_response 2018-12-14 15:36:19 +1300 waiting_response
64408 response 2018-12-18 10:29:43 +1300 2019-01-16 13:51:16 +1300 waiting_response incoming
65303 status_update 2019-01-16 13:51:16 +1300 waiting_response 2019-01-16 13:51:16 +1300 waiting_response
65304 followup_sent 2019-01-16 13:55:35 +1300 outgoing
65305 response 2019-01-16 14:00:48 +1300 2019-02-13 01:10:14 +1300 waiting_response incoming
66643 status_update 2019-02-13 01:10:14 +1300 waiting_response 2019-02-13 01:10:14 +1300 waiting_response
67483 followup_sent 2019-02-26 09:43:21 +1300 outgoing
68872 response 2019-03-22 11:25:58 +1300 2020-09-03 12:55:39 +1200 successful incoming
101634 status_update 2020-09-03 12:55:39 +1200 successful 2020-09-03 12:55:39 +1200 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.