Details of request “Location of FTTN cabinets

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
47156  sent  2020-06-22 11:27:18 +1000  waiting_response  2020-06-22 11:27:18 +1000  waiting_response  outgoing  
47444  response  2020-07-08 13:20:13 +1000    2020-07-13 09:33:15 +1000  waiting_clarification  incoming  
47747  status_update  2020-07-13 09:33:15 +1000  waiting_clarification  2020-07-13 09:33:15 +1000  waiting_clarification   
47748  followup_sent  2020-07-13 09:51:02 +1000  waiting_response  2020-07-13 09:51:02 +1000  waiting_response  outgoing  
48380  response  2020-07-29 12:25:31 +1000    2020-07-29 13:24:42 +1000  waiting_response  incoming  
48382  status_update  2020-07-29 13:24:42 +1000  waiting_response  2020-07-29 13:24:42 +1000  waiting_response   
48393  response  2020-07-29 17:16:21 +1000    2020-07-29 17:17:21 +1000  waiting_clarification  incoming  
48394  status_update  2020-07-29 17:17:21 +1000  waiting_clarification  2020-07-29 17:17:21 +1000  waiting_clarification   
48497  followup_sent  2020-08-03 08:39:33 +1000  waiting_response  2020-08-03 08:39:33 +1000  waiting_response  outgoing  
48973  response  2020-08-20 16:10:21 +1000    2020-08-20 16:28:15 +1000  waiting_response  incoming  
48979  status_update  2020-08-20 16:28:15 +1000  waiting_response  2020-08-20 16:28:15 +1000  waiting_response   
54989  overdue  2020-09-03 00:00:00 +1000         
49930  followup_sent  2020-09-19 17:57:28 +1000        outgoing  
50062  response  2020-09-24 09:24:10 +1000    2020-09-24 10:48:21 +1000  waiting_response  incoming  
50065  status_update  2020-09-24 10:48:21 +1000  waiting_response  2020-09-24 10:48:21 +1000  waiting_response   
50117  response  2020-09-25 15:25:58 +1000    2020-10-02 22:28:45 +1000  rejected  incoming  
50362  status_update  2020-10-02 22:28:45 +1000  rejected  2020-10-02 22:28:45 +1000  rejected   
60114  edit  2021-04-03 03:45:11 +1100         
60115  edit  2021-04-03 03:45:11 +1100         
60116  edit  2021-04-03 03:45:11 +1100         
60117  edit  2021-04-03 03:45:11 +1100         
60118  edit  2021-04-03 03:45:11 +1100         
60119  edit  2021-04-03 03:45:11 +1100         
60120  edit  2021-04-03 03:45:11 +1100         
60121  edit  2021-04-03 03:45:11 +1100         
60122  edit  2021-04-03 03:45:11 +1100         
60123  edit  2021-04-03 03:45:11 +1100         
60124  edit  2021-04-03 03:45:11 +1100         
60125  edit  2021-04-03 03:45:11 +1100         
60126  edit  2021-04-03 03:45:11 +1100         
60127  edit  2021-04-03 03:45:11 +1100         
60128  edit  2021-04-03 03:45:12 +1100         
60129  edit  2021-04-03 03:45:12 +1100         
60130  edit  2021-04-03 03:45:12 +1100         

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.