2020 for the subclass 189 and 491 family stream”

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
44399	sent	2020-01-14 14:49:03 +1100	waiting_response	2020-01-14 14:49:03 +1100	waiting_response	outgoing
44446	response	2020-01-17 07:51:15 +1100		2020-01-21 07:05:23 +1100	waiting_response	incoming
44511	status_update	2020-01-21 07:05:23 +1100	waiting_response	2020-01-21 07:05:23 +1100	waiting_response
44978	response	2020-02-12 16:42:49 +1100		2020-02-12 22:37:53 +1100	waiting_response	incoming
44980	followup_sent	2020-02-12 22:37:19 +1100				outgoing
44981	status_update	2020-02-12 22:37:53 +1100	waiting_response	2020-02-12 22:37:53 +1100	waiting_response
54802	overdue	2020-02-14 00:00:00 +1100
45028	response	2020-02-14 17:28:02 +1100		2020-02-15 23:39:58 +1100	waiting_response	incoming
45041	followup_sent	2020-02-15 23:39:49 +1100				outgoing
45042	status_update	2020-02-15 23:39:58 +1100	waiting_response	2020-02-15 23:39:58 +1100	waiting_response
45146	comment	2020-02-20 13:12:29 +1100
45301	comment	2020-02-28 18:18:07 +1100
45404	comment	2020-03-04 20:50:31 +1100
56444	very_overdue	2020-03-17 00:00:00 +1100
45788	comment	2020-03-24 13:56:13 +1100
45789	status_update	2020-03-24 14:18:05 +1100	waiting_response	2020-03-24 14:18:05 +1100	waiting_response
45790	followup_sent	2020-03-24 14:27:24 +1100	internal_review	2020-03-24 14:27:24 +1100	internal_review	outgoing
45803	response	2020-03-24 17:51:41 +1100				incoming
46067	response	2020-04-08 18:39:35 +1000				incoming
46068	response	2020-04-08 18:39:35 +1000		2020-07-17 12:36:30 +1000	partially_successful	incoming
48060	status_update	2020-07-17 12:36:30 +1000	partially_successful	2020-07-17 12:36:30 +1000	partially_successful
105093	edit	2022-07-18 03:45:33 +1000
105094	edit	2022-07-18 03:45:33 +1000
105095	edit	2022-07-18 03:45:33 +1000
105096	edit	2022-07-18 03:45:33 +1000
105097	edit	2022-07-18 03:45:33 +1000
105098	edit	2022-07-18 03:45:33 +1000
105099	edit	2022-07-18 03:45:33 +1000
105100	edit	2022-07-18 03:45:33 +1000
105101	edit	2022-07-18 03:45:33 +1000
105102	edit	2022-07-18 03:45:33 +1000
105103	edit	2022-07-18 03:45:33 +1000
105104	edit	2022-07-18 03:45:33 +1000
105105	edit	2022-07-18 03:45:33 +1000
105106	edit	2022-07-18 03:45:33 +1000
105107	edit	2022-07-18 03:45:34 +1000
105108	edit	2022-07-18 03:45:34 +1000
105109	edit	2022-07-18 03:45:34 +1000
105110	edit	2022-07-18 03:45:34 +1000
105111	edit	2022-07-18 03:45:34 +1000
105112	edit	2022-07-18 03:45:34 +1000
105113	edit	2022-07-18 03:45:34 +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.