LCCMR updates Emerging Issues rules, recommends statutory edits on land acquisition and conflict-of-interest rules
Get AI-powered insights, summaries, and transcripts
SubscribeSummary
After staff briefings and DNR testimony, the commission adopted updated Emerging Issues procedures (Option A), recommended repeal or revision of duplicative DNR acquisition-review language to the legislature, and voted to recommend clarified conflict-of-interest statutory language.
The Legislative Citizen Commission on Minnesota Resources adopted multiple procedural and statutory recommendations at its Dec. 5 meeting.
Members voted to adopt staff’s updated Emerging Issues procedures, clarifying eligibility criteria and timing so the Emerging Issues account is explicitly aligned with the LCCMR funding cycle. The change (Option A) passed unanimously on a roll-call vote and the full updated procedure language was adopted after discussion and an additional roll‑call vote.
The commission also heard DNR Assistant Commissioner Bob Meyer, who described the department’s SLAM (Strategic Land Asset Management) goals and recommended narrowing or repealing a statutory provision that requires DNR approval of ENRTF-funded acquisitions in ways that the agency now considers duplicative. Commissioner Reese moved that the LCCMR recommend the legislature adopt Option 2 (repeal/modify the provision); that recommendation passed 16–1.
Separately, the commission endorsed a recommendation to the legislature revising LCCMR conflict‑of‑interest statute language. The proposed change narrows the prohibited conduct to cases in which a member serves as a project manager or receives compensation from an ENRTF proposal, rather than broad package‑based voting thresholds. The motion to recommend the statutory amendment passed by roll call (14 yes, 3 no).
Staff will draft and transmit recommended statutory language to legislative counsel and will post the adopted Emerging Issues procedures and the updated 2026 calendar (with the Emerging Issues due date aligned to the RFP) on the meeting page.
