Details of request “NBN Rollout Statistics as at 31st May 2013

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
1994  sent  2013-08-01 17:13:52 +1000  waiting_response  2013-08-01 17:13:52 +1000  waiting_response  outgoing  
2003  response  2013-08-02 15:55:07 +1000        incoming  
2005  response  2013-08-02 15:55:08 +1000        incoming  
2007  response  2013-08-02 15:55:08 +1000  waiting_response  2013-08-02 16:29:09 +1000  waiting_response  incoming  
2016  followup_sent  2013-08-02 16:29:30 +1000        outgoing  
52836  overdue  2013-09-03 00:00:00 +1000         
2310  followup_sent  2013-09-04 18:15:20 +1000        outgoing  
2326  response  2013-09-05 17:40:48 +1000        incoming  
2327  response  2013-09-05 17:40:48 +1000        incoming  
2331  response  2013-09-05 17:48:32 +1000    2013-11-11 13:15:58 +1100  successful  incoming  
2931  status_update  2013-11-11 13:15:58 +1100  successful  2013-11-11 13:15:58 +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.