Details of request “Hadgkiss and Lloyd

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
35640 sent 2018-10-13 11:01:50 +1100 waiting_response 2018-10-13 11:01:50 +1100 waiting_response outgoing
35712 response 2018-10-15 16:03:34 +1100 incoming
35895 response 2018-10-24 14:06:58 +1100 2018-11-22 22:35:32 +1100 waiting_response incoming
35926 comment 2018-10-25 12:51:29 +1100
36926 followup_sent 2018-11-22 22:35:27 +1100 outgoing
36927 status_update 2018-11-22 22:35:32 +1100 waiting_response 2018-11-22 22:35:32 +1100 waiting_response
37058 response 2018-11-27 13:16:41 +1100 2018-12-19 07:15:27 +1100 waiting_response incoming
37545 followup_sent 2018-12-19 07:15:21 +1100 outgoing
37546 status_update 2018-12-19 07:15:27 +1100 waiting_response 2018-12-19 07:15:27 +1100 waiting_response
37548 response 2018-12-19 09:12:44 +1100 incoming
37659 response 2018-12-24 11:01:48 +1100 2019-01-16 18:36:16 +1100 waiting_response incoming
38053 followup_sent 2019-01-16 18:36:08 +1100 outgoing
38054 status_update 2019-01-16 18:36:16 +1100 waiting_response 2019-01-16 18:36:16 +1100 waiting_response
38137 response 2019-01-22 12:55:44 +1100 incoming
38157 response 2019-01-23 12:21:43 +1100 incoming
38396 response 2019-02-06 13:56:34 +1100 2019-02-07 18:36:03 +1100 waiting_response incoming
38435 followup_sent 2019-02-07 18:35:56 +1100 outgoing
38436 status_update 2019-02-07 18:36:03 +1100 waiting_response 2019-02-07 18:36:03 +1100 waiting_response
38537 response 2019-02-12 12:34:38 +1100 incoming
38824 followup_sent 2019-03-05 07:12:32 +1100 outgoing
38875 response 2019-03-08 11:19:44 +1100 incoming
38920 response 2019-03-12 17:44:12 +1100 2019-03-14 06:47:20 +1100 partially_successful incoming
38972 followup_sent 2019-03-14 06:47:11 +1100 outgoing
38973 status_update 2019-03-14 06:47:20 +1100 partially_successful 2019-03-14 06:47:20 +1100 partially_successful
39143 response 2019-03-26 13:26:15 +1100 2019-03-27 07:19:50 +1100 waiting_response incoming
39164 followup_sent 2019-03-27 07:19:41 +1100 outgoing
39165 status_update 2019-03-27 07:19:50 +1100 waiting_response 2019-03-27 07:19:50 +1100 waiting_response
39191 response 2019-03-28 11:38:19 +1100 incoming
39207 response 2019-03-29 10:56:35 +1100 incoming
39511 followup_sent 2019-04-10 18:50:41 +1000 internal_review 2019-04-10 18:50:41 +1000 internal_review outgoing
39610 response 2019-04-17 12:58:45 +1000 incoming
40017 response 2019-05-07 16:45:53 +1000 incoming
40027 response 2019-05-08 17:09:24 +1000 incoming
40573 response 2019-06-25 15:43:19 +1000 incoming
40752 followup_sent 2019-07-11 08:50:36 +1000 outgoing
41102 response 2019-08-06 16:03:56 +1000 incoming

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.