Details of request “Number of Applicants who moved from all Council's Sydney Metro area to City of Ryde Council

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
89815  sent  2022-04-05 12:01:54 +1000  waiting_response  2022-04-05 12:01:54 +1000  waiting_response  outgoing  
89816  response  2022-04-05 12:03:42 +1000    2022-04-05 12:16:28 +1000  waiting_response  incoming  
89817  status_update  2022-04-05 12:16:28 +1000  waiting_response  2022-04-05 12:16:28 +1000  waiting_response   
89912  response  2022-04-06 17:28:34 +1000    2022-04-07 11:08:14 +1000  waiting_response  incoming  
90260  status_update  2022-04-07 11:08:14 +1000  waiting_response  2022-04-07 11:08:14 +1000  waiting_response   
91211  response  2022-04-13 15:34:10 +1000    2022-04-13 15:54:48 +1000  waiting_response  incoming  
91212  followup_sent  2022-04-13 15:54:33 +1000        outgoing  
91213  status_update  2022-04-13 15:54:48 +1000  waiting_response  2022-04-13 15:54:48 +1000  waiting_response   
94571  overdue  2022-05-06 00:00:00 +1000         
96088  response  2022-05-17 15:46:27 +1000    2022-05-17 15:50:56 +1000  successful  incoming  
96089  status_update  2022-05-17 15:50:56 +1000  successful  2022-05-17 15:50:56 +1000  successful   
126039  edit  2022-11-18 03:45:17 +1100         
126040  edit  2022-11-18 03:45:17 +1100         
126041  edit  2022-11-18 03:45:17 +1100         
126042  edit  2022-11-18 03:45:17 +1100         
126043  edit  2022-11-18 03:45:17 +1100         
126044  edit  2022-11-18 03:45:17 +1100         
126045  edit  2022-11-18 03:45:17 +1100         
126046  edit  2022-11-18 03:45:17 +1100         
126047  edit  2022-11-18 03:45:17 +1100         
126048  edit  2022-11-18 03:45:17 +1100         
126049  edit  2022-11-18 03:45:17 +1100         
259593  edit  2024-05-18 03:45:15 +1000         
259594  edit  2024-05-18 03:45:15 +1000         
259595  edit  2024-05-18 03:45:16 +1000         
259596  edit  2024-05-18 03:45:16 +1000         
259597  edit  2024-05-18 03:45:16 +1000         
259598  edit  2024-05-18 03:45:16 +1000         
259599  edit  2024-05-18 03:45:16 +1000         
259600  edit  2024-05-18 03:45:16 +1000         
259601  edit  2024-05-18 03:45:16 +1000         
259602  edit  2024-05-18 03:45:16 +1000         
259603  edit  2024-05-18 03:45:16 +1000         
259604  edit  2024-05-18 03:45:16 +1000         
259605  edit  2024-05-18 03:45:16 +1000         
259606  edit  2024-05-18 03:45:16 +1000         
259607  edit  2024-05-18 03:45:16 +1000         
259608  edit  2024-05-18 03:45:16 +1000         
259609  edit  2024-05-18 03:45:16 +1000         
259610  edit  2024-05-18 03:45:16 +1000         
259611  edit  2024-05-18 03:45:16 +1000         
259612  edit  2024-05-18 03:45:16 +1000         
259613  edit  2024-05-18 03:45:16 +1000         
259614  edit  2024-05-18 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.