Details of request “Communications from MCA and BCA between June and September 2019

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
42932  sent  2019-11-10 18:38:01 +1100  waiting_response  2019-11-10 18:38:01 +1100  waiting_response  outgoing  
43055  response  2019-11-13 14:10:25 +1100        incoming  
43065  response  2019-11-13 17:27:13 +1100    2019-11-15 12:39:36 +1100  waiting_clarification  incoming  
43115  followup_sent  2019-11-15 12:39:29 +1100        outgoing  
43116  status_update  2019-11-15 12:39:36 +1100  waiting_clarification  2019-11-15 12:39:36 +1100  waiting_clarification   
43120  response  2019-11-15 13:36:36 +1100    2019-11-26 22:23:46 +1100  waiting_response  incoming  
43445  status_update  2019-11-26 22:23:46 +1100  waiting_response  2019-11-26 22:23:46 +1100  waiting_response   
43557  response  2019-12-04 09:43:21 +1100    2019-12-16 18:47:28 +1100  rejected  incoming  
43844  status_update  2019-12-16 18:47:28 +1100  rejected  2019-12-16 18:47:28 +1100  rejected   
43845  followup_sent  2019-12-16 18:56:20 +1100  internal_review  2019-12-16 18:56:20 +1100  internal_review  outgoing  
43858  response  2019-12-17 11:33:45 +1100    2019-12-17 12:11:17 +1100  internal_review  incoming  
43861  status_update  2019-12-17 12:11:17 +1100  internal_review  2019-12-17 12:11:17 +1100  internal_review   
43862  followup_sent  2019-12-17 12:14:04 +1100        outgoing  
43865  response  2019-12-17 12:43:11 +1100    2019-12-17 17:42:24 +1100  internal_review  incoming  
43905  status_update  2019-12-17 17:42:24 +1100  internal_review  2019-12-17 17:42:24 +1100  internal_review   
43906  followup_sent  2019-12-17 17:49:25 +1100        outgoing  
44417  response  2020-01-15 18:19:10 +1100        incoming  
44440  response  2020-01-16 16:48:33 +1100    2020-01-27 13:45:31 +1100  rejected  incoming  
44640  status_update  2020-01-27 13:45:31 +1100  rejected  2020-01-27 13:45:31 +1100  rejected   
80339  edit  2022-01-28 03:45:15 +1100         
80340  edit  2022-01-28 03:45:15 +1100         
80341  edit  2022-01-28 03:45:15 +1100         
80342  edit  2022-01-28 03:45:15 +1100         
80343  edit  2022-01-28 03:45:15 +1100         
80344  edit  2022-01-28 03:45:15 +1100         
80345  edit  2022-01-28 03:45:15 +1100         
80346  edit  2022-01-28 03:45:15 +1100         
80347  edit  2022-01-28 03:45:15 +1100         
80348  edit  2022-01-28 03:45:15 +1100         
80349  edit  2022-01-28 03:45:15 +1100         
80350  edit  2022-01-28 03:45:15 +1100         
80351  edit  2022-01-28 03:45:15 +1100         
80352  edit  2022-01-28 03:45:15 +1100         
80353  edit  2022-01-28 03:45:15 +1100         
80354  edit  2022-01-28 03:45:15 +1100         
80355  edit  2022-01-28 03:45:16 +1100         
80356  edit  2022-01-28 03:45:16 +1100         
80357  edit  2022-01-28 03:45:16 +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.