Details of request “Community Engagement pertaining to changes to the Runway 30 from 2017 through 2019

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
159475  sent  2023-05-17 13:53:42 +1000  waiting_response  2023-05-17 13:53:43 +1000  waiting_response  outgoing  
159480  response  2023-05-17 14:32:50 +1000    2023-05-17 14:41:21 +1000  waiting_clarification  incoming  
159481  status_update  2023-05-17 14:41:21 +1000  waiting_clarification  2023-05-17 14:41:21 +1000  waiting_clarification   
159487  followup_sent  2023-05-17 16:26:47 +1000  waiting_response  2023-05-17 16:26:47 +1000  waiting_response  outgoing  
159653  followup_sent  2023-05-18 18:18:31 +1000        outgoing  
159785  response  2023-05-19 10:42:21 +1000    2023-05-19 12:38:48 +1000  partially_successful  incoming  
159790  followup_sent  2023-05-19 12:38:07 +1000        outgoing  
159791  status_update  2023-05-19 12:38:48 +1000  partially_successful  2023-05-19 12:38:48 +1000  partially_successful   
159804  response  2023-05-19 16:41:38 +1000    2023-05-19 19:09:36 +1000  waiting_clarification  incoming  
159809  followup_sent  2023-05-19 19:09:29 +1000        outgoing  
159810  status_update  2023-05-19 19:09:36 +1000  waiting_clarification  2023-05-19 19:09:36 +1000  waiting_clarification   
160126  response  2023-05-22 09:43:23 +1000        incoming  
160134  followup_sent  2023-05-22 12:07:02 +1000  waiting_response  2023-05-22 12:07:02 +1000  waiting_response  outgoing  
160276  response  2023-05-23 10:42:29 +1000    2023-05-27 08:35:05 +1000  waiting_response  incoming  
160942  status_update  2023-05-27 08:35:05 +1000  waiting_response  2023-05-27 08:35:05 +1000  waiting_response   
165606  overdue  2023-06-22 00:00:00 +1000         
165607  followup_sent  2023-06-22 07:19:28 +1000        outgoing  
165632  response  2023-06-22 16:10:01 +1000    2023-06-23 07:19:31 +1000  successful  incoming  
165916  status_update  2023-06-23 07:19:31 +1000  successful  2023-06-23 07:19:31 +1000  successful   
218050  edit  2023-12-23 03:45:16 +1100         
218051  edit  2023-12-23 03:45:16 +1100         
218052  edit  2023-12-23 03:45:16 +1100         
218053  edit  2023-12-23 03:45:16 +1100         
218054  edit  2023-12-23 03:45:16 +1100         
218055  edit  2023-12-23 03:45:16 +1100         
218056  edit  2023-12-23 03:45:16 +1100         
218057  edit  2023-12-23 03:45:16 +1100         
218058  edit  2023-12-23 03:45:17 +1100         
218059  edit  2023-12-23 03:45:17 +1100         
218060  edit  2023-12-23 03:45:17 +1100         
218061  edit  2023-12-23 03:45:17 +1100         
218062  edit  2023-12-23 03:45:17 +1100         
218063  edit  2023-12-23 03:45:17 +1100         
218064  edit  2023-12-23 03:45:17 +1100         
218065  edit  2023-12-23 03:45:17 +1100         
218066  edit  2023-12-23 03:45:17 +1100         
218067  edit  2023-12-23 03:45:17 +1100         
218068  edit  2023-12-23 03:45:17 +1100         
396563  edit  2025-06-23 03:45:19 +1000         
396564  edit  2025-06-23 03:45:19 +1000         
396565  edit  2025-06-23 03:45:19 +1000         
396566  edit  2025-06-23 03:45:19 +1000         
396567  edit  2025-06-23 03:45:19 +1000         
396568  edit  2025-06-23 03:45:19 +1000         
396569  edit  2025-06-23 03:45:19 +1000         
396570  edit  2025-06-23 03:45:19 +1000         
396571  edit  2025-06-23 03:45:19 +1000         
396572  edit  2025-06-23 03:45:19 +1000         
396573  edit  2025-06-23 03:45:19 +1000         
396574  edit  2025-06-23 03:45:19 +1000         
396575  edit  2025-06-23 03:45:19 +1000         
396576  edit  2025-06-23 03:45:19 +1000         
396577  edit  2025-06-23 03:45:19 +1000         
396578  edit  2025-06-23 03:45:19 +1000         
396579  edit  2025-06-23 03:45:19 +1000         
396580  edit  2025-06-23 03:45:19 +1000         
396581  edit  2025-06-23 03:45:19 +1000         
396582  edit  2025-06-23 03:45:19 +1000         
396583  edit  2025-06-23 03:45:19 +1000         
396584  edit  2025-06-23 03:45:19 +1000         
396585  edit  2025-06-23 03:45:19 +1000         
396586  edit  2025-06-23 03:45:20 +1000         
396587  edit  2025-06-23 03:45:20 +1000         
396588  edit  2025-06-23 03:45:20 +1000         
396589  edit  2025-06-23 03:45:20 +1000         
396590  edit  2025-06-23 03:45:20 +1000         
396591  edit  2025-06-23 03:45:20 +1000         
396592  edit  2025-06-23 03:45:20 +1000         
396593  edit  2025-06-23 03:45:20 +1000         
396594  edit  2025-06-23 03:45:20 +1000         
396595  edit  2025-06-23 03:45:20 +1000         
396596  edit  2025-06-23 03:45:20 +1000         
396597  edit  2025-06-23 03:45:20 +1000         
396598  edit  2025-06-23 03:45:20 +1000         
396599  edit  2025-06-23 03:45:20 +1000         
396600  edit  2025-06-23 03:45:20 +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.