Details of request “2016-17 Most Expensive Trip

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
28044  sent  2017-08-08 16:50:35 +1000  waiting_response  2017-08-08 16:50:35 +1000  waiting_response  outgoing  
28055  response  2017-08-08 16:52:21 +1000        incoming  
28569  response  2017-08-14 12:11:16 +1000    2017-08-16 17:47:57 +1000  waiting_clarification  incoming  
28689  followup_sent  2017-08-16 17:46:53 +1000        outgoing  
28690  status_update  2017-08-16 17:47:57 +1000  waiting_clarification  2017-08-16 17:47:57 +1000  waiting_clarification   
28691  response  2017-08-16 17:48:02 +1000        incoming  
28721  response  2017-08-17 07:52:25 +1000        incoming  
28916  followup_sent  2017-08-22 11:23:55 +1000  waiting_response  2017-08-22 11:23:55 +1000  waiting_response  outgoing  
28918  response  2017-08-22 11:24:59 +1000        incoming  
29047  response  2017-08-25 16:06:10 +1000    2017-08-31 12:13:32 +1000  waiting_clarification  incoming  
29153  followup_sent  2017-08-31 12:13:27 +1000        outgoing  
29154  status_update  2017-08-31 12:13:32 +1000  waiting_clarification  2017-08-31 12:13:32 +1000  waiting_clarification   
29155  response  2017-08-31 12:14:27 +1000        incoming  
29234  response  2017-09-04 16:20:03 +1000        incoming  
30389  followup_sent  2017-10-30 16:01:16 +1100  waiting_response  2017-10-30 16:01:16 +1100  waiting_response  outgoing  
30390  status_update  2017-10-30 16:01:27 +1100  waiting_clarification  2017-10-30 16:01:27 +1100  waiting_clarification   
30394  response  2017-10-30 16:02:33 +1100    2017-10-30 16:05:05 +1100  not_held  incoming  
30398  status_update  2017-10-30 16:05:05 +1100  not_held  2017-10-30 16:05:05 +1100  not_held   
30419  response  2017-10-31 11:24:20 +1100        incoming  
30596  response  2017-11-15 08:27:04 +1100    2017-12-21 13:29:25 +1100  waiting_response  incoming  
30630  followup_sent  2017-11-15 22:44:26 +1100        outgoing  
54174  overdue  2017-12-16 00:00:00 +1100         
31170  status_update  2017-12-21 13:29:25 +1100  waiting_response  2017-12-21 13:29:25 +1100  waiting_response   
55997  very_overdue  2018-01-16 00:00:00 +1100         
32519  response  2018-04-10 12:36:10 +1000        incoming  
32937  response  2018-05-04 11:34:04 +1000        incoming  
33006  response  2018-05-11 12:47:27 +1000    2018-05-31 07:37:37 +1000  partially_successful  incoming  
33309  status_update  2018-05-31 07:37:37 +1000  partially_successful  2018-05-31 07:37:37 +1000  partially_successful   
34166  response  2018-07-25 13:05:56 +1000    2018-07-25 13:15:23 +1000  waiting_clarification  incoming  
34167  followup_sent  2018-07-25 13:15:08 +1000        outgoing  
34168  status_update  2018-07-25 13:15:23 +1000  waiting_clarification  2018-07-25 13:15:23 +1000  waiting_clarification   

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.