Details of request “Incomplete information on earthworks

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
54664 sent 2018-06-11 15:54:56 +1200 waiting_response 2018-06-11 15:54:56 +1200 waiting_response outgoing
54667 response 2018-06-11 15:56:30 +1200 incoming
54701 response 2018-06-12 09:36:25 +1200 incoming
54813 response 2018-06-14 12:06:24 +1200 incoming
55247 response 2018-06-25 11:06:25 +1200 incoming
55331 followup_sent 2018-06-26 15:37:53 +1200 outgoing
55366 response 2018-06-27 09:06:24 +1200 2018-07-03 12:05:12 +1200 waiting_response incoming
55791 status_update 2018-07-03 12:05:12 +1200 waiting_response 2018-07-03 12:05:12 +1200 waiting_response
56951 response 2018-07-24 10:47:43 +1200 incoming
56963 followup_sent 2018-07-24 13:38:14 +1200 outgoing
56964 response 2018-07-24 13:57:40 +1200 incoming
57025 followup_sent 2018-07-25 14:28:38 +1200 outgoing
57072 response 2018-07-26 12:07:40 +1200 incoming
57078 followup_sent 2018-07-26 14:15:52 +1200 outgoing
57164 response 2018-07-27 15:17:39 +1200 incoming
57257 response 2018-07-31 09:44:51 +1200 incoming
57473 response 2018-08-03 11:44:54 +1200 incoming
57477 followup_sent 2018-08-03 12:06:42 +1200 outgoing
57901 response 2018-08-13 10:41:18 +1200 incoming
57922 followup_sent 2018-08-13 13:29:12 +1200 outgoing
57924 response 2018-08-13 13:31:27 +1200 incoming
57925 followup_sent 2018-08-13 13:37:03 +1200 outgoing
57926 response 2018-08-13 13:41:15 +1200 incoming
57979 response 2018-08-14 08:41:26 +1200 2018-08-20 15:42:33 +1200 rejected incoming
58244 status_update 2018-08-20 15:42:33 +1200 rejected 2018-08-20 15:42:33 +1200 rejected
58282 response 2018-08-21 11:11:19 +1200 2018-08-21 12:36:53 +1200 attention_requested incoming
58288 status_update 2018-08-21 12:03:43 +1200 attention_requested 2018-08-21 12:36:53 +1200 attention_requested
58609 response 2018-08-30 09:21:21 +1200 2018-08-31 17:25:31 +1200 rejected incoming
58708 status_update 2018-08-31 17:25:31 +1200 rejected 2018-08-31 17:25:31 +1200 rejected
59209 response 2018-09-14 14:47:56 +1200 2018-09-14 15:21:04 +1200 rejected incoming
59214 status_update 2018-09-14 15:21:03 +1200 rejected 2018-09-14 15:21:04 +1200 rejected
59721 response 2018-09-28 17:06:16 +1200 2018-09-28 17:58:46 +1200 rejected incoming
59722 status_update 2018-09-28 17:58:45 +1200 rejected 2018-09-28 17:58:46 +1200 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.