Details of request “Request for User Guide - Call Centre Supervisor/Reporting Application

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
21147  sent  2016-12-29 15:25:39 +1100  waiting_response  2016-12-29 15:25:39 +1100  waiting_response  outgoing  
21148  response  2016-12-29 15:26:07 +1100    2017-01-02 13:59:24 +1100  waiting_response  incoming  
21178  status_update  2017-01-02 13:59:24 +1100  waiting_response  2017-01-02 13:59:24 +1100  waiting_response   
21277  response  2017-01-05 17:07:45 +1100    2017-01-05 17:40:14 +1100  waiting_clarification  incoming  
21280  status_update  2017-01-05 17:40:14 +1100  waiting_clarification  2017-01-05 17:40:14 +1100  waiting_clarification   
21281  followup_sent  2017-01-05 17:41:03 +1100  waiting_response  2017-01-05 17:41:03 +1100  waiting_response  outgoing  
21867  response  2017-01-23 15:06:35 +1100        incoming  
21868  response  2017-01-23 15:10:35 +1100    2017-01-23 15:18:24 +1100  waiting_clarification  incoming  
21870  status_update  2017-01-23 15:18:24 +1100  waiting_clarification  2017-01-23 15:18:24 +1100  waiting_clarification   
21871  response  2017-01-23 15:20:27 +1100        incoming  
21872  followup_sent  2017-01-23 15:23:08 +1100  waiting_response  2017-01-23 15:23:08 +1100  waiting_response  outgoing  
21873  response  2017-01-23 15:23:37 +1100        incoming  
21900  response  2017-01-24 17:12:54 +1100    2017-01-24 17:27:30 +1100  waiting_clarification  incoming  
21901  status_update  2017-01-24 17:27:29 +1100  waiting_clarification  2017-01-24 17:27:30 +1100  waiting_clarification   
21902  followup_sent  2017-01-24 17:28:27 +1100  waiting_response  2017-01-24 17:28:27 +1100  waiting_response  outgoing  
21903  response  2017-01-24 17:28:54 +1100    2017-01-24 17:31:14 +1100  waiting_response  incoming  
21904  status_update  2017-01-24 17:31:14 +1100  waiting_response  2017-01-24 17:31:14 +1100  waiting_response   
22053  response  2017-01-30 17:08:59 +1100    2017-02-07 08:59:04 +1100  waiting_clarification  incoming  
22317  status_update  2017-02-07 08:59:03 +1100  waiting_clarification  2017-02-07 08:59:04 +1100  waiting_clarification   
22318  followup_sent  2017-02-07 09:06:06 +1100  waiting_response  2017-02-07 09:06:06 +1100  waiting_response  outgoing  
22319  response  2017-02-07 09:06:36 +1100    2017-02-11 13:09:43 +1100  waiting_response  incoming  
22514  status_update  2017-02-11 13:09:43 +1100  waiting_response  2017-02-11 13:09:43 +1100  waiting_response   
53786  overdue  2017-03-10 00:00:00 +1100         
23561  response  2017-03-10 15:00:37 +1100    2017-03-10 23:44:10 +1100  rejected  incoming  
23569  status_update  2017-03-10 23:44:10 +1100  rejected  2017-03-10 23:44:10 +1100  rejected   
23570  followup_sent  2017-03-10 23:46:39 +1100  internal_review  2017-03-10 23:46:39 +1100  internal_review  outgoing  
24766  response  2017-04-10 14:39:36 +1000    2017-05-01 19:06:05 +1000  rejected  incoming  
24787  comment  2017-04-10 18:51:00 +1000         
55865  very_overdue  2017-04-11 00:00:00 +1000         
25410  status_update  2017-05-01 19:06:05 +1000  rejected  2017-05-01 19:06:05 +1000  rejected   
27369  response  2017-07-08 02:05:39 +1000    2017-07-31 19:57:30 +1000  waiting_response  incoming  
27842  comment  2017-07-31 19:57:07 +1000         
27843  status_update  2017-07-31 19:57:30 +1000  waiting_response  2017-07-31 19:57:30 +1000  waiting_response   

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.