Details of request “potential conflicts of interests senior leaders MBIE

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
25753 sent 2016-05-26 18:00:01 +1200 waiting_response 2016-05-26 18:00:01 +1200 waiting_response outgoing
25849 response 2016-05-30 16:34:37 +1200 incoming
25957 response 2016-06-03 10:22:17 +1200 incoming
26029 response 2016-06-07 07:09:45 +1200 incoming
26781 response 2016-06-23 08:57:36 +1200 incoming
27031 response 2016-07-04 13:27:36 +1200 incoming
27186 response 2016-07-08 06:47:36 +1200 incoming
27188 response 2016-07-08 08:07:35 +1200 incoming
27314 response 2016-07-11 17:17:36 +1200 2017-04-12 14:04:16 +1200 partially_successful incoming
38643 status_update 2017-04-12 14:04:16 +1200 partially_successful 2017-04-12 14:04:16 +1200 partially_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.