Details of request “Evidence of Criminal Conduct by Nicole Smith Chairman of NULIS

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
34856  sent  2018-09-08 07:31:11 +1000  waiting_response  2018-09-08 07:31:11 +1000  waiting_response  outgoing  
35357  response  2018-10-01 14:47:30 +1000    2018-10-30 10:54:42 +1100  waiting_clarification  incoming  
35364  followup_sent  2018-10-02 06:39:24 +1000        outgoing  
35509  status_update  2018-10-06 06:30:25 +1000  waiting_clarification  2018-10-06 06:30:25 +1000  waiting_clarification   
35529  response  2018-10-08 13:52:45 +1100    2018-10-30 10:54:42 +1100  waiting_response  incoming  
35541  redeliver_incoming  2018-10-08 16:28:25 +1100         
54403  overdue  2018-10-09 00:00:00 +1100         
36055  status_update  2018-10-30 10:54:42 +1100  waiting_response  2018-10-30 10:54:42 +1100  waiting_response   
36222  response  2018-11-07 16:54:58 +1100        incoming  
37021  followup_sent  2018-11-26 17:18:37 +1100        outgoing  
37168  response  2018-11-30 13:18:20 +1100    2018-12-05 07:18:17 +1100  waiting_clarification  incoming  
37255  status_update  2018-12-05 07:18:17 +1100  waiting_clarification  2018-12-05 07:18:17 +1100  waiting_clarification   
37306  response  2018-12-07 09:41:03 +1100    2018-12-16 11:30:57 +1100  rejected  incoming  
37494  status_update  2018-12-16 11:30:57 +1100  rejected  2018-12-16 11:30:57 +1100  rejected   
41276  followup_sent  2019-08-17 13:03:45 +1000        outgoing  
41284  response  2019-08-19 09:30:22 +1000    2019-08-30 08:32:54 +1000  waiting_response  incoming  
41286  followup_sent  2019-08-19 10:23:54 +1000        outgoing  
41336  followup_sent  2019-08-22 15:11:46 +1000        outgoing  
41460  status_update  2019-08-30 08:32:54 +1000  waiting_response  2019-08-30 08:32:54 +1000  waiting_response   
41467  response  2019-08-30 13:50:29 +1000    2019-08-31 07:28:34 +1000  successful  incoming  
41493  status_update  2019-08-31 07:28:34 +1000  successful  2019-08-31 07:28:34 +1000  successful   
41816  response  2019-09-23 17:19:01 +1000        incoming  
41817  response  2019-09-23 17:19:18 +1000    2019-10-10 18:51:45 +1100  successful  incoming  
42091  status_update  2019-10-10 18:51:45 +1100  successful  2019-10-10 18:51:45 +1100  successful   
42682  response  2019-10-31 12:56:21 +1100        incoming  
42683  response  2019-10-31 12:59:29 +1100    2019-11-03 15:42:16 +1100  successful  incoming  
42756  status_update  2019-11-03 15:42:16 +1100  successful  2019-11-03 15:42:16 +1100  successful   

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.