Details of request “Design and architecture decisions for MTM Distribution Fibre Network (DFN) - named document;NBN-NTO-EDS-359 Network Design Rules MTM Distribution Fibre Network

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
40501  sent  2019-06-18 12:18:31 +1000  waiting_response  2019-06-18 12:18:31 +1000  waiting_response  outgoing  
40639  response  2019-07-01 12:07:55 +1000    2019-07-02 10:16:49 +1000  waiting_response  incoming  
40646  status_update  2019-07-02 10:16:49 +1000  waiting_response  2019-07-02 10:16:49 +1000  waiting_response   
40654  response  2019-07-02 15:28:04 +1000        incoming  
40655  response  2019-07-02 15:53:28 +1000    2019-07-02 20:59:30 +1000  waiting_response  incoming  
40660  status_update  2019-07-02 20:59:30 +1000  waiting_response  2019-07-02 20:59:30 +1000  waiting_response   
40661  response  2019-07-02 21:22:51 +1000    2019-07-02 23:03:21 +1000  waiting_response  incoming  
40664  status_update  2019-07-02 23:03:21 +1000  waiting_response  2019-07-02 23:03:21 +1000  waiting_response   
54616  overdue  2019-07-19 00:00:00 +1000         
40882  response  2019-07-23 10:35:22 +1000    2019-07-23 10:36:19 +1000  waiting_response  incoming  
40883  status_update  2019-07-23 10:36:19 +1000  waiting_response  2019-07-23 10:36:19 +1000  waiting_response   
40884  response  2019-07-23 11:34:10 +1000        incoming  
40885  response  2019-07-23 11:43:18 +1000    2019-07-23 11:43:49 +1000  waiting_response  incoming  
40886  status_update  2019-07-23 11:43:49 +1000  waiting_response  2019-07-23 11:43:49 +1000  waiting_response   
40887  response  2019-07-23 11:54:48 +1000        incoming  
40889  response  2019-07-23 12:17:08 +1000    2019-07-23 12:20:34 +1000  waiting_response  incoming  
40890  status_update  2019-07-23 12:20:34 +1000  waiting_response  2019-07-23 12:20:34 +1000  waiting_response   
40934  response  2019-07-26 14:06:21 +1000        incoming  
40935  response  2019-07-26 14:31:45 +1000        incoming  
40954  response  2019-07-29 11:19:09 +1000        incoming  
41012  response  2019-07-31 17:02:41 +1000    2019-08-02 12:32:56 +1000  waiting_response  incoming  
41054  status_update  2019-08-02 12:32:56 +1000  waiting_response  2019-08-02 12:32:56 +1000  waiting_response   
41265  response  2019-08-16 17:17:47 +1000        incoming  
41266  response  2019-08-16 17:39:16 +1000    2019-08-16 17:39:41 +1000  rejected  incoming  
41267  status_update  2019-08-16 17:39:41 +1000  rejected  2019-08-16 17:39:41 +1000  rejected   
41472  response  2019-08-30 15:53:10 +1000        incoming  
41481  response  2019-08-30 17:45:18 +1000        incoming  
41485  comment  2019-08-30 19:04:38 +1000         
41486  edit  2019-08-30 19:04:55 +1000         
41487  edit_comment  2019-08-30 19:06:17 +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.