Details of request “Public Interest Disclosure investigations into alleged fraud and other criminal offences

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
30083  sent  2017-10-16 13:39:13 +1100  waiting_response  2017-10-16 13:39:13 +1100  waiting_response  outgoing  
30085  response  2017-10-16 13:52:41 +1100    2017-10-16 15:22:28 +1100  waiting_response  incoming  
30096  status_update  2017-10-16 15:22:28 +1100  waiting_response  2017-10-16 15:22:28 +1100  waiting_response   
30181  response  2017-10-19 17:53:41 +1100    2017-10-23 10:04:47 +1100  waiting_clarification  incoming  
30214  comment  2017-10-20 09:42:14 +1100         
30241  status_update  2017-10-23 10:04:46 +1100  waiting_clarification  2017-10-23 10:04:47 +1100  waiting_clarification   
30244  followup_sent  2017-10-23 12:45:56 +1100  waiting_response  2017-10-23 12:45:56 +1100  waiting_response  outgoing  
30245  status_update  2017-10-23 12:53:01 +1100  waiting_clarification  2017-10-23 12:53:01 +1100  waiting_clarification   
30304  response  2017-10-26 16:35:48 +1100    2017-11-06 13:18:31 +1100  waiting_response  incoming  
30321  comment  2017-10-27 11:43:06 +1100         
30489  status_update  2017-11-06 13:18:31 +1100  waiting_response  2017-11-06 13:18:31 +1100  waiting_response   
30491  followup_sent  2017-11-06 14:22:02 +1100        outgoing  
30563  followup_sent  2017-11-10 12:52:24 +1100        outgoing  
30576  response  2017-11-13 10:12:15 +1100    2017-11-17 15:48:07 +1100  waiting_response  incoming  
30663  followup_sent  2017-11-17 15:47:38 +1100        outgoing  
30664  status_update  2017-11-17 15:48:07 +1100  waiting_response  2017-11-17 15:48:07 +1100  waiting_response   
54166  overdue  2017-12-07 00:00:00 +1100         
55993  very_overdue  2018-01-06 00:00:00 +1100         
31396  followup_sent  2018-01-12 13:11:31 +1100        outgoing  
31688  response  2018-02-01 14:32:34 +1100    2018-02-08 12:54:47 +1100  waiting_response  incoming  
31781  followup_sent  2018-02-08 12:54:24 +1100        outgoing  
31782  status_update  2018-02-08 12:54:47 +1100  waiting_response  2018-02-08 12:54:47 +1100  waiting_response   
31784  followup_sent  2018-02-08 12:59:31 +1100  internal_review  2018-02-08 12:59:31 +1100  internal_review  outgoing  
31815  response  2018-02-12 12:03:54 +1100    2018-02-24 09:47:47 +1100  internal_review  incoming  
31983  status_update  2018-02-24 09:47:47 +1100  internal_review  2018-02-24 09:47:47 +1100  internal_review   
32222  response  2018-03-13 16:24:25 +1100    2019-04-28 15:31:05 +1000  partially_successful  incoming  
34094  comment  2018-07-18 14:41:59 +1000         
39763  status_update  2019-04-28 15:31:05 +1000  partially_successful  2019-04-28 15:31:05 +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.