Details of request “#2 Reason for amendments to s 67CC(2)

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
154212  sent  2023-04-17 22:15:51 +1000  waiting_response  2023-04-17 22:15:51 +1000  waiting_response  outgoing  
154213  response  2023-04-17 22:16:05 +1000    2023-04-17 22:19:48 +1000  waiting_response  incoming  
154214  status_update  2023-04-17 22:19:48 +1000  waiting_response  2023-04-17 22:19:48 +1000  waiting_response   
154215  followup_sent  2023-04-17 22:20:37 +1000        outgoing  
154603  response  2023-04-20 11:55:49 +1000    2023-04-20 14:43:02 +1000  waiting_clarification  incoming  
154613  status_update  2023-04-20 14:43:02 +1000  waiting_clarification  2023-04-20 14:43:02 +1000  waiting_clarification   
154614  followup_sent  2023-04-20 14:51:02 +1000  waiting_response  2023-04-20 14:51:02 +1000  waiting_response  outgoing  
154758  response  2023-04-21 09:13:52 +1000    2023-04-21 09:50:36 +1000  waiting_clarification  incoming  
154762  status_update  2023-04-21 09:50:36 +1000  waiting_clarification  2023-04-21 09:50:36 +1000  waiting_clarification   
154763  followup_sent  2023-04-21 09:52:27 +1000  waiting_response  2023-04-21 09:52:27 +1000  waiting_response  outgoing  
154778  response  2023-04-21 16:35:30 +1000    2023-04-21 17:02:31 +1000  waiting_response  incoming  
154779  status_update  2023-04-21 17:02:31 +1000  waiting_response  2023-04-21 17:02:31 +1000  waiting_response   
156127  response  2023-05-01 15:25:29 +1000    2023-05-01 23:25:26 +1000  waiting_clarification  incoming  
156144  status_update  2023-05-01 23:25:25 +1000  waiting_clarification  2023-05-01 23:25:25 +1000  waiting_clarification   
156145  followup_sent  2023-05-01 23:25:52 +1000  waiting_response  2023-05-01 23:25:52 +1000  waiting_response  outgoing  
156146  response  2023-05-01 23:26:09 +1000    2023-05-05 08:03:50 +1000  waiting_response  incoming  
156697  status_update  2023-05-05 08:03:50 +1000  waiting_response  2023-05-05 08:03:50 +1000  waiting_response   
160282  response  2023-05-23 15:21:00 +1000    2023-05-24 07:24:22 +1000  waiting_clarification  incoming  
160526  status_update  2023-05-24 07:24:21 +1000  waiting_clarification  2023-05-24 07:24:22 +1000  waiting_clarification   
160527  followup_sent  2023-05-24 07:25:10 +1000  waiting_response  2023-05-24 07:25:10 +1000  waiting_response  outgoing  
160528  response  2023-05-24 07:25:24 +1000    2023-05-24 07:26:50 +1000  waiting_response  incoming  
160529  status_update  2023-05-24 07:26:50 +1000  waiting_response  2023-05-24 07:26:50 +1000  waiting_response   
164195  response  2023-06-14 16:32:26 +1000    2023-06-25 07:26:12 +1000  waiting_clarification  incoming  
166128  status_update  2023-06-25 07:26:12 +1000  waiting_clarification  2023-06-25 07:26:12 +1000  waiting_clarification   
167886  followup_sent  2023-07-07 14:19:15 +1000  internal_review  2023-07-07 14:19:16 +1000  internal_review  outgoing  
167887  response  2023-07-07 14:19:32 +1000    2023-07-07 14:20:26 +1000  waiting_response  incoming  
167888  status_update  2023-07-07 14:20:26 +1000  waiting_response  2023-07-07 14:20:26 +1000  waiting_response   
168586  response  2023-07-12 16:42:25 +1000    2023-07-14 09:41:58 +1000  waiting_clarification  incoming  
169250  status_update  2023-07-14 09:41:58 +1000  waiting_clarification  2023-07-14 09:41:58 +1000  waiting_clarification   
169252  followup_sent  2023-07-14 09:43:07 +1000  waiting_response  2023-07-14 09:43:07 +1000  waiting_response  outgoing  
169266  response  2023-07-14 16:09:32 +1000    2023-07-14 17:23:57 +1000  waiting_response  incoming  
169268  status_update  2023-07-14 17:23:57 +1000  waiting_response  2023-07-14 17:23:57 +1000  waiting_response   
172211  response  2023-07-28 16:16:50 +1000    2023-08-01 07:35:21 +1000  waiting_response  incoming  
172950  status_update  2023-08-01 07:35:21 +1000  waiting_response  2023-08-01 07:35:21 +1000  waiting_response   
176122  overdue  2023-08-15 00:00:00 +1000         
179126  response  2023-08-21 18:17:25 +1000    2023-08-21 19:40:48 +1000  waiting_response  incoming  
179127  status_update  2023-08-21 19:40:48 +1000  waiting_response  2023-08-21 19:40:48 +1000  waiting_response   
185526  response  2023-09-04 16:34:10 +1000    2023-09-07 13:56:51 +1000  partially_successful  incoming  
187419  status_update  2023-09-07 13:56:51 +1000  partially_successful  2023-09-07 13:56:51 +1000  partially_successful   
189424  followup_sent  2023-09-11 13:43:48 +1000        outgoing  
189425  status_update  2023-09-11 13:44:11 +1000  partially_successful  2023-09-11 13:44:11 +1000  partially_successful   
238650  edit  2024-03-08 03:45:16 +1100         
238651  edit  2024-03-08 03:45:16 +1100         
238652  edit  2024-03-08 03:45:17 +1100         
238653  edit  2024-03-08 03:45:17 +1100         
238654  edit  2024-03-08 03:45:17 +1100         
238655  edit  2024-03-08 03:45:17 +1100         
238656  edit  2024-03-08 03:45:17 +1100         
238657  edit  2024-03-08 03:45:17 +1100         
238658  edit  2024-03-08 03:45:17 +1100         
238659  edit  2024-03-08 03:45:17 +1100         
238660  edit  2024-03-08 03:45:17 +1100         
238661  edit  2024-03-08 03:45:17 +1100         
238662  edit  2024-03-08 03:45:17 +1100         
238663  edit  2024-03-08 03:45:17 +1100         
238664  edit  2024-03-08 03:45:17 +1100         
238665  edit  2024-03-08 03:45:17 +1100         
238666  edit  2024-03-08 03:45:17 +1100         
238667  edit  2024-03-08 03:45:17 +1100         
238668  edit  2024-03-08 03:45:17 +1100         
238669  edit  2024-03-08 03:45:17 +1100         
238670  edit  2024-03-08 03:45:17 +1100         
238671  edit  2024-03-08 03:45:17 +1100         
238672  edit  2024-03-08 03:45:17 +1100         
238673  edit  2024-03-08 03:45:17 +1100         
238674  edit  2024-03-08 03:45:17 +1100         
238675  edit  2024-03-08 03:45:17 +1100         
238676  edit  2024-03-08 03:45:18 +1100         
238677  edit  2024-03-08 03:45:18 +1100         
238678  edit  2024-03-08 03:45:18 +1100         
238679  edit  2024-03-08 03:45:18 +1100         
238680  edit  2024-03-08 03:45:18 +1100         
238681  edit  2024-03-08 03:45:18 +1100         
238682  edit  2024-03-08 03:45:18 +1100         
238683  edit  2024-03-08 03:45:18 +1100         
238684  edit  2024-03-08 03:45:18 +1100         
238685  edit  2024-03-08 03:45:18 +1100         
238686  edit  2024-03-08 03:45:18 +1100         
238687  edit  2024-03-08 03:45:18 +1100         
238688  edit  2024-03-08 03:45:18 +1100         
238689  edit  2024-03-08 03:45:18 +1100         
238690  edit  2024-03-08 03:45:18 +1100         

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.