Details of request “ECC/EOC Seismic Resilience

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
170314 sent 2023-06-12 18:31:57 +1200 waiting_response 2023-06-12 18:31:57 +1200 waiting_response outgoing
170337 response 2023-06-13 08:32:36 +1200 2023-06-13 13:51:11 +1200 waiting_response incoming
170377 status_update 2023-06-13 13:51:11 +1200 waiting_response 2023-06-13 13:51:11 +1200 waiting_response
170641 response 2023-06-16 10:25:32 +1200 2023-06-16 10:32:10 +1200 waiting_response incoming
170643 status_update 2023-06-16 10:32:10 +1200 waiting_response 2023-06-16 10:32:10 +1200 waiting_response
172399 response 2023-06-28 12:25:54 +1200 incoming
172439 response 2023-06-28 15:35:56 +1200 incoming
172441 response 2023-06-28 15:45:57 +1200 incoming
172445 response 2023-06-28 15:55:57 +1200 incoming
172464 response 2023-06-28 16:46:01 +1200 incoming
172468 response 2023-06-28 16:55:56 +1200 incoming
172520 response 2023-06-29 10:55:56 +1200 incoming
172676 response 2023-06-30 15:15:56 +1200 incoming
172898 response 2023-07-04 10:16:59 +1200 incoming
173011 response 2023-07-05 12:07:02 +1200 incoming
173022 response 2023-07-05 13:26:59 +1200 incoming
173136 response 2023-07-06 14:17:02 +1200 2023-07-07 09:29:50 +1200 waiting_response incoming
173233 followup_sent 2023-07-07 09:22:49 +1200 outgoing
173240 followup_sent 2023-07-07 09:29:43 +1200 outgoing
173241 status_update 2023-07-07 09:29:50 +1200 waiting_response 2023-07-07 09:29:50 +1200 waiting_response
173243 followup_sent 2023-07-07 09:35:31 +1200 outgoing
173246 comment 2023-07-07 09:40:00 +1200
173549 response 2023-07-11 16:17:07 +1200 incoming
173551 response 2023-07-11 16:47:07 +1200 2023-07-11 20:05:43 +1200 waiting_response incoming
173561 status_update 2023-07-11 20:05:43 +1200 waiting_response 2023-07-11 20:05:43 +1200 waiting_response
173632 response 2023-07-12 14:47:07 +1200 2023-07-12 19:54:23 +1200 waiting_response incoming
173666 status_update 2023-07-12 19:54:23 +1200 waiting_response 2023-07-12 19:54:23 +1200 waiting_response
173667 comment 2023-07-12 19:55:31 +1200
173691 response 2023-07-13 10:07:11 +1200 incoming
173708 response 2023-07-13 12:07:07 +1200 incoming
174085 response 2023-07-19 14:43:55 +1200 2023-07-23 22:27:57 +1200 waiting_response incoming
174332 comment 2023-07-23 22:27:49 +1200
174333 status_update 2023-07-23 22:27:57 +1200 waiting_response 2023-07-23 22:27:57 +1200 waiting_response
174453 response 2023-07-25 11:33:55 +1200 incoming
174487 response 2023-07-25 16:43:55 +1200 2023-07-25 20:31:46 +1200 waiting_response incoming
174500 comment 2023-07-25 20:31:37 +1200
174501 status_update 2023-07-25 20:31:46 +1200 waiting_response 2023-07-25 20:31:46 +1200 waiting_response
174560 response 2023-07-26 13:03:54 +1200 2023-07-26 20:06:09 +1200 waiting_response incoming
174601 comment 2023-07-26 20:06:04 +1200
174602 status_update 2023-07-26 20:06:09 +1200 waiting_response 2023-07-26 20:06:09 +1200 waiting_response
174881 response 2023-07-31 15:43:59 +1200 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.