Details of request “Telephone standards 111-05010040

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
32313  sent  2018-03-22 22:35:59 +1100  waiting_response  2018-03-22 22:35:59 +1100  waiting_response  outgoing  
32362  response  2018-03-28 16:31:35 +1100    2018-04-01 12:35:28 +1000  waiting_response  incoming  
32388  status_update  2018-04-01 12:35:28 +1000  waiting_response  2018-04-01 12:35:28 +1000  waiting_response   
32476  response  2018-04-09 17:10:08 +1000    2018-04-09 18:56:13 +1000  waiting_response  incoming  
32478  status_update  2018-04-09 18:56:13 +1000  waiting_response  2018-04-09 18:56:13 +1000  waiting_response   
54258  overdue  2018-04-24 00:00:00 +1000         
32815  followup_sent  2018-04-28 22:04:23 +1000  internal_review  2018-04-28 22:04:24 +1000  internal_review  outgoing  
32866  response  2018-05-01 15:17:57 +1000    2018-05-05 07:20:11 +1000  internal_review  incoming  
32956  status_update  2018-05-05 07:20:11 +1000  internal_review  2018-05-05 07:20:11 +1000  internal_review   
33361  response  2018-06-04 16:00:23 +1000        incoming  
33734  followup_sent  2018-06-24 21:46:28 +1000  internal_review  2018-06-24 21:46:28 +1000  internal_review  outgoing  
33880  response  2018-07-03 18:22:38 +1000    2018-07-07 07:01:06 +1000  internal_review  incoming  
33916  status_update  2018-07-07 07:01:06 +1000  internal_review  2018-07-07 07:01:06 +1000  internal_review   
34156  response  2018-07-24 18:03:10 +1000        incoming  
34556  followup_sent  2018-08-23 21:17:27 +1000  internal_review  2018-08-23 21:17:27 +1000  internal_review  outgoing  
36251  response  2018-11-08 17:30:40 +1100        incoming  
36733  response  2018-11-19 15:57:24 +1100    2018-11-19 20:51:06 +1100  successful  incoming  
36745  followup_sent  2018-11-19 20:50:55 +1100        outgoing  
36746  status_update  2018-11-19 20:51:06 +1100  successful  2018-11-19 20:51:06 +1100  successful   
37071  followup_sent  2018-11-27 21:03:51 +1100        outgoing  
37093  response  2018-11-28 16:36:00 +1100    2018-12-23 04:11:11 +1100  successful  incoming  
37650  status_update  2018-12-23 04:11:11 +1100  successful  2018-12-23 04:11:11 +1100  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.