Details of request “Copy of all corespondence relating to investigations into behavior at a particular HNZC house

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
34711 sent 2017-01-30 18:37:36 +1300 waiting_response 2017-01-30 18:37:36 +1300 waiting_response outgoing
34712 response 2017-01-30 18:44:31 +1300 incoming
34725 response 2017-01-31 07:24:31 +1300 2017-01-31 07:47:30 +1300 waiting_response incoming
34726 followup_sent 2017-01-31 07:47:06 +1300 outgoing
34727 status_update 2017-01-31 07:47:29 +1300 waiting_response 2017-01-31 07:47:30 +1300 waiting_response
34780 response 2017-02-01 07:14:31 +1300 incoming
34864 response 2017-02-02 17:04:31 +1300 2018-05-18 07:22:24 +1200 rejected incoming
53358 status_update 2018-05-18 07:22:24 +1200 rejected 2018-05-18 07:22:24 +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.