Details of request “Citizenship ceremony backlog for Greater Sydney

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
111112  sent  2022-08-23 23:45:43 +1000  waiting_response  2022-08-23 23:45:43 +1000  waiting_response  outgoing  
111113  response  2022-08-23 23:46:23 +1000        incoming  
111547  response  2022-08-25 16:56:03 +1000    2022-08-26 10:57:31 +1000  waiting_clarification  incoming  
111665  followup_sent  2022-08-26 10:57:24 +1000        outgoing  
111666  status_update  2022-08-26 10:57:31 +1000  waiting_clarification  2022-08-26 10:57:31 +1000  waiting_clarification   
112515  response  2022-08-30 16:39:13 +1000    2022-09-01 15:45:31 +1000  user_withdrawn  incoming  
112754  status_update  2022-09-01 15:45:12 +1000  waiting_response  2022-09-01 15:45:12 +1000  waiting_response   
112755  status_update  2022-09-01 15:45:30 +1000  user_withdrawn  2022-09-01 15:45:31 +1000  user_withdrawn   
112756  followup_sent  2022-09-01 15:45:51 +1000        outgoing  
112896  response  2022-09-02 09:34:40 +1000        incoming  
146632  edit  2023-03-02 03:45:16 +1100         
146633  edit  2023-03-02 03:45:16 +1100         
146634  edit  2023-03-02 03:45:16 +1100         
146635  edit  2023-03-02 03:45:16 +1100         
146636  edit  2023-03-02 03:45:16 +1100         
146637  edit  2023-03-02 03:45:16 +1100         
146638  edit  2023-03-02 03:45:16 +1100         
146639  edit  2023-03-02 03:45:16 +1100         
146640  edit  2023-03-02 03:45:16 +1100         
146641  edit  2023-03-02 03:45:16 +1100         
292472  edit  2024-09-02 03:45:21 +1000         
292473  edit  2024-09-02 03:45:21 +1000         
292474  edit  2024-09-02 03:45:21 +1000         
292475  edit  2024-09-02 03:45:21 +1000         
292476  edit  2024-09-02 03:45:21 +1000         
292477  edit  2024-09-02 03:45:21 +1000         
292478  edit  2024-09-02 03:45:21 +1000         
292479  edit  2024-09-02 03:45:21 +1000         
292480  edit  2024-09-02 03:45:21 +1000         
292481  edit  2024-09-02 03:45:21 +1000         
292482  edit  2024-09-02 03:45:22 +1000         
292483  edit  2024-09-02 03:45:22 +1000         
292484  edit  2024-09-02 03:45:22 +1000         
292485  edit  2024-09-02 03:45:22 +1000         
292486  edit  2024-09-02 03:45:22 +1000         
292487  edit  2024-09-02 03:45:22 +1000         
292488  edit  2024-09-02 03:45:22 +1000         
292489  edit  2024-09-02 03:45:22 +1000         
292490  edit  2024-09-02 03:45:22 +1000         
292491  edit  2024-09-02 03:45:22 +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.