Details of request “Documents relating to breaches of the Public Service Act 1999

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
89752  sent  2022-04-04 21:57:48 +1000  waiting_response  2022-04-04 21:57:48 +1000  waiting_response  outgoing  
90401  response  2022-04-08 13:50:57 +1000    2022-04-12 22:33:22 +1000  waiting_response  incoming  
91107  status_update  2022-04-12 22:33:22 +1000  waiting_response  2022-04-12 22:33:22 +1000  waiting_response   
94036  response  2022-05-02 15:46:10 +1000    2022-05-08 18:46:13 +1000  rejected  incoming  
96429  overdue  2022-05-05 00:00:00 +1000         
94890  status_update  2022-05-08 18:46:13 +1000  rejected  2022-05-08 18:46:13 +1000  rejected   
94891  followup_sent  2022-05-08 18:52:17 +1000  internal_review  2022-05-08 18:52:17 +1000  internal_review  outgoing  
96113  response  2022-05-17 18:48:12 +1000    2022-05-19 20:14:30 +1000  waiting_response  incoming  
96319  status_update  2022-05-19 20:14:30 +1000  waiting_response  2022-05-19 20:14:30 +1000  waiting_response   
97167  response  2022-05-26 10:19:56 +1000    2022-06-08 15:04:40 +1000  rejected  incoming  
98424  status_update  2022-06-08 15:04:40 +1000  rejected  2022-06-08 15:04:40 +1000  rejected   
99012  followup_sent  2022-06-11 20:40:15 +1000        outgoing  
99013  response  2022-06-11 21:33:01 +1000    2022-06-11 21:42:44 +1000  rejected  incoming  
99015  status_update  2022-06-11 21:42:44 +1000  rejected  2022-06-11 21:42:44 +1000  rejected   
99261  response  2022-06-14 08:15:40 +1000    2022-06-14 10:27:30 +1000  rejected  incoming  
99265  status_update  2022-06-14 10:27:30 +1000  rejected  2022-06-14 10:27:30 +1000  rejected   
99266  followup_sent  2022-06-14 10:28:47 +1000        outgoing  
115176  response  2022-09-15 14:11:25 +1000        incoming  
115186  followup_sent  2022-09-15 14:52:58 +1000        outgoing  
115187  response  2022-09-15 14:53:20 +1000    2022-09-15 14:57:12 +1000  rejected  incoming  
115188  status_update  2022-09-15 14:57:12 +1000  rejected  2022-09-15 14:57:12 +1000  rejected   
122319  followup_sent  2022-10-26 17:57:46 +1100        outgoing  
127431  response  2022-11-24 15:06:50 +1100        incoming  
127432  response  2022-11-24 15:08:13 +1100        incoming  
127433  response  2022-11-24 15:12:21 +1100    2022-12-08 20:44:08 +1100  rejected  incoming  
130080  status_update  2022-12-08 20:44:08 +1100  rejected  2022-12-08 20:44:08 +1100  rejected   
130081  followup_sent  2022-12-08 20:45:38 +1100        outgoing  
130082  followup_sent  2022-12-08 20:46:46 +1100        outgoing  

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.