Details of request “Call logs 30/8

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
44275 sent 2017-08-30 15:35:05 +1200 waiting_response 2017-08-30 15:35:05 +1200 waiting_response outgoing
44277 response 2017-08-30 15:36:12 +1200 incoming
44278 response 2017-08-30 15:36:15 +1200 2017-08-31 07:48:24 +1200 waiting_response incoming
44289 followup_sent 2017-08-31 07:48:19 +1200 outgoing
44290 status_update 2017-08-31 07:48:24 +1200 waiting_response 2017-08-31 07:48:24 +1200 waiting_response
44291 response 2017-08-31 07:56:07 +1200 2017-08-31 15:41:37 +1200 waiting_response incoming
44307 status_update 2017-08-31 15:41:37 +1200 waiting_response 2017-08-31 15:41:37 +1200 waiting_response
44315 response 2017-08-31 16:36:07 +1200 incoming
44331 response 2017-09-01 07:56:07 +1200 incoming
44332 response 2017-09-01 09:06:07 +1200 incoming
44334 response 2017-09-01 09:36:08 +1200 incoming
44349 response 2017-09-01 11:06:08 +1200 2017-09-01 16:01:29 +1200 waiting_response incoming
44376 status_update 2017-09-01 16:01:29 +1200 waiting_response 2017-09-01 16:01:29 +1200 waiting_response
44450 response 2017-09-04 16:17:08 +1200 incoming
44451 response 2017-09-04 16:57:04 +1200 2017-09-04 18:33:00 +1200 successful incoming
44452 status_update 2017-09-04 18:33:00 +1200 successful 2017-09-04 18:33:00 +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.