Details of request “Adverse Experience Reporting 2,4-D and Metsulfuron Methyl

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
23568  sent  2017-03-10 18:46:06 +1100  waiting_response  2017-03-10 18:46:06 +1100  waiting_response  outgoing  
23695  response  2017-03-15 12:25:33 +1100    2017-03-15 12:46:43 +1100  waiting_clarification  incoming  
23697  status_update  2017-03-15 12:46:43 +1100  waiting_clarification  2017-03-15 12:46:43 +1100  waiting_clarification   
23699  followup_sent  2017-03-15 13:02:20 +1100  waiting_response  2017-03-15 13:02:20 +1100  waiting_response  outgoing  
23702  response  2017-03-15 13:34:24 +1100    2017-03-15 13:42:26 +1100  waiting_clarification  incoming  
23704  status_update  2017-03-15 13:42:26 +1100  waiting_clarification  2017-03-15 13:42:26 +1100  waiting_clarification   
23705  followup_sent  2017-03-15 13:55:08 +1100  waiting_response  2017-03-15 13:55:08 +1100  waiting_response  outgoing  
23973  response  2017-03-21 16:08:58 +1100    2017-03-30 12:21:30 +1100  waiting_clarification  incoming  
24353  status_update  2017-03-30 12:21:30 +1100  waiting_clarification  2017-03-30 12:21:30 +1100  waiting_clarification   
24357  followup_sent  2017-03-30 13:31:56 +1100  waiting_response  2017-03-30 13:31:56 +1100  waiting_response  outgoing  
24372  response  2017-03-30 15:25:26 +1100    2017-03-30 15:30:29 +1100  waiting_response  incoming  
24373  status_update  2017-03-30 15:30:29 +1100  waiting_response  2017-03-30 15:30:29 +1100  waiting_response   
24378  followup_sent  2017-03-30 16:09:55 +1100        outgoing  
24381  response  2017-03-30 16:45:25 +1100        incoming  
24383  response  2017-03-30 16:56:29 +1100    2017-03-30 18:10:24 +1100  waiting_response  incoming  
24385  status_update  2017-03-30 18:10:23 +1100  waiting_response  2017-03-30 18:10:24 +1100  waiting_response   
24386  followup_sent  2017-03-30 18:20:24 +1100        outgoing  
24414  response  2017-03-31 14:04:06 +1100    2017-03-31 14:35:28 +1100  waiting_clarification  incoming  
24417  status_update  2017-03-31 14:35:28 +1100  waiting_clarification  2017-03-31 14:35:28 +1100  waiting_clarification   
24418  followup_sent  2017-03-31 14:37:36 +1100  waiting_response  2017-03-31 14:37:36 +1100  waiting_response  outgoing  
24420  response  2017-03-31 15:03:47 +1100    2017-04-21 12:07:50 +1000  waiting_response  incoming  
25150  status_update  2017-04-21 12:07:50 +1000  waiting_response  2017-04-21 12:07:50 +1000  waiting_response   
25235  response  2017-04-24 17:11:25 +1000    2017-04-25 12:12:16 +1000  waiting_clarification  incoming  
25254  status_update  2017-04-25 12:12:16 +1000  waiting_clarification  2017-04-25 12:12:16 +1000  waiting_clarification   
25255  followup_sent  2017-04-25 12:42:10 +1000  waiting_response  2017-04-25 12:42:10 +1000  waiting_response  outgoing  
25815  response  2017-05-15 17:04:35 +1000    2017-05-18 13:51:03 +1000  waiting_response  incoming  
25946  status_update  2017-05-18 13:51:03 +1000  waiting_response  2017-05-18 13:51:03 +1000  waiting_response   
25947  followup_sent  2017-05-18 13:58:28 +1000  internal_review  2017-05-18 13:58:28 +1000  internal_review  outgoing  
26029  comment  2017-05-20 22:26:58 +1000         
26032  comment  2017-05-20 22:47:06 +1000         
26844  response  2017-06-19 16:25:05 +1000    2017-07-13 18:59:50 +1000  partially_successful  incoming  
27483  status_update  2017-07-13 18:59:49 +1000  partially_successful  2017-07-13 18:59:50 +1000  partially_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.