Details of request “NDIA operational guidelines and similar

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
155725  sent  2023-04-28 13:26:21 +1000  waiting_response  2023-04-28 13:26:21 +1000  waiting_response  outgoing  
155726  response  2023-04-28 13:26:40 +1000    2023-04-28 13:31:17 +1000  waiting_response  incoming  
155727  status_update  2023-04-28 13:31:17 +1000  waiting_response  2023-04-28 13:31:17 +1000  waiting_response   
161508  overdue  2023-05-30 00:00:00 +1000         
161512  followup_sent  2023-05-30 07:10:26 +1000  internal_review  2023-05-30 07:10:26 +1000  internal_review  outgoing  
171817  very_overdue  2023-06-28 00:00:00 +1000         
171505  response  2023-07-24 14:17:54 +1000    2023-07-25 07:24:51 +1000  waiting_response  incoming  
171701  status_update  2023-07-25 07:24:51 +1000  waiting_response  2023-07-25 07:24:51 +1000  waiting_response   
172965  response  2023-08-01 14:15:07 +1000    2023-08-03 21:53:35 +1000  not_held  incoming  
173302  status_update  2023-08-03 21:53:35 +1000  not_held  2023-08-03 21:53:35 +1000  not_held   
173303  followup_sent  2023-08-03 22:01:38 +1000        outgoing  
227811  edit  2024-02-04 03:45:14 +1100         
227812  edit  2024-02-04 03:45:15 +1100         
227813  edit  2024-02-04 03:45:15 +1100         
227814  edit  2024-02-04 03:45:15 +1100         
227815  edit  2024-02-04 03:45:15 +1100         
227816  edit  2024-02-04 03:45:15 +1100         
227817  edit  2024-02-04 03:45:15 +1100         
227818  edit  2024-02-04 03:45:15 +1100         
227819  edit  2024-02-04 03:45:15 +1100         
227820  edit  2024-02-04 03:45:15 +1100         
227821  edit  2024-02-04 03:45:15 +1100         
412196  edit  2025-08-06 03:45:44 +1000         
412197  edit  2025-08-06 03:45:44 +1000         
412198  edit  2025-08-06 03:45:44 +1000         
412199  edit  2025-08-06 03:45:44 +1000         
412200  edit  2025-08-06 03:45:44 +1000         
412201  edit  2025-08-06 03:45:44 +1000         
412202  edit  2025-08-06 03:45:44 +1000         
412203  edit  2025-08-06 03:45:44 +1000         
412204  edit  2025-08-06 03:45:45 +1000         
412205  edit  2025-08-06 03:45:45 +1000         
412206  edit  2025-08-06 03:45:45 +1000         
412207  edit  2025-08-06 03:45:45 +1000         
412208  edit  2025-08-06 03:45:45 +1000         
412209  edit  2025-08-06 03:45:45 +1000         
412210  edit  2025-08-06 03:45:45 +1000         
412211  edit  2025-08-06 03:45:45 +1000         
412212  edit  2025-08-06 03:45:45 +1000         
412213  edit  2025-08-06 03:45:45 +1000         
412214  edit  2025-08-06 03:45:45 +1000         
412215  edit  2025-08-06 03:45:45 +1000         
412216  edit  2025-08-06 03:45:45 +1000         
412217  edit  2025-08-06 03:45:45 +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.