Details of request “Risk Governance and Oversight of Centrelink Data Matching

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
22263  sent  2017-02-06 08:26:16 +1100  waiting_response  2017-02-06 08:26:16 +1100  waiting_response  outgoing  
22264  response  2017-02-06 08:26:56 +1100    2017-02-06 08:40:07 +1100  waiting_response  incoming  
22265  status_update  2017-02-06 08:40:06 +1100  waiting_response  2017-02-06 08:40:06 +1100  waiting_response   
22266  followup_sent  2017-02-06 08:59:09 +1100        outgoing  
22541  response  2017-02-13 16:29:57 +1100        incoming  
22544  response  2017-02-13 17:07:10 +1100    2017-02-13 17:07:37 +1100  waiting_response  incoming  
22545  status_update  2017-02-13 17:07:37 +1100  waiting_response  2017-02-13 17:07:37 +1100  waiting_response   
22973  response  2017-02-22 17:43:18 +1100    2017-02-22 20:00:46 +1100  waiting_clarification  incoming  
22974  status_update  2017-02-22 20:00:46 +1100  waiting_clarification  2017-02-22 20:00:46 +1100  waiting_clarification   
22977  followup_sent  2017-02-22 20:12:17 +1100  waiting_response  2017-02-22 20:12:17 +1100  waiting_response  outgoing  
23470  response  2017-03-08 11:00:46 +1100    2017-03-08 11:19:45 +1100  waiting_clarification  incoming  
23473  status_update  2017-03-08 11:19:44 +1100  waiting_clarification  2017-03-08 11:19:45 +1100  waiting_clarification   
23474  followup_sent  2017-03-08 11:26:43 +1100  waiting_response  2017-03-08 11:26:43 +1100  waiting_response  outgoing  
23493  response  2017-03-08 19:08:25 +1100    2017-03-10 08:30:26 +1100  waiting_clarification  incoming  
23535  status_update  2017-03-10 08:30:26 +1100  waiting_clarification  2017-03-10 08:30:26 +1100  waiting_clarification   
23544  followup_sent  2017-03-10 10:28:32 +1100  waiting_response  2017-03-10 10:28:32 +1100  waiting_response  outgoing  
23643  response  2017-03-14 15:55:31 +1100    2017-03-14 16:08:02 +1100  rejected  incoming  
23648  status_update  2017-03-14 16:08:02 +1100  rejected  2017-03-14 16:08:02 +1100  rejected   
23668  followup_sent  2017-03-14 20:01:47 +1100  internal_review  2017-03-14 20:01:47 +1100  internal_review  outgoing  
23723  response  2017-03-15 16:34:54 +1100    2017-03-16 10:58:40 +1100  rejected  incoming  
23746  status_update  2017-03-16 10:58:40 +1100  rejected  2017-03-16 10:58:40 +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.