Details of request “OIA response time statistics

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
69157 sent 2019-03-27 17:36:24 +1300 waiting_response 2019-03-27 17:36:24 +1300 waiting_response outgoing
69158 response 2019-03-27 17:45:57 +1300 2019-03-28 13:21:04 +1300 waiting_response incoming
69160 comment 2019-03-27 17:56:10 +1300
69203 followup_sent 2019-03-28 13:20:57 +1300 outgoing
69204 status_update 2019-03-28 13:21:04 +1300 waiting_response 2019-03-28 13:21:04 +1300 waiting_response
70994 comment 2019-04-30 19:54:06 +1200
72683 followup_sent 2019-06-04 14:19:08 +1200 outgoing
73129 response 2019-06-11 15:11:43 +1200 2019-06-11 20:25:00 +1200 waiting_response incoming
73137 comment 2019-06-11 19:03:54 +1200
73139 followup_sent 2019-06-11 20:23:38 +1200 outgoing
73140 status_update 2019-06-11 20:25:00 +1200 waiting_response 2019-06-11 20:25:00 +1200 waiting_response
73400 followup_sent 2019-06-19 06:01:21 +1200 outgoing
74358 response 2019-07-01 14:15:41 +1200 2019-07-01 15:57:00 +1200 rejected incoming
74366 status_update 2019-07-01 15:57:00 +1200 rejected 2019-07-01 15:57:00 +1200 rejected
77375 comment 2019-08-02 17:46:43 +1200
101746 edit 2020-09-05 20:33:35 +1200

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.