Details of request “Crowd control and fire safety training procedures

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
22020 sent 2017-01-29 13:57:11 +1100 waiting_response 2017-01-29 13:57:12 +1100 waiting_response outgoing
22127 response 2017-02-01 17:11:29 +1100 2017-02-02 10:19:12 +1100 waiting_clarification incoming
22144 status_update 2017-02-02 10:19:12 +1100 waiting_clarification 2017-02-02 10:19:12 +1100 waiting_clarification
22274 followup_sent 2017-02-06 11:14:23 +1100 waiting_response 2017-02-06 11:14:23 +1100 waiting_response outgoing
22291 response 2017-02-06 16:23:44 +1100 2017-03-10 10:38:57 +1100 waiting_clarification incoming
22356 comment 2017-02-07 17:47:20 +1100
22359 status_update 2017-02-07 18:50:43 +1100 waiting_response 2017-02-07 18:50:43 +1100 waiting_response
22360 comment 2017-02-07 18:53:23 +1100
23546 status_update 2017-03-10 10:38:57 +1100 waiting_clarification 2017-03-10 10:38:57 +1100 waiting_clarification
23670 status_update 2017-03-14 22:30:01 +1100 waiting_clarification 2017-03-14 22:30:02 +1100 waiting_clarification
23671 followup_sent 2017-03-14 22:37:49 +1100 waiting_response 2017-03-14 22:37:49 +1100 waiting_response outgoing
23676 response 2017-03-15 08:18:02 +1100 2017-03-15 10:16:50 +1100 waiting_response incoming
23681 status_update 2017-03-15 10:16:50 +1100 waiting_response 2017-03-15 10:16:50 +1100 waiting_response
23682 followup_sent 2017-03-15 10:22:31 +1100 outgoing
23689 response 2017-03-15 11:47:29 +1100 2017-03-15 11:53:47 +1100 waiting_clarification incoming
23690 status_update 2017-03-15 11:53:47 +1100 waiting_clarification 2017-03-15 11:53:47 +1100 waiting_clarification
23692 followup_sent 2017-03-15 12:06:07 +1100 waiting_response 2017-03-15 12:06:07 +1100 waiting_response outgoing
23696 response 2017-03-15 12:36:22 +1100 2017-05-04 22:16:34 +1000 rejected incoming
23698 status_update 2017-03-15 12:56:40 +1100 waiting_response 2017-03-15 12:56:40 +1100 waiting_response
23962 status_update 2017-03-21 13:33:27 +1100 waiting_response 2017-03-21 13:33:27 +1100 waiting_response
23963 comment 2017-03-21 13:35:16 +1100
25510 status_update 2017-05-04 22:16:34 +1000 rejected 2017-05-04 22:16:34 +1000 rejected
25511 comment 2017-05-04 22:26:35 +1000
25529 comment 2017-05-05 14:01:09 +1000

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.