2019-07-302019-07-3031-MarOklahoma Department of Transportation State Planning and Research Item No. 2156https://hdl.handle.net/11244/321064Only the products listed on the Approved Herbicide and Adjuvant List (AHAL) are approved for the ODOT Statewide Herbicide Contract. Herbicide/adjuvant items on the AHAL meet the minimum criteria set by ODOT. Any product not on the AHAL is not eligible for inclusion as an herbicide contract bid item in any upcoming bidding process. Herbicide/adjuvant products must meet minimum criteria before they will be placed on the current AHAL. Failure to meet one or more of the criteria will result in non-approval. The AHAL is updated annually and any listed products that fail to maintain minimum approval criteria will be removed along with any other products ODOT decides to remove. Manufacturers and distributors are encouraged to resubmit non-approved products at a later date once minimum approval criteria is met. ODOT reserves the right of final herbicide inclusion or exclusion to provide for specific herbicide product exemptions in the case of but not limited to: herbicide manufacturer supply issues, herbicide manufacturer delivery issues, EPA label issues, ODAFF label issues, and Oklahoma legislative issues. Section 2 of this report very briefly summarizes the actions taken in 2013 to update the 2012 AHAL to create the 2013 AHAL that is shown in Table 1. Section 3.0 provides the criteria used to evaluate the suitability of herbicide products for entry onto the AHAL. Section 4.0 overviews the criteria used to evaluate the suitability of spray adjuvants for entry onto the AHAL. In Section 5.0 the information submission requirements for AHAL candidate herbicides and adjuvants are covered. The requirements of the research data package for candidate herbicides are covered in Section 6.0 while the details of herbicide-adjuvant compatibility data package are covered in Section 7.0. The specific protocol to be used in screening for herbicide-adjuvant tank mix compatibility (jar test) is discussed in Section 8.0.20 pages447,865 bytesapplication.pdfTechnical Report