Details of request “Trans-Pacific Partnership Agreement”

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
73	sent	2012-11-21 10:59:59 +1100	waiting_response	2012-11-21 11:00:00 +1100	waiting_response	outgoing
74	response	2012-11-21 15:03:14 +1100	waiting_response	2012-11-21 15:17:33 +1100	waiting_response	incoming
155	response	2012-12-10 13:06:46 +1100	waiting_clarification	2012-12-10 13:10:25 +1100	waiting_clarification	incoming
187	followup_sent	2012-12-17 22:22:11 +1100	waiting_response	2012-12-17 22:22:11 +1100	waiting_response	outgoing
206	response	2012-12-20 10:14:19 +1100	waiting_response	2012-12-21 10:24:33 +1100	waiting_response	incoming
216	followup_sent	2012-12-21 10:30:39 +1100				outgoing
217	response	2012-12-21 11:20:51 +1100	waiting_response	2012-12-21 11:49:20 +1100	waiting_response	incoming
308	followup_sent	2013-01-15 12:01:28 +1100				outgoing
309	response	2013-01-15 12:41:50 +1100	waiting_response	2013-01-15 12:43:23 +1100	waiting_response	incoming
310	followup_sent	2013-01-15 12:47:13 +1100				outgoing
52764	overdue	2013-01-17 00:00:00 +1100
419	followup_sent	2013-02-06 19:28:03 +1100				outgoing
473	response	2013-02-11 16:59:11 +1100	waiting_clarification	2013-02-11 18:08:21 +1100	waiting_clarification	incoming
477	followup_sent	2013-02-12 13:32:05 +1100	waiting_response	2013-02-12 13:32:05 +1100	waiting_response	outgoing
486	response	2013-02-13 14:51:46 +1100	waiting_response	2013-02-13 14:52:29 +1100	waiting_response	incoming
487	followup_sent	2013-02-13 14:53:30 +1100				outgoing
489	response	2013-02-13 15:02:12 +1100	waiting_response	2013-02-14 10:03:47 +1100	waiting_response	incoming
539	response	2013-02-22 16:46:40 +1100	waiting_response	2013-02-22 17:06:14 +1100	waiting_response	incoming
547	comment	2013-02-24 10:30:59 +1100
587	followup_sent	2013-03-06 00:29:47 +1100				outgoing
614	response	2013-03-08 15:25:24 +1100	waiting_response	2013-03-08 16:38:46 +1100	waiting_response	incoming
619	followup_sent	2013-03-12 11:35:18 +1100				outgoing
620	response	2013-03-12 16:07:55 +1100	waiting_response	2013-03-12 16:08:56 +1100	waiting_response	incoming
621	followup_sent	2013-03-12 16:14:17 +1100	internal_review	2013-03-12 16:14:17 +1100	internal_review	outgoing
654	response	2013-03-22 15:26:08 +1100	internal_review	2013-03-22 16:28:47 +1100	internal_review	incoming
657	followup_sent	2013-03-22 16:31:42 +1100				outgoing
658	response	2013-03-22 16:35:40 +1100	internal_review	2013-03-24 11:39:13 +1100	internal_review	incoming
685	response	2013-03-26 14:36:38 +1100	internal_review	2013-03-26 14:51:24 +1100	internal_review	incoming
777	response	2013-04-15 17:24:55 +1000				incoming
781	response	2013-04-16 09:36:30 +1000		2013-04-16 16:09:49 +1000	partially_successful	incoming
784	comment	2013-04-16 15:39:34 +1000	partially_successful

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.