Details of request “Reducing ambulance response time

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
108527  sent  2022-08-08 04:39:35 +1000  waiting_response  2022-08-08 04:39:35 +1000  waiting_response  outgoing  
108799  response  2022-08-10 11:00:50 +1000    2022-08-12 09:23:54 +1000  waiting_response  incoming  
109076  status_update  2022-08-12 09:23:53 +1000  waiting_response  2022-08-12 09:23:54 +1000  waiting_response   
109077  followup_sent  2022-08-12 09:25:15 +1000  internal_review  2022-08-12 09:25:15 +1000  internal_review  outgoing  
110226  response  2022-08-19 13:08:48 +1000    2022-09-05 13:25:09 +1000  waiting_response  incoming  
113619  followup_sent  2022-09-05 13:25:01 +1000        outgoing  
113620  status_update  2022-09-05 13:25:09 +1000  waiting_response  2022-09-05 13:25:09 +1000  waiting_response   
114910  response  2022-09-13 12:03:32 +1000    2022-09-30 14:36:07 +1000  rejected  incoming  
113994  overdue  2022-09-23 00:00:00 +1000         
117802  status_update  2022-09-30 14:36:07 +1000  rejected  2022-09-30 14:36:07 +1000  rejected   
151527  edit  2023-04-01 03:45:15 +1100         
151528  edit  2023-04-01 03:45:15 +1100         
151529  edit  2023-04-01 03:45:15 +1100         
151530  edit  2023-04-01 03:45:15 +1100         
151531  edit  2023-04-01 03:45:16 +1100         
151532  edit  2023-04-01 03:45:16 +1100         
151533  edit  2023-04-01 03:45:16 +1100         
151534  edit  2023-04-01 03:45:16 +1100         
151535  edit  2023-04-01 03:45:16 +1100         
151536  edit  2023-04-01 03:45:16 +1100         
301092  edit  2024-10-01 03:45:18 +1000         
301093  edit  2024-10-01 03:45:18 +1000         
301094  edit  2024-10-01 03:45:18 +1000         
301095  edit  2024-10-01 03:45:18 +1000         
301096  edit  2024-10-01 03:45:18 +1000         
301097  edit  2024-10-01 03:45:18 +1000         
301098  edit  2024-10-01 03:45:18 +1000         
301099  edit  2024-10-01 03:45:18 +1000         
301100  edit  2024-10-01 03:45:18 +1000         
301101  edit  2024-10-01 03:45:18 +1000         
301102  edit  2024-10-01 03:45:18 +1000         
301103  edit  2024-10-01 03:45:18 +1000         
301104  edit  2024-10-01 03:45:18 +1000         
301105  edit  2024-10-01 03:45:18 +1000         
301106  edit  2024-10-01 03:45:18 +1000         
301107  edit  2024-10-01 03:45:18 +1000         
301108  edit  2024-10-01 03:45:18 +1000         
301109  edit  2024-10-01 03:45:18 +1000         
301110  edit  2024-10-01 03:45:18 +1000         
301111  edit  2024-10-01 03:45:18 +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.