Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Propelon System topic
No spam. Unsubscribe anytime.
Legislature’s Reviser office pauses Propelon rollout; steering committee weighing options as ARPA authority nears expiration
Summary
Office of the Reviser of Statutes staff told the budget committee that a steering committee had imposed stop-work orders on Propelon and recommended delaying go‑live; staff said the current appropriation of $2.6 million in ARPA funds to pay for the system will be harder to expend after an October expiration of expenditure authority.
Officials from the Office of the Reviser of Statutes told the Committee on Legislative Budget that the Propelon bill‑drafting system rollout has been paused after the LCC steering committee concluded the system was not ready for the 2026 session.
Gordon, representing the Reviser office, explained the steering committee recommended pausing work, negotiating with Propelon to meet a set of critical terms, and exploring other vendors. The committee directed staff in the fall to consider alternatives; staff later issued stop-work orders in November and December and then instructed Propelon to cease work in January while the steering committee developed recommendations.
Gordon said one short-term option is to give Propelon a narrow window (about four months) to produce an updated system for testing; if it met defined requirements, the Reviser would accept it for 2027. If not, the steering committee would come back to the LCC with alternate options. Gordon also said internal IT staff believe the current system of records could be maintained for two to three years while a replacement path is pursued.
Separately, budget staff reminded the committee that $2.6 million in ARPA funds had been appropriated to pay for the Propelon work and that authority to expend those funds expires in October. Staff noted there is limited ability for contractors to carry over work after that point and urged the committee and LCC to plan accordingly.
Committee members asked whether the system that Propelon might deliver after a short remediation period could be trusted; Gordon said he was not an IT specialist and would rely on the incoming CTO and IT staff to test and vet any product. He said the steering committee will brief the new CTO and return recommendations to the LCC.
