Details of request “NBN Installer records showing missed appointments

Event history

This table shows the technical details of the internal events that happened to this request on Right To Know. 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 Right To Know. 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 FOI 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
13045 sent 2016-03-10 10:16:30 +1100 waiting_response 2016-03-10 10:16:30 +1100 waiting_response outgoing
13059 response 2016-03-11 10:43:40 +1100 2016-03-14 20:58:30 +1100 waiting_clarification incoming
13102 status_update 2016-03-14 20:58:29 +1100 waiting_clarification 2016-03-14 20:58:30 +1100 waiting_clarification
13116 followup_sent 2016-03-15 09:43:25 +1100 waiting_response 2016-03-15 09:43:25 +1100 waiting_response outgoing
13117 response 2016-03-15 09:53:10 +1100 2016-03-15 09:57:30 +1100 waiting_response incoming
13118 status_update 2016-03-15 09:57:30 +1100 waiting_response 2016-03-15 09:57:30 +1100 waiting_response
13284 response 2016-03-23 12:11:41 +1100 2016-04-15 23:28:22 +1000 waiting_clarification incoming
13822 status_update 2016-04-15 23:28:22 +1000 waiting_clarification 2016-04-15 23:28:22 +1000 waiting_clarification
13928 followup_sent 2016-04-18 22:26:59 +1000 waiting_response 2016-04-18 22:26:59 +1000 waiting_response outgoing
13936 followup_sent 2016-04-19 08:40:34 +1000 outgoing
13937 response 2016-04-19 08:52:17 +1000 2016-04-19 08:53:59 +1000 waiting_response incoming
13938 status_update 2016-04-19 08:53:59 +1000 waiting_response 2016-04-19 08:53:59 +1000 waiting_response
14010 response 2016-04-21 13:29:45 +1000 2016-04-27 12:38:52 +1000 waiting_response incoming
14036 followup_sent 2016-04-22 13:32:53 +1000 outgoing
14131 status_update 2016-04-27 12:38:51 +1000 waiting_response 2016-04-27 12:38:51 +1000 waiting_response
14558 followup_sent 2016-05-18 10:14:30 +1000 outgoing
14559 response 2016-05-18 10:49:33 +1000 incoming
14643 response 2016-05-20 16:14:32 +1000 incoming
14776 followup_sent 2016-05-26 14:06:34 +1000 outgoing
14777 response 2016-05-26 14:07:17 +1000 2016-05-26 14:19:55 +1000 waiting_response incoming
14778 status_update 2016-05-26 14:19:54 +1000 waiting_response 2016-05-26 14:19:55 +1000 waiting_response
14853 response 2016-05-31 16:26:06 +1000 2016-07-05 21:15:14 +1000 rejected incoming
15423 status_update 2016-07-05 21:15:13 +1000 rejected 2016-07-05 21:15:13 +1000 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 Right To Know 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.