Details of request “Justice Jillian Williams

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
140204  sent  2023-01-27 15:26:38 +1100  waiting_response  2023-01-27 15:26:38 +1100  waiting_response  outgoing  
140205  response  2023-01-27 15:26:55 +1100    2023-01-27 15:49:19 +1100  waiting_response  incoming  
140210  status_update  2023-01-27 15:49:19 +1100  waiting_response  2023-01-27 15:49:19 +1100  waiting_response   
144563  response  2023-02-17 12:10:29 +1100    2023-02-18 01:29:12 +1100  waiting_response  incoming  
144573  status_update  2023-02-18 01:29:12 +1100  waiting_response  2023-02-18 01:29:12 +1100  waiting_response   
145205  response  2023-02-21 13:05:53 +1100    2023-02-21 16:09:26 +1100  waiting_response  incoming  
145232  status_update  2023-02-21 16:09:26 +1100  waiting_response  2023-02-21 16:09:26 +1100  waiting_response   
146269  response  2023-02-27 17:19:04 +1100    2023-02-28 12:19:59 +1100  successful  incoming  
146274  status_update  2023-02-27 18:12:07 +1100  waiting_clarification  2023-02-27 18:12:07 +1100  waiting_clarification   
146374  status_update  2023-02-28 12:19:59 +1100  successful  2023-02-28 12:19:59 +1100  successful   
184633  edit  2023-09-01 03:45:14 +1000         
184634  edit  2023-09-01 03:45:15 +1000         
184635  edit  2023-09-01 03:45:15 +1000         
184636  edit  2023-09-01 03:45:15 +1000         
184637  edit  2023-09-01 03:45:15 +1000         
184638  edit  2023-09-01 03:45:15 +1000         
184639  edit  2023-09-01 03:45:15 +1000         
184640  edit  2023-09-01 03:45:15 +1000         
184641  edit  2023-09-01 03:45:15 +1000         
184642  edit  2023-09-01 03:45:15 +1000         
354775  edit  2025-03-01 03:48:13 +1100         
354776  edit  2025-03-01 03:48:13 +1100         
354777  edit  2025-03-01 03:48:13 +1100         
354778  edit  2025-03-01 03:48:14 +1100         
354779  edit  2025-03-01 03:48:14 +1100         
354780  edit  2025-03-01 03:48:14 +1100         
354781  edit  2025-03-01 03:48:14 +1100         
354782  edit  2025-03-01 03:48:14 +1100         
354783  edit  2025-03-01 03:48:15 +1100         
354784  edit  2025-03-01 03:48:15 +1100         
354785  edit  2025-03-01 03:48:15 +1100         
354786  edit  2025-03-01 03:48:15 +1100         
354787  edit  2025-03-01 03:48:15 +1100         
354788  edit  2025-03-01 03:48:16 +1100         
354789  edit  2025-03-01 03:48:16 +1100         
354790  edit  2025-03-01 03:48:16 +1100         
354791  edit  2025-03-01 03:48:16 +1100         
354792  edit  2025-03-01 03:48:16 +1100         
354793  edit  2025-03-01 03:48:16 +1100         
354794  edit  2025-03-01 03:48:17 +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.