Details of request “Documents about RACER

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
34952  sent  2018-09-12 13:18:10 +1000  waiting_response  2018-09-12 13:18:10 +1000  waiting_response  outgoing  
35060  response  2018-09-17 14:18:11 +1000    2018-09-17 15:14:16 +1000  waiting_response  incoming  
35061  status_update  2018-09-17 15:14:16 +1000  waiting_response  2018-09-17 15:14:16 +1000  waiting_response   
35285  response  2018-09-27 17:03:22 +1000    2018-09-27 20:23:14 +1000  waiting_response  incoming  
35300  status_update  2018-09-27 20:23:14 +1000  waiting_response  2018-09-27 20:23:14 +1000  waiting_response   
35301  followup_sent  2018-09-27 20:25:19 +1000        outgoing  
35396  followup_sent  2018-10-02 23:17:32 +1000        outgoing  
35409  response  2018-10-03 11:46:27 +1000    2018-10-03 12:39:50 +1000  waiting_response  incoming  
35415  status_update  2018-10-03 12:39:50 +1000  waiting_response  2018-10-03 12:39:50 +1000  waiting_response   
35416  followup_sent  2018-10-03 12:42:44 +1000        outgoing  
35420  response  2018-10-03 14:47:22 +1000    2018-10-03 15:08:17 +1000  waiting_response  incoming  
35426  followup_sent  2018-10-03 15:08:14 +1000        outgoing  
35427  status_update  2018-10-03 15:08:17 +1000  waiting_response  2018-10-03 15:08:17 +1000  waiting_response   
35428  followup_sent  2018-10-03 15:10:52 +1000        outgoing  
35576  followup_sent  2018-10-10 17:56:16 +1100        outgoing  
35624  response  2018-10-12 15:21:04 +1100    2018-10-12 16:19:11 +1100  waiting_response  incoming  
35627  status_update  2018-10-12 16:19:11 +1100  waiting_response  2018-10-12 16:19:11 +1100  waiting_response   
35628  followup_sent  2018-10-12 16:25:03 +1100        outgoing  
35629  followup_sent  2018-10-12 16:28:51 +1100        outgoing  
35630  followup_sent  2018-10-12 16:39:39 +1100        outgoing  
54379  overdue  2018-10-13 00:00:00 +1100         
35639  followup_sent  2018-10-13 01:04:59 +1100        outgoing  
35717  response  2018-10-15 16:45:05 +1100    2018-10-15 20:14:24 +1100  waiting_response  incoming  
35721  status_update  2018-10-15 20:14:24 +1100  waiting_response  2018-10-15 20:14:24 +1100  waiting_response   
35722  followup_sent  2018-10-15 20:35:54 +1100        outgoing  
35738  response  2018-10-16 09:35:43 +1100    2018-10-17 17:26:16 +1100  waiting_response  incoming  
35768  status_update  2018-10-17 17:26:16 +1100  waiting_response  2018-10-17 17:26:16 +1100  waiting_response   
35769  followup_sent  2018-10-17 17:33:14 +1100        outgoing  
35770  followup_sent  2018-10-17 19:49:51 +1100        outgoing  
35786  response  2018-10-18 16:16:52 +1100    2018-10-18 19:31:38 +1100  waiting_response  incoming  
35798  status_update  2018-10-18 19:31:38 +1100  waiting_response  2018-10-18 19:31:38 +1100  waiting_response   
35799  followup_sent  2018-10-18 19:47:27 +1100        outgoing  
35962  response  2018-10-26 09:14:37 +1100    2018-10-26 23:09:01 +1100  waiting_response  incoming  
35995  status_update  2018-10-26 23:09:01 +1100  waiting_response  2018-10-26 23:09:01 +1100  waiting_response   
35996  followup_sent  2018-10-26 23:25:45 +1100        outgoing  
36018  followup_sent  2018-10-29 12:22:23 +1100        outgoing  
36019  response  2018-10-29 12:58:34 +1100    2018-11-01 16:50:03 +1100  waiting_response  incoming  
36131  status_update  2018-11-01 16:50:03 +1100  waiting_response  2018-11-01 16:50:03 +1100  waiting_response   
36132  followup_sent  2018-11-01 16:57:42 +1100        outgoing  
56144  very_overdue  2018-11-13 00:00:00 +1100         
36348  followup_sent  2018-11-14 23:47:02 +1100        outgoing  
37288  followup_sent  2018-12-06 19:39:15 +1100        outgoing  
37289  status_update  2018-12-06 19:47:02 +1100  waiting_response  2018-12-06 19:47:02 +1100  waiting_response   
39166  response  2019-03-27 08:58:23 +1100        incoming  
39167  response  2019-03-27 08:58:45 +1100        incoming  
39168  response  2019-03-27 08:58:46 +1100    2019-04-28 15:33:09 +1000  partially_successful  incoming  
39764  status_update  2019-04-28 15:33:09 +1000  partially_successful  2019-04-28 15:33:09 +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.