Details of request “Removal/ revocation of the E&EC – Ethics and Conduct Committee by CASA in September 2016

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
20310 sent 2016-12-06 16:33:06 +1100 waiting_response 2016-12-06 16:33:06 +1100 waiting_response outgoing
20321 response 2016-12-07 08:57:19 +1100 incoming
20387 response 2016-12-08 16:05:08 +1100 2016-12-12 10:29:56 +1100 waiting_clarification incoming
20608 followup_sent 2016-12-12 10:29:36 +1100 outgoing
20610 status_update 2016-12-12 10:29:56 +1100 waiting_clarification 2016-12-12 10:29:56 +1100 waiting_clarification
20611 response 2016-12-12 10:30:48 +1100 incoming
20612 response 2016-12-12 10:32:12 +1100 incoming
20619 followup_sent 2016-12-12 11:01:43 +1100 waiting_response 2016-12-12 11:01:43 +1100 waiting_response outgoing
20995 response 2016-12-21 13:59:48 +1100 incoming
21056 followup_sent 2016-12-22 16:43:30 +1100 outgoing
21071 response 2016-12-23 10:20:51 +1100 2017-01-13 12:27:32 +1100 waiting_response incoming
21500 status_update 2017-01-13 12:27:32 +1100 waiting_response 2017-01-13 12:27:32 +1100 waiting_response
21501 followup_sent 2017-01-13 12:29:09 +1100 outgoing
21508 response 2017-01-13 13:09:26 +1100 incoming
21523 followup_sent 2017-01-13 16:10:46 +1100 internal_review 2017-01-13 16:10:46 +1100 internal_review outgoing
21525 response 2017-01-13 16:21:01 +1100 incoming
21529 followup_sent 2017-01-13 17:03:00 +1100 outgoing
21571 response 2017-01-16 08:47:07 +1100 2017-01-17 10:20:55 +1100 internal_review incoming
21619 status_update 2017-01-17 10:20:54 +1100 internal_review 2017-01-17 10:20:55 +1100 internal_review
22329 response 2017-02-07 11:42:00 +1100 2017-02-24 16:16:19 +1100 partially_successful incoming
23073 status_update 2017-02-24 16:16:18 +1100 partially_successful 2017-02-24 16:16:18 +1100 partially_successful
23082 followup_sent 2017-02-24 16:38:24 +1100 outgoing
23143 response 2017-02-27 11:11:04 +1100 incoming
23830 response 2017-03-17 14:33:12 +1100 2017-04-09 13:15:51 +1000 partially_successful incoming
23935 followup_sent 2017-03-20 21:47:59 +1100 outgoing
24704 status_update 2017-04-07 20:52:07 +1000 successful 2017-04-07 20:52:07 +1000 successful
24736 status_update 2017-04-09 13:15:51 +1000 partially_successful 2017-04-09 13:15:51 +1000 partially_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 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.