Details of request “Extension of Time Applications - s 15AB - Complex or Voluminous

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
29705  sent  2017-10-05 12:48:45 +1100  waiting_response  2017-10-05 12:48:46 +1100  waiting_response  outgoing  
29743  response  2017-10-05 15:13:10 +1100    2017-10-05 15:32:58 +1100  waiting_response  incoming  
29744  status_update  2017-10-05 15:32:58 +1100  waiting_response  2017-10-05 15:32:58 +1100  waiting_response   
29745  followup_sent  2017-10-05 15:33:33 +1100        outgoing  
29746  followup_sent  2017-10-05 15:39:29 +1100        outgoing  
29748  response  2017-10-05 16:11:36 +1100    2017-10-05 16:20:07 +1100  waiting_response  incoming  
29749  status_update  2017-10-05 16:20:06 +1100  waiting_response  2017-10-05 16:20:06 +1100  waiting_response   
29750  followup_sent  2017-10-05 16:22:31 +1100        outgoing  
29751  response  2017-10-05 16:24:45 +1100    2017-10-05 16:32:44 +1100  waiting_response  incoming  
29752  followup_sent  2017-10-05 16:32:37 +1100        outgoing  
29753  status_update  2017-10-05 16:32:44 +1100  waiting_response  2017-10-05 16:32:44 +1100  waiting_response   
29795  response  2017-10-06 17:09:37 +1100    2017-10-06 17:15:55 +1100  waiting_response  incoming  
29796  followup_sent  2017-10-06 17:15:50 +1100        outgoing  
29797  status_update  2017-10-06 17:15:55 +1100  waiting_response  2017-10-06 17:15:55 +1100  waiting_response   
29798  response  2017-10-06 17:18:49 +1100    2017-10-06 17:19:33 +1100  waiting_response  incoming  
29799  status_update  2017-10-06 17:19:33 +1100  waiting_response  2017-10-06 17:19:33 +1100  waiting_response   
30496  response  2017-11-06 17:20:42 +1100    2017-11-06 17:25:32 +1100  waiting_response  incoming  
30497  status_update  2017-11-06 17:25:32 +1100  waiting_response  2017-11-06 17:25:32 +1100  waiting_response   
30498  followup_sent  2017-11-06 17:36:36 +1100        outgoing  
30535  response  2017-11-08 10:48:57 +1100        incoming  
30536  response  2017-11-08 10:51:48 +1100        incoming  
30537  response  2017-11-08 10:57:23 +1100    2017-11-08 11:00:43 +1100  waiting_response  incoming  
30538  status_update  2017-11-08 11:00:42 +1100  waiting_response  2017-11-08 11:00:43 +1100  waiting_response   
30539  followup_sent  2017-11-08 11:40:48 +1100        outgoing  
54143  overdue  2017-11-09 00:00:00 +1100         
30570  response  2017-11-10 17:12:19 +1100    2017-11-10 20:32:02 +1100  waiting_response  incoming  
30572  status_update  2017-11-10 20:32:02 +1100  waiting_response  2017-11-10 20:32:02 +1100  waiting_response   
30573  followup_sent  2017-11-10 20:34:46 +1100        outgoing  
30613  response  2017-11-15 13:28:45 +1100    2017-11-15 13:53:24 +1100  waiting_response  incoming  
30614  followup_sent  2017-11-15 13:53:20 +1100        outgoing  
30615  status_update  2017-11-15 13:53:24 +1100  waiting_response  2017-11-15 13:53:24 +1100  waiting_response   
30617  comment  2017-11-15 14:10:09 +1100         
30625  response  2017-11-15 17:32:18 +1100    2017-11-15 17:58:51 +1100  waiting_response  incoming  
30626  followup_sent  2017-11-15 17:58:44 +1100        outgoing  
30627  status_update  2017-11-15 17:58:51 +1100  waiting_response  2017-11-15 17:58:51 +1100  waiting_response   
30628  followup_sent  2017-11-15 17:59:39 +1100        outgoing  
55979  very_overdue  2017-12-05 00:00:00 +1100         
30897  comment  2017-12-05 08:35:09 +1100         
31048  comment  2017-12-14 11:09:01 +1100         
31910  status_update  2018-02-20 06:10:23 +1100  waiting_response  2018-02-20 06:10:23 +1100  waiting_response   
32369  status_update  2018-03-29 01:30:30 +1100  waiting_response  2018-03-29 01:30:31 +1100  waiting_response   
32932  status_update  2018-05-03 21:48:24 +1000  waiting_response  2018-05-03 21:48:24 +1000  waiting_response   
33209  status_update  2018-05-23 13:18:47 +1000  waiting_response  2018-05-23 13:18:47 +1000  waiting_response   
33210  status_update  2018-05-23 13:19:11 +1000  waiting_response  2018-05-23 13:19:11 +1000  waiting_response   
34743  status_update  2018-09-03 18:17:05 +1000  waiting_response  2018-09-03 18:17:05 +1000  waiting_response   
35501  status_update  2018-10-05 14:26:06 +1000  waiting_response  2018-10-05 14:26:06 +1000  waiting_response   

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.