Details of request “Unlawful actions Fines Victoria

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
33955  sent  2018-07-09 15:43:51 +1000  waiting_response  2018-07-09 15:43:51 +1000  waiting_response  outgoing  
33956  response  2018-07-09 15:44:12 +1000    2018-07-13 11:49:06 +1000  waiting_response  incoming  
34017  status_update  2018-07-13 11:49:06 +1000  waiting_response  2018-07-13 11:49:06 +1000  waiting_response   
54342  overdue  2018-08-09 00:00:00 +1000         
34558  followup_sent  2018-08-24 09:21:14 +1000        outgoing  
34560  response  2018-08-24 10:26:37 +1000    2018-08-24 10:51:46 +1000  waiting_clarification  incoming  
34561  status_update  2018-08-24 10:51:46 +1000  waiting_clarification  2018-08-24 10:51:46 +1000  waiting_clarification   
34562  followup_sent  2018-08-24 10:53:07 +1000  waiting_response  2018-08-24 10:53:07 +1000  waiting_response  outgoing  
34563  response  2018-08-24 11:18:06 +1000        incoming  
34564  followup_sent  2018-08-24 11:25:37 +1000        outgoing  
34565  response  2018-08-24 11:28:10 +1000    2018-08-24 15:49:36 +1000  waiting_clarification  incoming  
34570  status_update  2018-08-24 15:49:36 +1000  waiting_clarification  2018-08-24 15:49:36 +1000  waiting_clarification   
34571  followup_sent  2018-08-24 15:53:10 +1000  waiting_response  2018-08-24 15:53:10 +1000  waiting_response  outgoing  
34573  response  2018-08-24 17:19:06 +1000    2018-08-28 09:48:44 +1000  waiting_clarification  incoming  
34610  status_update  2018-08-28 09:48:44 +1000  waiting_clarification  2018-08-28 09:48:44 +1000  waiting_clarification   
34611  followup_sent  2018-08-28 09:49:10 +1000  waiting_response  2018-08-28 09:49:10 +1000  waiting_response  outgoing  
54378  overdue  2018-09-28 00:00:00 +1000         
56136  very_overdue  2018-10-30 00:00:00 +1100         
36047  followup_sent  2018-10-30 10:15:22 +1100  internal_review  2018-10-30 10:15:22 +1100  internal_review  outgoing  
36070  response  2018-10-30 16:54:44 +1100    2018-10-30 17:16:34 +1100  internal_review  incoming  
36072  followup_sent  2018-10-30 17:16:18 +1100        outgoing  
36073  status_update  2018-10-30 17:16:34 +1100  internal_review  2018-10-30 17:16:34 +1100  internal_review   
36075  response  2018-10-30 17:25:05 +1100    2018-10-30 18:10:08 +1100  internal_review  incoming  
36076  followup_sent  2018-10-30 18:09:56 +1100        outgoing  
36077  status_update  2018-10-30 18:10:08 +1100  internal_review  2018-10-30 18:10:08 +1100  internal_review   
36083  response  2018-10-31 13:04:21 +1100    2018-10-31 13:15:01 +1100  internal_review  incoming  
36084  status_update  2018-10-31 13:15:01 +1100  internal_review  2018-10-31 13:15:01 +1100  internal_review   

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.