Details of request “The contractual obligations of a Sydney trains contractor.

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
31060 sent 2017-12-14 22:04:23 +1100 waiting_response 2017-12-14 22:04:23 +1100 waiting_response outgoing
31103 response 2017-12-18 12:31:52 +1100 2017-12-18 14:23:36 +1100 waiting_response incoming
31104 followup_sent 2017-12-18 14:23:10 +1100 outgoing
31105 status_update 2017-12-18 14:23:36 +1100 waiting_response 2017-12-18 14:23:36 +1100 waiting_response
31106 response 2017-12-18 14:36:28 +1100 2019-02-02 11:48:39 +1100 rejected incoming
38283 status_update 2019-02-02 11:48:39 +1100 rejected 2019-02-02 11:48:39 +1100 rejected
38284 comment 2019-02-02 11:49:08 +1100

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.