Details of request “Maintenance performed by Council for Suttons Beach Pavilion

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
85550  sent  2022-03-05 22:50:52 +1100  waiting_response  2022-03-05 22:50:52 +1100  waiting_response  outgoing  
85551  response  2022-03-05 22:51:14 +1100    2022-03-06 15:33:39 +1100  waiting_response  incoming  
85651  status_update  2022-03-06 15:33:39 +1100  waiting_response  2022-03-06 15:33:39 +1100  waiting_response   
88486  response  2022-03-22 17:53:33 +1100    2022-03-27 17:27:58 +1100  waiting_response  incoming  
89004  status_update  2022-03-27 17:27:58 +1100  waiting_response  2022-03-27 17:27:58 +1100  waiting_response   
89793  overdue  2022-04-09 00:00:00 +1000         
90687  followup_sent  2022-04-10 09:01:11 +1000        outgoing  
90688  response  2022-04-10 09:01:38 +1000    2022-04-14 09:35:54 +1000  waiting_response  incoming  
91285  status_update  2022-04-14 09:35:54 +1000  waiting_response  2022-04-14 09:35:54 +1000  waiting_response   
94494  very_overdue  2022-05-05 00:00:00 +1000         
120168  edit  2022-10-14 03:45:15 +1100         
120169  edit  2022-10-14 03:45:15 +1100         
120170  edit  2022-10-14 03:45:15 +1100         
120171  edit  2022-10-14 03:45:15 +1100         
120172  edit  2022-10-14 03:45:15 +1100         
120173  edit  2022-10-14 03:45:15 +1100         
120174  edit  2022-10-14 03:45:15 +1100         
120175  edit  2022-10-14 03:45:15 +1100         
120176  edit  2022-10-14 03:45:15 +1100         
120177  edit  2022-10-14 03:45:15 +1100         
248168  edit  2024-04-14 03:45:20 +1000         
248169  edit  2024-04-14 03:45:20 +1000         
248170  edit  2024-04-14 03:45:20 +1000         
248171  edit  2024-04-14 03:45:20 +1000         
248172  edit  2024-04-14 03:45:20 +1000         
248173  edit  2024-04-14 03:45:20 +1000         
248174  edit  2024-04-14 03:45:20 +1000         
248175  edit  2024-04-14 03:45:21 +1000         
248176  edit  2024-04-14 03:45:21 +1000         
248177  edit  2024-04-14 03:45:21 +1000         
248178  edit  2024-04-14 03:45:21 +1000         
248179  edit  2024-04-14 03:45:21 +1000         
248180  edit  2024-04-14 03:45:21 +1000         
248181  edit  2024-04-14 03:45:21 +1000         
248182  edit  2024-04-14 03:45:21 +1000         
248183  edit  2024-04-14 03:45:21 +1000         
248184  edit  2024-04-14 03:45:21 +1000         
248185  edit  2024-04-14 03:45:21 +1000         
248186  edit  2024-04-14 03:45:21 +1000         
248187  edit  2024-04-14 03:45:21 +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.