Details of request “Litigation update 22 August

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
230638  sent  2024-02-15 10:20:18 +1100  waiting_response  2024-02-15 10:20:18 +1100  waiting_response  outgoing  
230639  response  2024-02-15 10:21:24 +1100    2024-02-16 13:16:04 +1100  waiting_response  incoming  
230793  status_update  2024-02-16 13:16:04 +1100  waiting_response  2024-02-16 13:16:04 +1100  waiting_response   
230794  status_update  2024-02-16 13:16:25 +1100  waiting_response  2024-02-16 13:16:25 +1100  waiting_response   
230795  status_update  2024-02-16 13:16:42 +1100  waiting_response  2024-02-16 13:16:42 +1100  waiting_response   
230796  status_update  2024-02-16 13:17:02 +1100  waiting_response  2024-02-16 13:17:02 +1100  waiting_response   
230797  status_update  2024-02-16 13:17:36 +1100  waiting_response  2024-02-16 13:17:36 +1100  waiting_response   
232472  response  2024-02-19 10:01:24 +1100    2024-02-19 11:26:53 +1100  waiting_response  incoming  
232498  status_update  2024-02-19 11:26:53 +1100  waiting_response  2024-02-19 11:26:53 +1100  waiting_response   
238609  response  2024-03-07 14:37:41 +1100    2024-03-12 15:20:07 +1100  waiting_response  incoming  
239732  status_update  2024-03-12 15:20:07 +1100  waiting_response  2024-03-12 15:20:07 +1100  waiting_response   
241202  overdue  2024-03-19 00:00:00 +1100         
249510  very_overdue  2024-04-16 00:00:00 +1000         
250001  followup_sent  2024-04-18 09:24:04 +1000  internal_review  2024-04-18 09:24:04 +1000  internal_review  outgoing  
250003  response  2024-04-18 09:24:55 +1000    2024-04-22 14:18:19 +1000  waiting_response  incoming  
251668  status_update  2024-04-22 14:18:19 +1000  waiting_response  2024-04-22 14:18:19 +1000  waiting_response   
253236  response  2024-04-29 17:16:41 +1000    2024-05-01 12:51:14 +1000  rejected  incoming  
253753  status_update  2024-05-01 12:51:14 +1000  rejected  2024-05-01 12:51:14 +1000  rejected   
310092  edit  2024-11-02 03:45:18 +1100         
310093  edit  2024-11-02 03:45:18 +1100         
310094  edit  2024-11-02 03:45:18 +1100         
310095  edit  2024-11-02 03:45:18 +1100         
310096  edit  2024-11-02 03:45:18 +1100         
310097  edit  2024-11-02 03:45:18 +1100         
310098  edit  2024-11-02 03:45:18 +1100         
310099  edit  2024-11-02 03:45:18 +1100         
310100  edit  2024-11-02 03:45:18 +1100         
310101  edit  2024-11-02 03:45:18 +1100         
310102  edit  2024-11-02 03:45:18 +1100         
310103  edit  2024-11-02 03:45:18 +1100         
310104  edit  2024-11-02 03:45:19 +1100         
310105  edit  2024-11-02 03:45:19 +1100         
310106  edit  2024-11-02 03:45:19 +1100         
310107  edit  2024-11-02 03:45:19 +1100         
310108  edit  2024-11-02 03:45:19 +1100         
310109  edit  2024-11-02 03:45:19 +1100         

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.