Details of request “FOI Request - Monitoring Decision

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
226010  sent  2024-01-24 17:05:21 +1100  waiting_response  2024-01-24 17:05:21 +1100  waiting_response  outgoing  
226011  response  2024-01-24 17:15:49 +1100    2024-01-28 11:06:50 +1100  waiting_response  incoming  
226575  status_update  2024-01-28 11:06:50 +1100  waiting_response  2024-01-28 11:06:50 +1100  waiting_response   
227554  response  2024-02-02 15:37:20 +1100    2024-02-02 20:44:23 +1100  waiting_clarification  incoming  
227570  status_update  2024-02-02 20:44:22 +1100  waiting_clarification  2024-02-02 20:44:23 +1100  waiting_clarification   
227572  followup_sent  2024-02-02 20:48:36 +1100  waiting_response  2024-02-02 20:48:36 +1100  waiting_response  outgoing  
227573  response  2024-02-02 20:48:53 +1100        incoming  
228211  response  2024-02-05 16:01:45 +1100        incoming  
228214  followup_sent  2024-02-05 16:11:09 +1100        outgoing  
228215  response  2024-02-05 16:11:26 +1100        incoming  
228747  response  2024-02-08 16:05:36 +1100    2024-02-08 17:13:47 +1100  rejected  incoming  
228749  status_update  2024-02-08 17:13:47 +1100  rejected  2024-02-08 17:13:47 +1100  rejected   
230453  followup_sent  2024-02-14 15:09:55 +1100        outgoing  
230454  response  2024-02-14 15:10:14 +1100    2024-02-19 16:38:15 +1100  rejected  incoming  
232513  status_update  2024-02-19 16:38:15 +1100  rejected  2024-02-19 16:38:15 +1100  rejected   
236111  response  2024-02-29 16:15:24 +1100    2024-02-29 16:18:54 +1100  rejected  incoming  
236113  status_update  2024-02-29 16:18:53 +1100  rejected  2024-02-29 16:18:54 +1100  rejected   
292175  edit  2024-09-01 03:45:15 +1000         
292176  edit  2024-09-01 03:45:15 +1000         
292177  edit  2024-09-01 03:45:15 +1000         
292178  edit  2024-09-01 03:45:15 +1000         
292179  edit  2024-09-01 03:45:15 +1000         
292180  edit  2024-09-01 03:45:15 +1000         
292181  edit  2024-09-01 03:45:15 +1000         
292182  edit  2024-09-01 03:45:15 +1000         
292183  edit  2024-09-01 03:45:15 +1000         
292184  edit  2024-09-01 03:45:15 +1000         
292185  edit  2024-09-01 03:45:16 +1000         
292186  edit  2024-09-01 03:45:16 +1000         
292187  edit  2024-09-01 03:45:16 +1000         
292188  edit  2024-09-01 03:45:16 +1000         
292189  edit  2024-09-01 03:45:16 +1000         
292190  edit  2024-09-01 03:45:16 +1000         
292191  edit  2024-09-01 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.