Details of request “documents relating to Trans-Pacific Partnership (TPP) Ministerial meeting in Atlanta, Georgia, USA on Sep.-Oct. 2015

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
11655  sent  2015-12-23 12:14:45 +1100  waiting_response  2015-12-23 12:14:45 +1100  waiting_response  outgoing  
11731  response  2015-12-30 11:03:59 +1100    2016-01-03 08:56:13 +1100  waiting_response  incoming  
11760  status_update  2016-01-03 08:56:12 +1100  waiting_response  2016-01-03 08:56:13 +1100  waiting_response   
11884  response  2016-01-11 08:37:14 +1100    2016-01-11 12:24:11 +1100  waiting_clarification  incoming  
11890  status_update  2016-01-11 12:24:09 +1100  waiting_clarification  2016-01-11 12:24:11 +1100  waiting_clarification   
11892  followup_sent  2016-01-11 13:04:54 +1100  waiting_response  2016-01-11 13:04:55 +1100  waiting_response  outgoing  
11894  response  2016-01-11 14:22:56 +1100    2016-01-11 16:02:56 +1100  waiting_clarification  incoming  
11895  status_update  2016-01-11 16:02:56 +1100  waiting_clarification  2016-01-11 16:02:56 +1100  waiting_clarification   
11896  followup_sent  2016-01-11 16:04:25 +1100  waiting_response  2016-01-11 16:04:25 +1100  waiting_response  outgoing  
11898  response  2016-01-11 16:22:56 +1100    2016-01-11 17:04:52 +1100  waiting_response  incoming  
11901  status_update  2016-01-11 17:04:51 +1100  waiting_response  2016-01-11 17:04:52 +1100  waiting_response   
12029  response  2016-01-19 11:14:16 +1100    2016-01-24 13:27:19 +1100  waiting_clarification  incoming  
12103  followup_sent  2016-01-24 13:27:07 +1100        outgoing  
12104  status_update  2016-01-24 13:27:19 +1100  waiting_clarification  2016-01-24 13:27:19 +1100  waiting_clarification   
12105  followup_sent  2016-01-24 13:28:35 +1100  waiting_response  2016-01-24 13:28:35 +1100  waiting_response  outgoing  
53263  overdue  2016-02-24 00:00:00 +1100         
12573  followup_sent  2016-02-24 11:31:40 +1100        outgoing  
12574  response  2016-02-24 11:32:15 +1100        incoming  
12644  response  2016-02-25 17:28:28 +1100    2016-02-25 17:42:17 +1100  waiting_clarification  incoming  
12645  status_update  2016-02-25 17:42:16 +1100  waiting_clarification  2016-02-25 17:42:17 +1100  waiting_clarification   
12648  followup_sent  2016-02-25 17:56:10 +1100  waiting_response  2016-02-25 17:56:10 +1100  waiting_response  outgoing  
13080  followup_sent  2016-03-11 18:15:35 +1100        outgoing  
13281  response  2016-03-23 10:39:26 +1100        incoming  
13302  followup_sent  2016-03-24 03:47:18 +1100  internal_review  2016-03-24 03:47:18 +1100  internal_review  outgoing  
13619  response  2016-04-06 11:19:05 +1000        incoming  
14112  response  2016-04-26 13:32:00 +1000    2016-04-30 10:01:09 +1000  not_held  incoming  
14189  status_update  2016-04-30 10:01:09 +1000  not_held  2016-04-30 10:01:09 +1000  not_held   

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.