Details of request “Comcare PIN as reported by the Saturday paper

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
162344  sent  2023-06-03 08:11:22 +1000  waiting_response  2023-06-03 08:11:22 +1000  waiting_response  outgoing  
162345  response  2023-06-03 08:11:37 +1000    2023-06-03 14:28:45 +1000  waiting_response  incoming  
162348  status_update  2023-06-03 14:28:45 +1000  waiting_response  2023-06-03 14:28:45 +1000  waiting_response   
162623  response  2023-06-05 19:16:31 +1000    2023-06-05 21:02:16 +1000  waiting_clarification  incoming  
162624  followup_sent  2023-06-05 21:02:07 +1000        outgoing  
162625  status_update  2023-06-05 21:02:16 +1000  waiting_clarification  2023-06-05 21:02:16 +1000  waiting_clarification   
162626  response  2023-06-05 21:02:21 +1000    2023-06-05 21:03:28 +1000  waiting_response  incoming  
162627  status_update  2023-06-05 21:03:28 +1000  waiting_response  2023-06-05 21:03:28 +1000  waiting_response   
162975  response  2023-06-06 10:38:55 +1000    2023-06-06 13:42:15 +1000  waiting_response  incoming  
162981  status_update  2023-06-06 13:42:15 +1000  waiting_response  2023-06-06 13:42:15 +1000  waiting_response   
165282  response  2023-06-21 12:42:23 +1000    2023-06-21 13:09:03 +1000  waiting_response  incoming  
165285  followup_sent  2023-06-21 13:08:53 +1000        outgoing  
165286  status_update  2023-06-21 13:09:03 +1000  waiting_response  2023-06-21 13:09:03 +1000  waiting_response   
165287  response  2023-06-21 13:09:08 +1000    2023-06-21 13:12:43 +1000  waiting_response  incoming  
165288  status_update  2023-06-21 13:12:43 +1000  waiting_response  2023-06-21 13:12:43 +1000  waiting_response   
165620  response  2023-06-22 11:01:57 +1000    2023-06-22 13:29:27 +1000  waiting_response  incoming  
165625  followup_sent  2023-06-22 13:29:17 +1000        outgoing  
165626  status_update  2023-06-22 13:29:27 +1000  waiting_response  2023-06-22 13:29:27 +1000  waiting_response   
165627  response  2023-06-22 13:29:30 +1000    2023-06-22 13:43:00 +1000  waiting_response  incoming  
165629  status_update  2023-06-22 13:43:00 +1000  waiting_response  2023-06-22 13:43:00 +1000  waiting_response   
166747  response  2023-06-30 14:21:18 +1000    2023-06-30 14:52:10 +1000  waiting_response  incoming  
166748  followup_sent  2023-06-30 14:51:59 +1000        outgoing  
166749  status_update  2023-06-30 14:52:10 +1000  waiting_response  2023-06-30 14:52:10 +1000  waiting_response   
166750  response  2023-06-30 14:52:12 +1000    2023-06-30 14:53:41 +1000  waiting_response  incoming  
166751  status_update  2023-06-30 14:53:41 +1000  waiting_response  2023-06-30 14:53:41 +1000  waiting_response   
166755  response  2023-06-30 16:20:07 +1000    2023-07-06 11:46:03 +1000  waiting_response  incoming  
167691  status_update  2023-07-06 11:46:03 +1000  waiting_response  2023-07-06 11:46:03 +1000  waiting_response   
171172  overdue  2023-07-22 00:00:00 +1000         
172956  comment  2023-08-01 10:27:34 +1000         
172957  report_comment  2023-08-01 10:28:56 +1000         
172961  hide_comment  2023-08-01 12:22:32 +1000         
173075  response  2023-08-02 17:19:32 +1000    2023-08-03 03:49:08 +1000  partially_successful  incoming  
173198  status_update  2023-08-03 03:49:08 +1000  partially_successful  2023-08-03 03:49:08 +1000  partially_successful   
227586  edit  2024-02-03 03:45:15 +1100         
227587  edit  2024-02-03 03:45:15 +1100         
227588  edit  2024-02-03 03:45:15 +1100         
227589  edit  2024-02-03 03:45:15 +1100         
227590  edit  2024-02-03 03:45:15 +1100         
227591  edit  2024-02-03 03:45:15 +1100         
227592  edit  2024-02-03 03:45:15 +1100         
227593  edit  2024-02-03 03:45:15 +1100         
227594  edit  2024-02-03 03:45:15 +1100         
227595  edit  2024-02-03 03:45:15 +1100         
227596  edit  2024-02-03 03:45:15 +1100         
227597  edit  2024-02-03 03:45:15 +1100         
227598  edit  2024-02-03 03:45:15 +1100         
227599  edit  2024-02-03 03:45:15 +1100         
227600  edit  2024-02-03 03:45:16 +1100         
227601  edit  2024-02-03 03:45:16 +1100         
227602  edit  2024-02-03 03:45:16 +1100         
227603  edit  2024-02-03 03:45:16 +1100         
227604  edit  2024-02-03 03:45:16 +1100         
227605  edit  2024-02-03 03:45:16 +1100         
227606  edit  2024-02-03 03:45:16 +1100         
227607  edit  2024-02-03 03:45:16 +1100         
227608  edit  2024-02-03 03:45:16 +1100         
227609  edit  2024-02-03 03:45:16 +1100         
227610  edit  2024-02-03 03:45:16 +1100         
227611  edit  2024-02-03 03:45:16 +1100         
227612  edit  2024-02-03 03:45:16 +1100         
227613  edit  2024-02-03 03:45:16 +1100         
227614  edit  2024-02-03 03:45:16 +1100         
227615  edit  2024-02-03 03:45:17 +1100         
227616  edit  2024-02-03 03:45:17 +1100         
227617  edit  2024-02-03 03:45:17 +1100         
227618  edit  2024-02-03 03:45:17 +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.