Details of request “Guidelines for Communicating with Clients

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
42096  sent  2019-10-11 08:38:24 +1100  waiting_response  2019-10-11 08:38:24 +1100  waiting_response  outgoing  
42097  response  2019-10-11 08:38:43 +1100    2019-10-14 12:36:51 +1100  waiting_response  incoming  
42134  status_update  2019-10-14 12:36:51 +1100  waiting_response  2019-10-14 12:36:51 +1100  waiting_response   
42414  response  2019-10-23 14:26:05 +1100        incoming  
42439  followup_sent  2019-10-24 09:12:00 +1100        outgoing  
42440  response  2019-10-24 09:12:19 +1100    2019-10-25 11:48:35 +1100  waiting_clarification  incoming  
42488  status_update  2019-10-25 11:48:35 +1100  waiting_clarification  2019-10-25 11:48:35 +1100  waiting_clarification   
42505  response  2019-10-25 16:00:25 +1100        incoming  
42506  followup_sent  2019-10-25 16:12:57 +1100  waiting_response  2019-10-25 16:12:57 +1100  waiting_response  outgoing  
42507  response  2019-10-25 16:13:34 +1100    2019-10-27 09:33:32 +1100  waiting_clarification  incoming  
42553  status_update  2019-10-27 09:33:32 +1100  waiting_clarification  2019-10-27 09:33:32 +1100  waiting_clarification   
42952  response  2019-11-11 13:52:20 +1100        incoming  
43095  response  2019-11-14 17:20:55 +1100        incoming  
43186  response  2019-11-18 19:42:07 +1100    2020-06-27 16:09:50 +1000  rejected  incoming  
47249  status_update  2020-06-27 16:09:50 +1000  rejected  2020-06-27 16:09:50 +1000  rejected   
100873  edit  2022-06-28 03:45:16 +1000         
100874  edit  2022-06-28 03:45:16 +1000         
100875  edit  2022-06-28 03:45:16 +1000         
100876  edit  2022-06-28 03:45:16 +1000         
100877  edit  2022-06-28 03:45:16 +1000         
100878  edit  2022-06-28 03:45:16 +1000         
100879  edit  2022-06-28 03:45:16 +1000         
100880  edit  2022-06-28 03:45:16 +1000         
100881  edit  2022-06-28 03:45:16 +1000         
100882  edit  2022-06-28 03:45:17 +1000         
100883  edit  2022-06-28 03:45:17 +1000         
100884  edit  2022-06-28 03:45:17 +1000         
100885  edit  2022-06-28 03:45:17 +1000         
100886  edit  2022-06-28 03:45:17 +1000         
100887  edit  2022-06-28 03:45:17 +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.