Details of request “LGOIA Request - correspondence with Sarin Investments Limited on Lower Hutt hotel

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
76519 sent 2019-07-25 21:12:10 +1200 waiting_response 2019-07-25 21:12:10 +1200 waiting_response outgoing
76520 response 2019-07-25 21:19:15 +1200 incoming
76543 response 2019-07-26 11:29:15 +1200 incoming
77337 response 2019-08-02 14:09:18 +1200 2019-08-02 16:28:32 +1200 waiting_clarification incoming
77363 status_update 2019-08-02 16:28:31 +1200 waiting_clarification 2019-08-02 16:28:32 +1200 waiting_clarification
77364 followup_sent 2019-08-02 16:30:54 +1200 waiting_response 2019-08-02 16:30:54 +1200 waiting_response outgoing
77367 response 2019-08-02 17:19:15 +1200 2019-08-05 19:30:22 +1200 waiting_clarification incoming
77860 status_update 2019-08-05 19:30:22 +1200 waiting_clarification 2019-08-05 19:30:22 +1200 waiting_clarification
77863 followup_sent 2019-08-05 19:47:19 +1200 waiting_response 2019-08-05 19:47:19 +1200 waiting_response outgoing
77961 response 2019-08-07 13:05:36 +1200 2019-08-07 16:54:49 +1200 waiting_clarification incoming
77982 status_update 2019-08-07 16:54:49 +1200 waiting_clarification 2019-08-07 16:54:49 +1200 waiting_clarification
78107 followup_sent 2019-08-09 10:18:55 +1200 waiting_response 2019-08-09 10:18:55 +1200 waiting_response outgoing
78154 response 2019-08-09 15:05:36 +1200 incoming
78250 response 2019-08-12 11:35:36 +1200 incoming
78309 followup_sent 2019-08-13 11:55:35 +1200 outgoing
78329 response 2019-08-13 12:45:39 +1200 incoming
78581 response 2019-08-14 11:25:36 +1200 incoming
78582 followup_sent 2019-08-14 12:02:19 +1200 outgoing
78583 response 2019-08-14 12:05:36 +1200 incoming
78589 followup_sent 2019-08-14 12:47:30 +1200 outgoing
78627 followup_sent 2019-08-15 10:51:16 +1200 outgoing
78630 response 2019-08-15 11:05:36 +1200 incoming
78659 response 2019-08-15 16:55:36 +1200 incoming
78699 followup_sent 2019-08-16 13:27:00 +1200 outgoing
79666 response 2019-08-29 12:05:43 +1200 incoming
79713 response 2019-08-30 09:55:36 +1200 2019-08-30 16:13:52 +1200 successful incoming
79757 followup_sent 2019-08-30 16:13:43 +1200 outgoing
79758 status_update 2019-08-30 16:13:52 +1200 successful 2019-08-30 16:13:52 +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.