Details of request “Indigenous Operational Blueprints

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
99914  sent  2022-06-19 09:51:50 +1000  waiting_response  2022-06-19 09:51:50 +1000  waiting_response  outgoing  
99915  response  2022-06-19 09:52:02 +1000    2022-06-19 09:52:59 +1000  waiting_response  incoming  
99916  status_update  2022-06-19 09:52:59 +1000  waiting_response  2022-06-19 09:52:59 +1000  waiting_response   
100765  response  2022-06-27 17:33:04 +1000    2022-06-28 15:23:06 +1000  waiting_clarification  incoming  
100974  status_update  2022-06-28 15:23:06 +1000  waiting_clarification  2022-06-28 15:23:06 +1000  waiting_clarification   
100975  followup_sent  2022-06-28 15:24:20 +1000  waiting_response  2022-06-28 15:24:21 +1000  waiting_response  outgoing  
101963  response  2022-07-08 16:40:51 +1000    2022-07-16 09:11:18 +1000  waiting_response  incoming  
104443  status_update  2022-07-16 09:11:18 +1000  waiting_response  2022-07-16 09:11:18 +1000  waiting_response   
106810  response  2022-07-28 18:04:30 +1000        incoming  
107395  response  2022-08-02 16:13:41 +1000    2022-08-02 17:32:30 +1000  successful  incoming  
107401  status_update  2022-08-02 17:32:30 +1000  successful  2022-08-02 17:32:30 +1000  successful   
141328  edit  2023-02-03 03:45:13 +1100         
141329  edit  2023-02-03 03:45:13 +1100         
141330  edit  2023-02-03 03:45:13 +1100         
141331  edit  2023-02-03 03:45:13 +1100         
141332  edit  2023-02-03 03:45:13 +1100         
141333  edit  2023-02-03 03:45:13 +1100         
141334  edit  2023-02-03 03:45:13 +1100         
141335  edit  2023-02-03 03:45:13 +1100         
141336  edit  2023-02-03 03:45:13 +1100         
141337  edit  2023-02-03 03:45:13 +1100         
141338  edit  2023-02-03 03:45:13 +1100         
282282  edit  2024-08-03 03:45:15 +1000         
282283  edit  2024-08-03 03:45:15 +1000         
282284  edit  2024-08-03 03:45:16 +1000         
282285  edit  2024-08-03 03:45:16 +1000         
282286  edit  2024-08-03 03:45:16 +1000         
282287  edit  2024-08-03 03:45:16 +1000         
282288  edit  2024-08-03 03:45:16 +1000         
282289  edit  2024-08-03 03:45:16 +1000         
282290  edit  2024-08-03 03:45:16 +1000         
282291  edit  2024-08-03 03:45:16 +1000         
282292  edit  2024-08-03 03:45:16 +1000         
282293  edit  2024-08-03 03:45:16 +1000         
282294  edit  2024-08-03 03:45:16 +1000         
282295  edit  2024-08-03 03:45:16 +1000         
282296  edit  2024-08-03 03:45:16 +1000         
282297  edit  2024-08-03 03:45:16 +1000         
282298  edit  2024-08-03 03:45:16 +1000         
282299  edit  2024-08-03 03:45:16 +1000         
282300  edit  2024-08-03 03:45:16 +1000         
282301  edit  2024-08-03 03:45:16 +1000         
282302  edit  2024-08-03 03:45:16 +1000         
282303  edit  2024-08-03 03:45:16 +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.