097”

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
352040	sent	2025-02-20 21:38:40 +1100	waiting_response	2025-02-20 21:38:40 +1100	waiting_response	outgoing
352041	response	2025-02-20 21:38:53 +1100		2025-02-20 21:40:06 +1100	waiting_response	incoming
352043	status_update	2025-02-20 21:40:06 +1100	waiting_response	2025-02-20 21:40:06 +1100	waiting_response
352313	response	2025-02-21 13:12:56 +1100		2025-02-25 07:38:33 +1100	waiting_response	incoming
353397	status_update	2025-02-25 07:38:33 +1100	waiting_response	2025-02-25 07:38:33 +1100	waiting_response
353653	response	2025-02-26 09:36:10 +1100		2025-03-07 12:49:29 +1100	waiting_response	incoming
357332	status_update	2025-03-07 12:49:29 +1100	waiting_response	2025-03-07 12:49:29 +1100	waiting_response
363109	overdue	2025-03-25 00:00:00 +1100
363362	status_update	2025-03-26 09:09:18 +1100	waiting_response	2025-03-26 09:09:18 +1100	waiting_response
369885	response	2025-04-07 14:35:13 +1000		2025-04-07 14:40:10 +1000	waiting_response	incoming
369886	followup_sent	2025-04-07 14:40:05 +1000				outgoing
369887	status_update	2025-04-07 14:40:10 +1000	waiting_response	2025-04-07 14:40:10 +1000	waiting_response
369888	response	2025-04-07 14:40:31 +1000				incoming
370401	response	2025-04-09 10:33:11 +1000		2025-05-05 09:30:17 +1000	waiting_response	incoming
378748	very_overdue	2025-04-24 00:00:00 +1000
378370	status_update	2025-05-05 09:30:17 +1000	waiting_response	2025-05-05 09:30:17 +1000	waiting_response
379036	response	2025-05-07 18:13:46 +1000		2025-05-07 19:18:18 +1000	waiting_response	incoming
379037	followup_sent	2025-05-07 19:18:15 +1000				outgoing
379038	status_update	2025-05-07 19:18:18 +1000	waiting_response	2025-05-07 19:18:18 +1000	waiting_response
379039	response	2025-05-07 19:19:29 +1000				incoming
379771	response	2025-05-09 14:08:23 +1000				incoming
379772	response	2025-05-09 14:09:25 +1000				incoming
379773	response	2025-05-09 14:10:25 +1000		2025-05-09 20:44:35 +1000	successful	incoming
379798	status_update	2025-05-09 20:44:35 +1000	successful	2025-05-09 20:44:35 +1000	successful
380514	followup_sent	2025-05-12 11:42:41 +1000				outgoing
380515	response	2025-05-12 11:43:07 +1000				incoming
380519	response	2025-05-12 12:16:06 +1000				incoming
380520	followup_sent	2025-05-12 12:19:41 +1000				outgoing
380521	response	2025-05-12 12:20:14 +1000				incoming
380529	response	2025-05-12 13:56:12 +1000		2025-05-16 10:19:16 +1000	successful	incoming
382696	status_update	2025-05-16 10:19:16 +1000	successful	2025-05-16 10:19:16 +1000	successful
384169	response	2025-05-22 10:00:54 +1000		2025-05-22 10:08:36 +1000	successful	incoming
384170	followup_sent	2025-05-22 10:08:28 +1000				outgoing
384171	status_update	2025-05-22 10:08:36 +1000	successful	2025-05-22 10:08:36 +1000	successful
384201	response	2025-05-22 14:20:07 +1000				incoming
384202	response	2025-05-22 14:26:18 +1000				incoming

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.