Details of request “Referrals to Coordinated Care and Client Liaison Units for FY15/16-FY17/18 by age group

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
34323  sent  2018-08-08 19:42:14 +1000  waiting_response  2018-08-08 19:42:14 +1000  waiting_response  outgoing  
34347  response  2018-08-09 14:39:30 +1000    2018-08-09 15:26:47 +1000  waiting_response  incoming  
34349  status_update  2018-08-09 15:26:47 +1000  waiting_response  2018-08-09 15:26:47 +1000  waiting_response   
34750  status_update  2018-09-03 18:38:21 +1000  waiting_response  2018-09-03 18:38:21 +1000  waiting_response   
34813  response  2018-09-06 16:08:31 +1000    2018-09-07 02:19:07 +1000  waiting_response  incoming  
34818  status_update  2018-09-07 02:19:07 +1000  waiting_response  2018-09-07 02:19:07 +1000  waiting_response   
34819  followup_sent  2018-09-07 02:36:16 +1000        outgoing  
34830  response  2018-09-07 13:19:05 +1000    2018-09-07 13:39:42 +1000  waiting_response  incoming  
34831  followup_sent  2018-09-07 13:39:37 +1000        outgoing  
34832  status_update  2018-09-07 13:39:41 +1000  waiting_response  2018-09-07 13:39:42 +1000  waiting_response   
54349  overdue  2018-09-08 00:00:00 +1000         
35084  response  2018-09-18 16:01:45 +1000    2018-09-18 16:03:46 +1000  waiting_response  incoming  
35086  status_update  2018-09-18 16:03:46 +1000  waiting_response  2018-09-18 16:03:46 +1000  waiting_response   
35087  followup_sent  2018-09-18 16:04:58 +1000        outgoing  
35111  response  2018-09-19 13:50:31 +1000    2018-09-19 13:52:50 +1000  partially_successful  incoming  
35112  followup_sent  2018-09-19 13:52:42 +1000        outgoing  
35113  status_update  2018-09-19 13:52:50 +1000  partially_successful  2018-09-19 13:52:50 +1000  partially_successful   
35115  response  2018-09-19 13:57:31 +1000    2018-09-19 13:59:43 +1000  partially_successful  incoming  
35116  status_update  2018-09-19 13:59:43 +1000  partially_successful  2018-09-19 13:59:43 +1000  partially_successful   
35324  response  2018-09-28 13:23:09 +1000    2018-10-25 18:46:37 +1100  partially_successful  incoming  
35949  status_update  2018-10-25 18:46:37 +1100  partially_successful  2018-10-25 18:46:37 +1100  partially_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.