Details of request “FOI Request for Detail Incident Report 1-736A1L

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
31029  sent  2017-12-13 17:02:01 +1100  waiting_response  2017-12-13 17:02:01 +1100  waiting_response  outgoing  
31030  response  2017-12-13 17:03:29 +1100    2017-12-13 17:04:01 +1100  waiting_response  incoming  
31031  status_update  2017-12-13 17:04:01 +1100  waiting_response  2017-12-13 17:04:01 +1100  waiting_response   
31071  response  2017-12-15 15:10:52 +1100    2018-01-09 21:42:00 +1100  waiting_response  incoming  
31335  status_update  2018-01-09 21:42:00 +1100  waiting_response  2018-01-09 21:42:00 +1100  waiting_response   
31346  response  2018-01-11 08:33:51 +1100    2018-01-16 09:27:33 +1100  waiting_response  incoming  
54193  overdue  2018-01-13 00:00:00 +1100         
31455  status_update  2018-01-16 09:27:33 +1100  waiting_response  2018-01-16 09:27:33 +1100  waiting_response   
56010  very_overdue  2018-02-14 00:00:00 +1100         
31865  followup_sent  2018-02-14 10:44:23 +1100  internal_review  2018-02-14 10:44:23 +1100  internal_review  outgoing  
31866  response  2018-02-14 10:45:55 +1100    2018-02-14 10:57:03 +1100  internal_review  incoming  
31867  status_update  2018-02-14 10:57:03 +1100  internal_review  2018-02-14 10:57:03 +1100  internal_review   
32457  response  2018-04-06 16:00:20 +1000    2018-04-09 20:23:37 +1000  internal_review  incoming  
32492  followup_sent  2018-04-09 20:23:21 +1000        outgoing  
32493  status_update  2018-04-09 20:23:37 +1000  internal_review  2018-04-09 20:23:37 +1000  internal_review   
32494  response  2018-04-09 20:24:19 +1000    2018-04-10 20:26:29 +1000  internal_review  incoming  
32528  status_update  2018-04-10 20:26:29 +1000  internal_review  2018-04-10 20:26:29 +1000  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.