Details of request “Coronial Services

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
174249 sent 2023-07-21 12:52:17 +1200 waiting_response 2023-07-21 12:52:17 +1200 waiting_response outgoing
174251 response 2023-07-21 12:54:40 +1200 incoming
176178 response 2023-08-18 11:30:58 +1200 incoming
177102 response 2023-08-31 16:43:34 +1200 2023-09-27 09:10:38 +1300 waiting_response incoming
179741 followup_sent 2023-09-27 09:10:19 +1300 outgoing
179742 status_update 2023-09-27 09:10:38 +1300 waiting_response 2023-09-27 09:10:38 +1300 waiting_response
179745 response 2023-09-27 09:28:26 +1300 incoming
179831 response 2023-09-28 13:08:22 +1300 incoming
180116 followup_sent 2023-10-02 15:46:46 +1300 outgoing
180119 response 2023-10-02 15:57:49 +1300 2023-10-23 16:14:50 +1300 waiting_response incoming
180194 followup_sent 2023-10-03 14:28:38 +1300 outgoing
181686 followup_sent 2023-10-23 16:09:42 +1300 outgoing
181687 followup_sent 2023-10-23 16:12:47 +1300 outgoing
181688 status_update 2023-10-23 16:14:50 +1300 waiting_response 2023-10-23 16:14:50 +1300 waiting_response
182623 comment 2023-11-03 10:55:00 +1300
183448 followup_sent 2023-11-14 13:00:40 +1300 outgoing
183450 response 2023-11-14 13:17:01 +1300 2023-11-15 10:08:08 +1300 waiting_response incoming
183514 status_update 2023-11-15 10:08:08 +1300 waiting_response 2023-11-15 10:08:08 +1300 waiting_response
183525 followup_sent 2023-11-15 11:51:56 +1300 outgoing
183526 comment 2023-11-15 11:56:09 +1300
183687 followup_sent 2023-11-17 11:55:28 +1300 outgoing
184145 followup_sent 2023-11-23 17:00:07 +1300 outgoing
184260 followup_sent 2023-11-24 14:49:40 +1300 outgoing
184261 response 2023-11-24 14:57:01 +1300 incoming
184280 followup_sent 2023-11-24 16:26:15 +1300 outgoing
184281 response 2023-11-24 16:37:01 +1300 incoming
184315 followup_sent 2023-11-27 06:20:06 +1300 outgoing
184316 response 2023-11-27 06:27:01 +1300 incoming
184906 response 2023-12-01 12:47:06 +1300 incoming
186672 response 2023-12-19 15:51:18 +1300 incoming
186812 response 2023-12-21 09:21:12 +1300 incoming
186813 response 2023-12-21 09:21:16 +1300 incoming
186855 response 2023-12-21 14:41:12 +1300 incoming
188122 response 2024-01-22 13:53:00 +1300 incoming
188163 followup_sent 2024-01-23 10:14:51 +1300 outgoing
188313 response 2024-01-24 08:47:07 +1300 2024-07-26 21:47:40 +1200 successful incoming
205703 status_update 2024-07-26 21:47:40 +1200 successful 2024-07-26 21:47:40 +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.