Details of request “Correspondence between Defence and APF regarding Sub Contract "leak".

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
16207  sent  2016-08-29 16:30:16 +1000  waiting_response  2016-08-29 16:30:16 +1000  waiting_response  outgoing  
16209  response  2016-08-29 16:31:31 +1000    2016-08-29 16:32:23 +1000  waiting_response  incoming  
16210  status_update  2016-08-29 16:32:22 +1000  waiting_response  2016-08-29 16:32:23 +1000  waiting_response   
16282  response  2016-09-01 10:03:52 +1000    2016-09-01 10:06:06 +1000  waiting_response  incoming  
16284  status_update  2016-09-01 10:06:06 +1000  waiting_response  2016-09-01 10:06:06 +1000  waiting_response   
16941  response  2016-09-22 15:40:41 +1000    2016-09-22 16:04:50 +1000  waiting_response  incoming  
16942  status_update  2016-09-22 16:04:50 +1000  waiting_response  2016-09-22 16:04:50 +1000  waiting_response   
16943  followup_sent  2016-09-22 16:08:02 +1000        outgoing  
16944  response  2016-09-22 16:09:41 +1000    2016-10-03 11:28:20 +1100  waiting_response  incoming  
53483  overdue  2016-09-29 00:00:00 +1000         
17176  status_update  2016-10-03 11:28:20 +1100  waiting_response  2016-10-03 11:28:20 +1100  waiting_response   
17764  followup_sent  2016-10-28 11:27:31 +1100        outgoing  
17765  response  2016-10-28 11:28:55 +1100        incoming  
17766  response  2016-10-28 11:53:14 +1100    2016-10-28 11:57:11 +1100  waiting_response  incoming  
17767  status_update  2016-10-28 11:57:11 +1100  waiting_response  2016-10-28 11:57:11 +1100  waiting_response   
17768  followup_sent  2016-10-28 12:04:58 +1100        outgoing  
17769  response  2016-10-28 12:06:54 +1100        incoming  
17770  response  2016-10-28 12:38:34 +1100    2016-10-28 13:29:00 +1100  waiting_response  incoming  
17772  status_update  2016-10-28 13:28:59 +1100  waiting_response  2016-10-28 13:29:00 +1100  waiting_response   
55555  very_overdue  2016-10-29 00:00:00 +1100         
19842  followup_sent  2016-11-25 13:10:11 +1100        outgoing  
19843  response  2016-11-25 13:12:27 +1100    2016-11-25 13:16:44 +1100  waiting_response  incoming  
19845  status_update  2016-11-25 13:16:44 +1100  waiting_response  2016-11-25 13:16:44 +1100  waiting_response   
19882  response  2016-11-28 08:17:59 +1100    2016-11-28 09:09:02 +1100  waiting_response  incoming  
19885  status_update  2016-11-28 09:09:01 +1100  waiting_response  2016-11-28 09:09:02 +1100  waiting_response   
19915  response  2016-11-28 15:55:34 +1100    2016-11-28 16:10:55 +1100  successful  incoming  
19922  status_update  2016-11-28 16:10:55 +1100  successful  2016-11-28 16:10:55 +1100  successful   
19927  followup_sent  2016-11-28 17:41:59 +1100        outgoing  

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.