Details of request “General Ledger (Last 5 Financial Years)

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
63970  set_embargo  2021-06-11 13:43:11 +1000         
63971  sent  2021-06-11 13:43:11 +1000  waiting_response  2021-06-11 13:43:11 +1000  waiting_response  outgoing  
63972  response  2021-06-11 13:43:26 +1000    2021-06-11 17:26:01 +1000  waiting_response  incoming  
64078  status_update  2021-06-11 17:26:01 +1000  waiting_response  2021-06-11 17:26:01 +1000  waiting_response   
64892  response  2021-06-25 17:27:16 +1000    2021-07-04 18:49:39 +1000  waiting_response  incoming  
65471  status_update  2021-07-04 18:49:39 +1000  waiting_response  2021-07-04 18:49:39 +1000  waiting_response   
65514  expire_embargo  2021-07-04 18:54:39 +1000         
65593  response  2021-07-06 11:11:49 +1000    2021-07-06 12:25:33 +1000  successful  incoming  
65600  status_update  2021-07-06 12:25:32 +1000  successful  2021-07-06 12:25:33 +1000  successful   
65993  response  2021-07-12 11:20:27 +1000    2021-07-17 09:46:17 +1000  rejected  incoming  
66354  status_update  2021-07-17 09:46:17 +1000  rejected  2021-07-17 09:46:17 +1000  rejected   
78948  edit  2022-01-17 03:45:16 +1100         
78949  edit  2022-01-17 03:45:16 +1100         
78950  edit  2022-01-17 03:45:16 +1100         
78951  edit  2022-01-17 03:45:16 +1100         
78952  edit  2022-01-17 03:45:16 +1100         
78953  edit  2022-01-17 03:45:16 +1100         
78954  edit  2022-01-17 03:45:16 +1100         
78955  edit  2022-01-17 03:45:16 +1100         
78956  edit  2022-01-17 03:45:16 +1100         
78957  edit  2022-01-17 03:45:16 +1100         
78958  edit  2022-01-17 03:45:16 +1100         
169646  edit  2023-07-17 03:45:22 +1000         
169647  edit  2023-07-17 03:45:22 +1000         
169648  edit  2023-07-17 03:45:22 +1000         
169649  edit  2023-07-17 03:45:23 +1000         
169650  edit  2023-07-17 03:45:23 +1000         
169651  edit  2023-07-17 03:45:23 +1000         
169652  edit  2023-07-17 03:45:23 +1000         
169653  edit  2023-07-17 03:45:23 +1000         
169654  edit  2023-07-17 03:45:23 +1000         
169655  edit  2023-07-17 03:45:23 +1000         
169656  edit  2023-07-17 03:45:23 +1000         
169657  edit  2023-07-17 03:45:23 +1000         
169658  edit  2023-07-17 03:45:23 +1000         
169659  edit  2023-07-17 03:45:23 +1000         
169660  edit  2023-07-17 03:45:23 +1000         
169661  edit  2023-07-17 03:45:23 +1000         
169662  edit  2023-07-17 03:45:23 +1000         
169663  edit  2023-07-17 03:45:23 +1000         
169664  edit  2023-07-17 03:45:24 +1000         
169665  edit  2023-07-17 03:45:24 +1000         
169666  edit  2023-07-17 03:45:24 +1000         
169667  edit  2023-07-17 03:45:24 +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.