Details of request “Trial by Jury

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
43141  sent  2019-11-15 22:57:06 +1100  waiting_response  2019-11-15 22:57:06 +1100  waiting_response  outgoing  
43271  response  2019-11-21 11:32:14 +1100        incoming  
43572  response  2019-12-05 08:57:40 +1100    2019-12-05 18:55:36 +1100  waiting_clarification  incoming  
43598  followup_sent  2019-12-05 18:55:11 +1100        outgoing  
43599  status_update  2019-12-05 18:55:36 +1100  waiting_clarification  2019-12-05 18:55:36 +1100  waiting_clarification   
43602  response  2019-12-06 08:29:50 +1100    2019-12-08 17:02:49 +1100  waiting_clarification  incoming  
43635  status_update  2019-12-08 17:02:49 +1100  waiting_clarification  2019-12-08 17:02:49 +1100  waiting_clarification   
43636  followup_sent  2019-12-08 17:05:28 +1100  waiting_response  2019-12-08 17:05:28 +1100  waiting_response  outgoing  
43666  response  2019-12-10 09:54:04 +1100    2019-12-10 16:25:22 +1100  waiting_clarification  incoming  
43676  status_update  2019-12-10 16:25:22 +1100  waiting_clarification  2019-12-10 16:25:22 +1100  waiting_clarification   
43677  followup_sent  2019-12-10 16:26:11 +1100  waiting_response  2019-12-10 16:26:11 +1100  waiting_response  outgoing  
44075  response  2019-12-23 11:49:28 +1100    2019-12-23 12:59:05 +1100  waiting_response  incoming  
44076  status_update  2019-12-23 12:59:05 +1100  waiting_response  2019-12-23 12:59:05 +1100  waiting_response   
54760  overdue  2020-01-10 00:00:00 +1100         
44395  response  2020-01-14 12:44:33 +1100    2020-01-31 15:36:52 +1100  rejected  incoming  
44738  status_update  2020-01-31 15:36:52 +1100  rejected  2020-01-31 15:36:52 +1100  rejected   
80766  edit  2022-02-01 03:45:20 +1100         
80767  edit  2022-02-01 03:45:20 +1100         
80768  edit  2022-02-01 03:45:20 +1100         
80769  edit  2022-02-01 03:45:20 +1100         
80770  edit  2022-02-01 03:45:20 +1100         
80771  edit  2022-02-01 03:45:20 +1100         
80772  edit  2022-02-01 03:45:20 +1100         
80773  edit  2022-02-01 03:45:20 +1100         
80774  edit  2022-02-01 03:45:20 +1100         
80775  edit  2022-02-01 03:45:20 +1100         
80776  edit  2022-02-01 03:45:20 +1100         
80777  edit  2022-02-01 03:45:20 +1100         
80778  edit  2022-02-01 03:45:20 +1100         
80779  edit  2022-02-01 03:45:20 +1100         
80780  edit  2022-02-01 03:45:20 +1100         
80781  edit  2022-02-01 03:45:20 +1100         

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.