Details of request “Barwon Valley School Upgrade and Modernisation - Stage 2

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
282610  sent  2024-08-04 22:17:16 +1000  waiting_response  2024-08-04 22:17:16 +1000  waiting_response  outgoing  
282869  response  2024-08-05 10:35:28 +1000    2024-08-05 10:41:23 +1000  waiting_response  incoming  
282870  status_update  2024-08-05 10:41:23 +1000  waiting_response  2024-08-05 10:41:23 +1000  waiting_response   
290538  response  2024-08-23 15:30:47 +1000    2024-08-24 18:22:10 +1000  waiting_response  incoming  
290728  status_update  2024-08-24 18:22:09 +1000  waiting_response  2024-08-24 18:22:10 +1000  waiting_response   
291070  response  2024-08-26 09:38:30 +1000    2024-08-27 16:36:12 +1000  waiting_response  incoming  
291303  followup_sent  2024-08-27 16:35:53 +1000        outgoing  
291304  status_update  2024-08-27 16:36:00 +1000  waiting_clarification  2024-08-27 16:36:00 +1000  waiting_clarification   
291305  status_update  2024-08-27 16:36:12 +1000  waiting_response  2024-08-27 16:36:12 +1000  waiting_response   
293020  overdue  2024-09-19 00:00:00 +1000         
297588  followup_sent  2024-09-19 08:48:26 +1000        outgoing  
299098  response  2024-09-26 08:01:14 +1000    2024-09-26 10:38:03 +1000  waiting_response  incoming  
299110  status_update  2024-09-26 10:38:03 +1000  waiting_response  2024-09-26 10:38:03 +1000  waiting_response   
301615  response  2024-10-02 09:28:43 +1000    2024-10-02 10:32:23 +1000  waiting_response  incoming  
301618  status_update  2024-10-02 10:32:23 +1000  waiting_response  2024-10-02 10:32:23 +1000  waiting_response   
307316  overdue  2024-11-05 00:00:00 +1100         
314686  very_overdue  2024-11-19 00:00:00 +1100         
315068  followup_sent  2024-11-21 13:33:46 +1100  internal_review  2024-11-21 13:33:46 +1100  internal_review  outgoing  
315069  status_update  2024-11-21 13:34:10 +1100  internal_review  2024-11-21 13:34:10 +1100  internal_review   
320398  followup_sent  2024-12-03 16:13:40 +1100        outgoing  
322485  response  2024-12-06 09:42:34 +1100    2024-12-06 14:44:07 +1100  waiting_response  incoming  
322522  status_update  2024-12-06 14:44:07 +1100  waiting_response  2024-12-06 14:44:07 +1100  waiting_response   
336256  followup_sent  2025-01-15 10:58:00 +1100        outgoing  
336680  response  2025-01-16 08:08:28 +1100    2025-01-16 13:30:29 +1100  waiting_response  incoming  
336726  status_update  2025-01-16 13:30:29 +1100  waiting_response  2025-01-16 13:30:29 +1100  waiting_response   
339513  response  2025-01-23 12:37:35 +1100        incoming  
339514  response  2025-01-23 12:41:16 +1100        incoming  
339515  response  2025-01-23 12:50:10 +1100        incoming  
339517  response  2025-01-23 13:03:49 +1100        incoming  
339518  response  2025-01-23 13:06:10 +1100    2025-01-23 14:31:24 +1100  successful  incoming  
339528  followup_sent  2025-01-23 14:31:19 +1100        outgoing  
339529  status_update  2025-01-23 14:31:24 +1100  successful  2025-01-23 14:31:24 +1100  successful   
409273  edit  2025-07-24 03:45:19 +1000         
409274  edit  2025-07-24 03:45:19 +1000         
409275  edit  2025-07-24 03:45:19 +1000         
409276  edit  2025-07-24 03:45:19 +1000         
409277  edit  2025-07-24 03:45:19 +1000         
409278  edit  2025-07-24 03:45:20 +1000         
409279  edit  2025-07-24 03:45:20 +1000         
409280  edit  2025-07-24 03:45:20 +1000         
409281  edit  2025-07-24 03:45:20 +1000         
409282  edit  2025-07-24 03:45:20 +1000         
409283  edit  2025-07-24 03:45:20 +1000         
409284  edit  2025-07-24 03:45:20 +1000         
409285  edit  2025-07-24 03:45:20 +1000         
409286  edit  2025-07-24 03:45:20 +1000         
409287  edit  2025-07-24 03:45:20 +1000         
409288  edit  2025-07-24 03:45:20 +1000         
409289  edit  2025-07-24 03:45:20 +1000         
409290  edit  2025-07-24 03:45:20 +1000         
409291  edit  2025-07-24 03:45:20 +1000         
409292  edit  2025-07-24 03:45:20 +1000         
409293  edit  2025-07-24 03:45:20 +1000         
409294  edit  2025-07-24 03:45:20 +1000         
409295  edit  2025-07-24 03:45:20 +1000         
409296  edit  2025-07-24 03:45:20 +1000         
409297  edit  2025-07-24 03:45:20 +1000         
409298  edit  2025-07-24 03:45:20 +1000         
409299  edit  2025-07-24 03:45:20 +1000         
409300  edit  2025-07-24 03:45:20 +1000         
409301  edit  2025-07-24 03:45:20 +1000         
409302  edit  2025-07-24 03:45:20 +1000         
409303  edit  2025-07-24 03:45:20 +1000         
409304  edit  2025-07-24 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.