Details of request “Funds received from RFSA

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
216781  sent  2023-12-18 14:39:07 +1100  waiting_response  2023-12-18 14:39:07 +1100  waiting_response  outgoing  
219887  response  2024-01-02 13:42:18 +1100    2024-01-02 14:34:49 +1100  rejected  incoming  
219892  status_update  2024-01-02 14:34:49 +1100  rejected  2024-01-02 14:34:49 +1100  rejected   
220319  followup_sent  2024-01-04 08:28:52 +1100        outgoing  
220334  response  2024-01-04 13:58:31 +1100    2024-01-04 14:12:36 +1100  waiting_response  incoming  
220335  status_update  2024-01-04 14:12:36 +1100  waiting_response  2024-01-04 14:12:36 +1100  waiting_response   
220336  followup_sent  2024-01-04 14:34:20 +1100        outgoing  
224323  overdue  2024-01-16 00:00:00 +1100         
224919  overdue  2024-01-16 00:00:00 +1100         
225139  overdue  2024-01-16 00:00:00 +1100         
225261  overdue  2024-01-16 00:00:00 +1100         
225632  overdue  2024-01-16 00:00:00 +1100         
225762  overdue  2024-01-16 00:00:00 +1100         
225971  overdue  2024-01-16 00:00:00 +1100         
226128  overdue  2024-01-16 00:00:00 +1100         
226289  overdue  2024-01-16 00:00:00 +1100         
226421  overdue  2024-01-16 00:00:00 +1100         
226571  overdue  2024-01-16 00:00:00 +1100         
226671  overdue  2024-01-16 00:00:00 +1100         
226793  overdue  2024-01-16 00:00:00 +1100         
226987  overdue  2024-01-16 00:00:00 +1100         
227339  overdue  2024-01-16 00:00:00 +1100         
227528  overdue  2024-01-16 00:00:00 +1100         
227794  overdue  2024-01-16 00:00:00 +1100         
228029  overdue  2024-01-16 00:00:00 +1100         
228187  overdue  2024-01-16 00:00:00 +1100         
228330  overdue  2024-01-16 00:00:00 +1100         
228572  overdue  2024-01-16 00:00:00 +1100         
228726  overdue  2024-01-16 00:00:00 +1100         
228890  overdue  2024-01-16 00:00:00 +1100         
229319  overdue  2024-01-16 00:00:00 +1100         
229460  overdue  2024-01-16 00:00:00 +1100         
229561  overdue  2024-01-16 00:00:00 +1100         
229861  overdue  2024-01-16 00:00:00 +1100         
230446  overdue  2024-01-16 00:00:00 +1100         
230614  overdue  2024-01-16 00:00:00 +1100         
230780  overdue  2024-01-16 00:00:00 +1100         
231001  overdue  2024-01-16 00:00:00 +1100         
223071  followup_sent  2024-01-16 08:29:54 +1100        outgoing  
231004  very_overdue  2024-02-17 00:00:00 +1100         
231005  followup_sent  2024-02-17 11:34:03 +1100  internal_review  2024-02-17 11:34:03 +1100  internal_review  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.