Details of request “Official travel

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
41981  sent  2019-10-02 09:36:13 +1000  waiting_response  2019-10-02 09:36:13 +1000  waiting_response  outgoing  
41982  response  2019-10-02 09:37:05 +1000        incoming  
42010  response  2019-10-03 15:41:14 +1000        incoming  
42067  response  2019-10-09 12:58:59 +1100        incoming  
42155  followup_sent  2019-10-14 22:03:11 +1100        outgoing  
42156  response  2019-10-14 22:04:21 +1100        incoming  
42235  response  2019-10-17 12:37:18 +1100        incoming  
42786  response  2019-11-04 13:55:53 +1100    2019-11-19 17:21:05 +1100  rejected  incoming  
43216  status_update  2019-11-19 17:21:05 +1100  rejected  2019-11-19 17:21:05 +1100  rejected   
43217  followup_sent  2019-11-19 17:24:34 +1100  internal_review  2019-11-19 17:24:34 +1100  internal_review  outgoing  
43218  response  2019-11-19 17:25:40 +1100        incoming  
43985  response  2019-12-19 17:28:00 +1100    2020-01-09 22:53:00 +1100  rejected  incoming  
44320  status_update  2020-01-09 22:53:00 +1100  rejected  2020-01-09 22:53:00 +1100  rejected   
44321  followup_sent  2020-01-09 22:53:52 +1100  internal_review  2020-01-09 22:53:52 +1100  internal_review  outgoing  
44322  response  2020-01-09 22:54:34 +1100        incoming  
44377  response  2020-01-13 15:41:23 +1100    2020-07-09 14:06:13 +1000  rejected  incoming  
47537  status_update  2020-07-09 14:06:13 +1000  rejected  2020-07-09 14:06:13 +1000  rejected   
102289  edit  2022-07-10 03:45:23 +1000         
102290  edit  2022-07-10 03:45:23 +1000         
102291  edit  2022-07-10 03:45:23 +1000         
102292  edit  2022-07-10 03:45:23 +1000         
102293  edit  2022-07-10 03:45:23 +1000         
102294  edit  2022-07-10 03:45:23 +1000         
102295  edit  2022-07-10 03:45:23 +1000         
102296  edit  2022-07-10 03:45:23 +1000         
102297  edit  2022-07-10 03:45:23 +1000         
102298  edit  2022-07-10 03:45:24 +1000         
102299  edit  2022-07-10 03:45:24 +1000         
102300  edit  2022-07-10 03:45:24 +1000         
102301  edit  2022-07-10 03:45:24 +1000         
102302  edit  2022-07-10 03:45:24 +1000         
102303  edit  2022-07-10 03:45:24 +1000         
102304  edit  2022-07-10 03:45:24 +1000         
102305  edit  2022-07-10 03:45:24 +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.