Details of request “Individualised assessments conducted at sea

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
46835  sent  2020-06-04 13:19:51 +1000  waiting_response  2020-06-04 13:19:51 +1000  waiting_response  outgoing  
46836  response  2020-06-04 13:21:13 +1000        incoming  
46845  response  2020-06-05 10:26:54 +1000    2020-06-09 10:32:23 +1000  waiting_response  incoming  
46871  status_update  2020-06-09 10:32:23 +1000  waiting_response  2020-06-09 10:32:23 +1000  waiting_response   
47219  response  2020-06-25 13:14:06 +1000    2020-06-25 13:25:17 +1000  waiting_clarification  incoming  
47220  status_update  2020-06-25 13:25:17 +1000  waiting_clarification  2020-06-25 13:25:17 +1000  waiting_clarification   
47221  followup_sent  2020-06-25 13:38:13 +1000  waiting_response  2020-06-25 13:38:13 +1000  waiting_response  outgoing  
47229  response  2020-06-26 11:38:40 +1000    2020-07-05 10:17:46 +1000  waiting_response  incoming  
47384  status_update  2020-07-05 10:17:45 +1000  waiting_response  2020-07-05 10:17:46 +1000  waiting_response   
47385  followup_sent  2020-07-05 10:18:28 +1000        outgoing  
48130  response  2020-07-21 09:31:54 +1000    2020-07-25 08:55:10 +1000  waiting_response  incoming  
48301  status_update  2020-07-25 08:55:10 +1000  waiting_response  2020-07-25 08:55:10 +1000  waiting_response   
54933  overdue  2020-07-28 00:00:00 +1000         
48612  response  2020-08-05 18:02:43 +1000    2020-08-21 11:45:58 +1000  successful  incoming  
48992  status_update  2020-08-21 11:45:58 +1000  successful  2020-08-21 11:45:58 +1000  successful   
49669  response  2020-09-10 09:45:05 +1000    2020-09-21 15:20:35 +1000  partially_successful  incoming  
49959  status_update  2020-09-21 15:20:34 +1000  partially_successful  2020-09-21 15:20:34 +1000  partially_successful   
59514  edit  2021-03-22 03:45:10 +1100         
59515  edit  2021-03-22 03:45:10 +1100         
59516  edit  2021-03-22 03:45:10 +1100         
59517  edit  2021-03-22 03:45:10 +1100         
59518  edit  2021-03-22 03:45:10 +1100         
59519  edit  2021-03-22 03:45:11 +1100         
59520  edit  2021-03-22 03:45:11 +1100         
59521  edit  2021-03-22 03:45:11 +1100         
59522  edit  2021-03-22 03:45:11 +1100         
59523  edit  2021-03-22 03:45:11 +1100         
59524  edit  2021-03-22 03:45:11 +1100         
59525  edit  2021-03-22 03:45:11 +1100         
59526  edit  2021-03-22 03:45:11 +1100         
59527  edit  2021-03-22 03:45:11 +1100         
59528  edit  2021-03-22 03:45:11 +1100         
59529  edit  2021-03-22 03:45:11 +1100         
59530  edit  2021-03-22 03:45:11 +1100         

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.