Details of request “Average Hold Data for 2016

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
21145  sent  2016-12-29 15:23:18 +1100  waiting_response  2016-12-29 15:23:18 +1100  waiting_response  outgoing  
21146  response  2016-12-29 15:23:45 +1100        incoming  
21237  response  2017-01-04 16:27:29 +1100    2017-01-04 17:54:04 +1100  waiting_clarification  incoming  
21241  status_update  2017-01-04 17:54:04 +1100  waiting_clarification  2017-01-04 17:54:04 +1100  waiting_clarification   
21242  followup_sent  2017-01-04 18:09:24 +1100  internal_review  2017-01-04 18:09:25 +1100  internal_review  outgoing  
21250  comment  2017-01-04 21:46:54 +1100         
21251  comment  2017-01-04 22:31:57 +1100         
21389  response  2017-01-09 16:20:58 +1100        incoming  
21390  response  2017-01-09 17:28:57 +1100    2017-01-09 21:16:13 +1100  internal_review  incoming  
21391  comment  2017-01-09 18:08:13 +1100         
21394  status_update  2017-01-09 21:16:13 +1100  internal_review  2017-01-09 21:16:13 +1100  internal_review   
21395  followup_sent  2017-01-09 21:28:24 +1100        outgoing  
21419  response  2017-01-11 11:39:48 +1100    2017-01-11 20:14:40 +1100  internal_review  incoming  
21435  status_update  2017-01-11 20:14:40 +1100  internal_review  2017-01-11 20:14:40 +1100  internal_review   
21831  response  2017-01-20 17:30:51 +1100    2017-01-20 19:52:57 +1100  internal_review  incoming  
21832  followup_sent  2017-01-20 19:52:53 +1100        outgoing  
21833  status_update  2017-01-20 19:52:57 +1100  internal_review  2017-01-20 19:52:57 +1100  internal_review   
21834  response  2017-01-20 19:53:20 +1100    2017-01-24 09:23:04 +1100  internal_review  incoming  
21890  status_update  2017-01-24 09:23:04 +1100  internal_review  2017-01-24 09:23:04 +1100  internal_review   
22310  response  2017-02-07 07:59:41 +1100    2017-02-07 08:57:39 +1100  internal_review  incoming  
22313  followup_sent  2017-02-07 08:57:34 +1100        outgoing  
22314  status_update  2017-02-07 08:57:39 +1100  internal_review  2017-02-07 08:57:39 +1100  internal_review   
22315  response  2017-02-07 08:58:01 +1100        incoming  
22377  response  2017-02-08 11:34:36 +1100    2017-02-08 11:38:05 +1100  internal_review  incoming  
22379  status_update  2017-02-08 11:38:05 +1100  internal_review  2017-02-08 11:38:05 +1100  internal_review   
22380  followup_sent  2017-02-08 11:38:39 +1100        outgoing  
22485  response  2017-02-10 15:29:15 +1100    2017-02-10 15:41:07 +1100  internal_review  incoming  
22490  status_update  2017-02-10 15:41:07 +1100  internal_review  2017-02-10 15:41:07 +1100  internal_review   
22578  response  2017-02-14 17:41:05 +1100    2017-02-28 21:36:25 +1100  internal_review  incoming  
23226  followup_sent  2017-02-28 21:36:20 +1100        outgoing  
23227  status_update  2017-02-28 21:36:25 +1100  internal_review  2017-02-28 21:36:25 +1100  internal_review   
23907  response  2017-03-20 13:05:27 +1100        incoming  
24382  response  2017-03-30 16:54:21 +1100    2017-04-03 22:09:27 +1000  rejected  incoming  
24540  status_update  2017-04-03 22:09:26 +1000  rejected  2017-04-03 22:09:26 +1000  rejected   
24639  comment  2017-04-06 09:06:37 +1000         

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.