Details of request “‘Personal and Environmental Circumstances Case’ questions and related Knowledge Articles.

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
281299  sent  2024-07-31 02:05:39 +1000  waiting_response  2024-07-31 02:05:39 +1000  waiting_response  outgoing  
281300  response  2024-07-31 02:06:02 +1000    2024-07-31 02:27:56 +1000  waiting_response  incoming  
281301  status_update  2024-07-31 02:27:56 +1000  waiting_response  2024-07-31 02:27:56 +1000  waiting_response   
290545  followup_sent  2024-08-23 17:50:05 +1000        outgoing  
291089  response  2024-08-26 15:10:22 +1000    2024-08-26 15:43:51 +1000  waiting_response  incoming  
291091  followup_sent  2024-08-26 15:43:48 +1000        outgoing  
291092  status_update  2024-08-26 15:43:51 +1000  waiting_response  2024-08-26 15:43:51 +1000  waiting_response   
291093  response  2024-08-26 15:58:59 +1000    2024-08-26 16:13:52 +1000  waiting_response  incoming  
291094  status_update  2024-08-26 16:13:52 +1000  waiting_response  2024-08-26 16:13:52 +1000  waiting_response   
291095  followup_sent  2024-08-26 16:35:42 +1000        outgoing  
292142  overdue  2024-08-31 00:00:00 +1000         
299132  followup_sent  2024-09-26 14:49:17 +1000        outgoing  
300802  followup_sent  2024-09-30 00:15:14 +1000        outgoing  
301272  very_overdue  2024-10-01 00:00:00 +1000         
301353  followup_sent  2024-10-01 23:33:26 +1000        outgoing  
302158  followup_sent  2024-10-04 14:36:16 +1000        outgoing  
302165  response  2024-10-04 15:11:12 +1000    2024-10-04 15:12:22 +1000  waiting_response  incoming  
302167  status_update  2024-10-04 15:12:22 +1000  waiting_response  2024-10-04 15:12:22 +1000  waiting_response   
302168  followup_sent  2024-10-04 15:14:03 +1000        outgoing  
303741  followup_sent  2024-10-12 00:02:29 +1100        outgoing  
307170  followup_sent  2024-10-21 20:05:45 +1100        outgoing  
308018  response  2024-10-25 10:20:21 +1100    2024-10-25 21:34:22 +1100  waiting_response  incoming  
308048  status_update  2024-10-25 21:34:22 +1100  waiting_response  2024-10-25 21:34:22 +1100  waiting_response   
308320  followup_sent  2024-10-26 20:08:32 +1100        outgoing  
309263  followup_sent  2024-10-29 13:26:25 +1100        outgoing  
311864  followup_sent  2024-11-09 02:44:49 +1100        outgoing  
314479  response  2024-11-18 10:54:01 +1100    2024-11-18 13:30:10 +1100  successful  incoming  
314484  status_update  2024-11-18 13:30:10 +1100  successful  2024-11-18 13:30:10 +1100  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.