Details of request “Victoria School Building Authority - workplace culture

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
38029  sent  2019-01-15 12:45:09 +1100  waiting_response  2019-01-15 12:45:09 +1100  waiting_response  outgoing  
38049  response  2019-01-16 10:17:37 +1100        incoming  
38135  response  2019-01-22 11:02:15 +1100    2019-01-23 17:26:33 +1100  waiting_clarification  incoming  
38167  status_update  2019-01-23 17:26:33 +1100  waiting_clarification  2019-01-23 17:26:33 +1100  waiting_clarification   
38168  followup_sent  2019-01-23 17:28:54 +1100  waiting_response  2019-01-23 17:28:54 +1100  waiting_response  outgoing  
38177  response  2019-01-24 15:37:54 +1100    2019-02-04 07:58:20 +1100  waiting_response  incoming  
38353  status_update  2019-02-04 07:58:20 +1100  waiting_response  2019-02-04 07:58:20 +1100  waiting_response   
38570  response  2019-02-15 07:44:45 +1100    2019-02-20 14:17:16 +1100  waiting_response  incoming  
38662  status_update  2019-02-20 14:17:16 +1100  waiting_response  2019-02-20 14:17:16 +1100  waiting_response   
54536  overdue  2019-02-23 00:00:00 +1100         
38740  followup_sent  2019-02-26 17:33:02 +1100        outgoing  
38741  status_update  2019-02-26 17:35:16 +1100  waiting_response  2019-02-26 17:35:16 +1100  waiting_response   
38754  edit_incoming  2019-02-27 12:10:27 +1100        incoming  
38841  response  2019-03-06 15:28:33 +1100    2019-03-13 11:50:10 +1100  waiting_response  incoming  
38933  status_update  2019-03-13 11:50:10 +1100  waiting_response  2019-03-13 11:50:10 +1100  waiting_response   
38936  followup_sent  2019-03-13 12:03:12 +1100        outgoing  
39019  response  2019-03-18 17:01:24 +1100    2019-03-21 21:36:12 +1100  waiting_response  incoming  
39080  followup_sent  2019-03-21 21:36:03 +1100        outgoing  
39081  status_update  2019-03-21 21:36:12 +1100  waiting_response  2019-03-21 21:36:12 +1100  waiting_response   
56267  very_overdue  2019-03-26 00:00:00 +1100         
39153  response  2019-03-26 15:00:44 +1100    2019-03-27 12:32:04 +1100  waiting_response  incoming  
39169  followup_sent  2019-03-27 12:31:51 +1100        outgoing  
39170  status_update  2019-03-27 12:32:04 +1100  waiting_response  2019-03-27 12:32:04 +1100  waiting_response   
39272  response  2019-04-02 16:54:16 +1100    2019-04-02 18:13:00 +1100  waiting_response  incoming  
39274  followup_sent  2019-04-02 18:12:54 +1100        outgoing  
39275  status_update  2019-04-02 18:13:00 +1100  waiting_response  2019-04-02 18:13:00 +1100  waiting_response   
40249  response  2019-05-24 15:33:29 +1000    2019-05-28 07:29:40 +1000  partially_successful  incoming  
40277  status_update  2019-05-28 07:29:40 +1000  partially_successful  2019-05-28 07:29:40 +1000  partially_successful   

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.