Lifetime Citizen Portal Access — AI Briefings, Alerts & Unlimited Follows
Committee approves School Land Trust rule updates, staff defends website transfer and cost
Loading...
Summary
The Financial Operations Committee approved on first reading a major set of clarifying amendments to the School Land Trust rule (R277‑477) and heard a staff briefing on the history, costs and outstanding work on the School Land Trust website.
The Financial Operations Committee approved draft 1 of amendments to R277‑477 (distribution of funds from the trust distribution account and administration of the School Land Trust program) and forwarded the rule to the full board for final reading.
The proposed revisions, developed over a year by the Trust Lands advisory committee and stakeholder subcommittees, emphasize clarity and updated terminology. Changes include new definitions ("academic," "district liaison," "private school entity," and USIMS-related terms), reorganized plan‑review steps that align rule language with practice, updates that allow a carryover limit of 10% or $5,000 (whichever is greater), and an increase in the modest incentive from $2 to $4 per student (with an allowance to exceed $4 for academic incentives tied to instructional goals).
Director Paula Plant told the committee the work followed a yearlong advisory‑committee process and multiple stakeholder subgroups. She said the committee’s focus this first year was clarification; simplification is a planned next step and will include a review of where code versus rule requires specific items to be posted publicly. "All of these changes went through the Trust Lands advisory committee," Plant said. "They voted on them. They're not mine; they're not my team's."
Website history and costs: staff and IT director Jared Felt reviewed why the School Land Trust website was outsourced initially, the difficulties the agency faced when contracts ended or underbid vendors could not supply the source code, and the decision to host and develop the application in‑house. The agency provided an estimate of initial acquisition and ongoing sustainment costs and described development challenges (missing vendor source code, developer turnover and onboarding, quality assurance needs). Staff noted that several features remain to be restored or improved but that bringing the application in‑house has yielded new integrations with the state financial system and reduced some manual work.
Vote and next steps: The committee approved R277‑477 draft 1 on first reading and will forward it to the board for final action. Staff said they will continue to pursue simplification and to map which posting or documentation requirements are statutory and which can be changed in rule; they will also continue development to restore missing website features in priority order informed by LEA feedback.
