Details of request “Australian Competition and Consumer Commission v Uber B.V. (Uber) Court Documents

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
97561  sent  2022-05-30 23:43:36 +1000  waiting_response  2022-05-30 23:43:36 +1000  waiting_response  outgoing  
97562  response  2022-05-30 23:43:54 +1000        incoming  
98876  response  2022-06-10 10:02:00 +1000        incoming  
101042  response  2022-06-29 13:25:40 +1000    2022-06-30 12:39:45 +1000  waiting_response  incoming  
101256  overdue  2022-06-30 00:00:00 +1000         
101146  status_update  2022-06-30 12:39:45 +1000  waiting_response  2022-06-30 12:39:45 +1000  waiting_response   
101147  followup_sent  2022-06-30 12:56:03 +1000        outgoing  
106802  response  2022-07-28 16:57:36 +1000    2023-03-14 19:00:50 +1100  rejected  incoming  
140581  edit  2023-01-29 03:45:17 +1100         
140582  edit  2023-01-29 03:45:17 +1100         
140583  edit  2023-01-29 03:45:17 +1100         
140584  edit  2023-01-29 03:45:17 +1100         
140585  edit  2023-01-29 03:45:17 +1100         
140586  edit  2023-01-29 03:45:17 +1100         
140587  edit  2023-01-29 03:45:17 +1100         
140588  edit  2023-01-29 03:45:17 +1100         
148902  status_update  2023-03-14 19:00:49 +1100  rejected  2023-03-14 19:00:50 +1100  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.