Details of request “Procurement records relating to CN3174232

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
22090 sent 2017-01-31 18:11:22 +1100 waiting_response 2017-01-31 18:11:22 +1100 waiting_response outgoing
22579 response 2017-02-14 17:43:17 +1100 2017-02-23 12:52:32 +1100 waiting_response incoming
22988 status_update 2017-02-23 12:52:32 +1100 waiting_response 2017-02-23 12:52:32 +1100 waiting_response
23063 response 2017-02-24 13:56:03 +1100 2017-02-24 14:22:08 +1100 waiting_clarification incoming
23064 followup_sent 2017-02-24 14:22:04 +1100 outgoing
23065 status_update 2017-02-24 14:22:08 +1100 waiting_clarification 2017-02-24 14:22:08 +1100 waiting_clarification
23078 response 2017-02-24 16:28:28 +1100 incoming
23081 followup_sent 2017-02-24 16:35:07 +1100 waiting_response 2017-02-24 16:35:07 +1100 waiting_response outgoing
23301 followup_sent 2017-03-02 14:44:00 +1100 outgoing
23302 followup_sent 2017-03-02 14:50:23 +1100 outgoing
23360 response 2017-03-03 17:58:46 +1100 2017-03-06 10:28:11 +1100 waiting_clarification incoming
23394 status_update 2017-03-06 10:28:11 +1100 waiting_clarification 2017-03-06 10:28:11 +1100 waiting_clarification
23395 followup_sent 2017-03-06 10:42:13 +1100 waiting_response 2017-03-06 10:42:14 +1100 waiting_response outgoing
23510 response 2017-03-09 11:51:52 +1100 incoming
23594 followup_sent 2017-03-13 13:32:21 +1100 outgoing
23595 response 2017-03-13 13:32:49 +1100 2017-03-13 14:21:54 +1100 waiting_response incoming
23601 status_update 2017-03-13 14:21:54 +1100 waiting_response 2017-03-13 14:21:54 +1100 waiting_response
24191 response 2017-03-27 16:25:52 +1100 2017-03-31 12:43:37 +1100 waiting_response incoming
24408 status_update 2017-03-31 12:43:37 +1100 waiting_response 2017-03-31 12:43:37 +1100 waiting_response
24424 response 2017-03-31 16:56:50 +1100 incoming
24427 followup_sent 2017-03-31 17:04:31 +1100 outgoing
24576 response 2017-04-04 17:24:32 +1000 2017-04-27 10:23:47 +1000 rejected incoming
24578 followup_sent 2017-04-04 17:34:18 +1000 outgoing
25296 status_update 2017-04-27 10:23:47 +1000 rejected 2017-04-27 10:23:47 +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.