Details of request “Legal Services & Assurance Branch Position Tree Report

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
35593  sent  2018-10-11 17:04:30 +1100  waiting_response  2018-10-11 17:04:31 +1100  waiting_response  outgoing  
35714  response  2018-10-15 16:40:15 +1100    2018-10-15 16:42:28 +1100  waiting_response  incoming  
35716  status_update  2018-10-15 16:42:28 +1100  waiting_response  2018-10-15 16:42:28 +1100  waiting_response   
35719  followup_sent  2018-10-15 16:54:50 +1100        outgoing  
35930  response  2018-10-25 15:22:34 +1100    2018-10-25 16:57:15 +1100  waiting_response  incoming  
35932  status_update  2018-10-25 16:57:15 +1100  waiting_response  2018-10-25 16:57:15 +1100  waiting_response   
35937  followup_sent  2018-10-25 17:47:05 +1100        outgoing  
35938  status_update  2018-10-25 17:47:26 +1100  waiting_response  2018-10-25 17:47:26 +1100  waiting_response   
35945  comment  2018-10-25 18:28:51 +1100         
54407  overdue  2018-11-13 00:00:00 +1100         
36342  status_update  2018-11-14 16:43:16 +1100  waiting_response  2018-11-14 16:43:16 +1100  waiting_response   
36943  response  2018-11-23 14:53:17 +1100    2018-11-26 14:33:31 +1100  waiting_response  incoming  
37013  status_update  2018-11-26 14:33:31 +1100  waiting_response  2018-11-26 14:33:31 +1100  waiting_response   
37016  comment  2018-11-26 16:12:56 +1100         
37099  status_update  2018-11-28 19:45:01 +1100  waiting_response  2018-11-28 19:45:01 +1100  waiting_response   
56171  very_overdue  2018-12-11 00:00:00 +1100         
37577  status_update  2018-12-20 01:03:12 +1100  waiting_response  2018-12-20 01:03:12 +1100  waiting_response   
37578  status_update  2018-12-20 01:03:27 +1100  waiting_response  2018-12-20 01:03:27 +1100  waiting_response   
37582  status_update  2018-12-20 01:05:02 +1100  waiting_response  2018-12-20 01:05:02 +1100  waiting_response   
40333  response  2019-05-31 16:45:26 +1000    2019-05-31 17:27:34 +1000  waiting_response  incoming  
40336  status_update  2019-05-31 17:27:34 +1000  waiting_response  2019-05-31 17:27:34 +1000  waiting_response   
40339  followup_sent  2019-05-31 18:11:08 +1000        outgoing  
40340  response  2019-05-31 18:20:22 +1000    2019-05-31 18:44:04 +1000  waiting_response  incoming  
40341  status_update  2019-05-31 18:44:04 +1000  waiting_response  2019-05-31 18:44:04 +1000  waiting_response   
40342  followup_sent  2019-05-31 18:58:23 +1000        outgoing  
40588  response  2019-06-26 16:57:43 +1000    2019-06-27 12:58:13 +1000  partially_successful  incoming  
40601  status_update  2019-06-27 12:58:13 +1000  partially_successful  2019-06-27 12:58:13 +1000  partially_successful   
40602  followup_sent  2019-06-27 13:17:09 +1000        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.