Details of request “Request for Delegation Schedules

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
6707  sent  2014-10-29 14:35:18 +1100  waiting_response  2014-10-29 14:35:18 +1100  waiting_response  outgoing  
6708  response  2014-10-29 14:35:42 +1100    2014-10-29 14:40:49 +1100  waiting_response  incoming  
6711  status_update  2014-10-29 14:40:48 +1100  waiting_response  2014-10-29 14:40:49 +1100  waiting_response   
6712  response  2014-10-29 14:58:44 +1100    2014-10-30 07:59:50 +1100  waiting_clarification  incoming  
6714  status_update  2014-10-30 07:59:49 +1100  waiting_clarification  2014-10-30 07:59:50 +1100  waiting_clarification   
6715  followup_sent  2014-10-30 08:02:00 +1100  waiting_response  2014-10-30 08:02:00 +1100  waiting_response  outgoing  
6716  response  2014-10-30 08:02:22 +1100        incoming  
6717  response  2014-10-30 08:22:06 +1100        incoming  
6739  response  2014-11-04 14:17:30 +1100    2014-11-05 17:47:48 +1100  waiting_clarification  incoming  
6742  status_update  2014-11-05 17:47:47 +1100  waiting_clarification  2014-11-05 17:47:48 +1100  waiting_clarification   
6743  followup_sent  2014-11-05 17:49:45 +1100  waiting_response  2014-11-05 17:49:46 +1100  waiting_response  outgoing  
6744  response  2014-11-05 17:50:07 +1100    2014-11-05 18:29:50 +1100  waiting_response  incoming  
6747  status_update  2014-11-05 18:29:50 +1100  waiting_response  2014-11-05 18:29:50 +1100  waiting_response   
6750  response  2014-11-06 09:09:27 +1100    2014-11-06 18:15:23 +1100  waiting_response  incoming  
6753  followup_sent  2014-11-06 18:15:17 +1100        outgoing  
6754  status_update  2014-11-06 18:15:23 +1100  waiting_response  2014-11-06 18:15:23 +1100  waiting_response   
6755  response  2014-11-06 18:15:38 +1100    2014-11-10 17:18:41 +1100  waiting_response  incoming  
6770  status_update  2014-11-10 17:18:41 +1100  waiting_response  2014-11-10 17:18:41 +1100  waiting_response   
6832  response  2014-11-18 09:09:45 +1100    2014-11-18 18:19:39 +1100  waiting_response  incoming  
6834  status_update  2014-11-18 18:19:38 +1100  waiting_response  2014-11-18 18:19:39 +1100  waiting_response   
6923  response  2014-11-28 08:34:00 +1100    2014-12-02 22:57:47 +1100  not_held  incoming  
6938  status_update  2014-12-02 22:57:47 +1100  not_held  2014-12-02 22:57:47 +1100  not_held   
6939  followup_sent  2014-12-02 22:59:29 +1100        outgoing  
6941  response  2014-12-02 22:59:56 +1100    2014-12-08 21:25:16 +1100  rejected  incoming  
6946  status_update  2014-12-04 12:30:42 +1100  waiting_response  2014-12-04 12:30:43 +1100  waiting_response   
52991  overdue  2014-12-06 00:00:00 +1100         
6985  status_update  2014-12-08 21:25:16 +1100  rejected  2014-12-08 21:25:16 +1100  rejected   

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.