Details of request “Training documents provided by John Hempton

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
61583  sent  2021-05-02 12:25:47 +1000  waiting_response  2021-05-02 12:25:47 +1000  waiting_response  outgoing  
62366  response  2021-05-13 12:05:35 +1000    2021-06-02 12:57:39 +1000  waiting_response  incoming  
63467  overdue  2021-06-02 00:00:00 +1000         
63415  status_update  2021-06-02 12:57:38 +1000  waiting_response  2021-06-02 12:57:39 +1000  waiting_response   
65370  response  2021-07-01 17:15:20 +1000    2021-07-03 14:26:36 +1000  rejected  incoming  
65417  status_update  2021-07-03 14:26:36 +1000  rejected  2021-07-03 14:26:36 +1000  rejected   
65418  followup_sent  2021-07-03 14:30:39 +1000  internal_review  2021-07-03 14:30:39 +1000  internal_review  outgoing  
65752  response  2021-07-08 14:49:05 +1000    2021-07-17 15:10:19 +1000  rejected  incoming  
66393  status_update  2021-07-17 15:10:19 +1000  rejected  2021-07-17 15:10:19 +1000  rejected   
79178  edit  2022-01-18 03:45:16 +1100         
79179  edit  2022-01-18 03:45:16 +1100         
79180  edit  2022-01-18 03:45:16 +1100         
79181  edit  2022-01-18 03:45:16 +1100         
79182  edit  2022-01-18 03:45:16 +1100         
79183  edit  2022-01-18 03:45:16 +1100         
79184  edit  2022-01-18 03:45:16 +1100         
79185  edit  2022-01-18 03:45:16 +1100         
79186  edit  2022-01-18 03:45:16 +1100         
170290  edit  2023-07-18 03:45:28 +1000         
170291  edit  2023-07-18 03:45:28 +1000         
170292  edit  2023-07-18 03:45:28 +1000         
170293  edit  2023-07-18 03:45:28 +1000         
170294  edit  2023-07-18 03:45:28 +1000         
170295  edit  2023-07-18 03:45:28 +1000         
170296  edit  2023-07-18 03:45:28 +1000         
170297  edit  2023-07-18 03:45:28 +1000         
170298  edit  2023-07-18 03:45:28 +1000         
170299  edit  2023-07-18 03:45:28 +1000         
170300  edit  2023-07-18 03:45:28 +1000         
170301  edit  2023-07-18 03:45:28 +1000         
170302  edit  2023-07-18 03:45:28 +1000         
170303  edit  2023-07-18 03:45:28 +1000         
170304  edit  2023-07-18 03:45:28 +1000         
170305  edit  2023-07-18 03:45:28 +1000         
170306  edit  2023-07-18 03:45:28 +1000         
170307  edit  2023-07-18 03:45:28 +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.