Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Calis Modernization topic
No spam. Unsubscribe anytime.
Legislative bill-drafting system deployment delayed; steering committee sets new timeline
Summary
Legislative IT and the reviser’s office told the Legislative Coordinating Council that the CALIS bill-drafting system did not go into production on June 30 because required functionality remained incomplete; a session-ready system is targeted for Oct. 1 with monthly reports to the council.
Legislative IT and the Reviser of Statutes told the Legislative Coordinating Council on July 1 that the planned June 30 production deployment of the CALIS bill-drafting system did not occur because required features and bug fixes were not complete.
Tom, legislative IT staff, briefed the council that “the production deployment of the CALIS bill drafting system, did not occur on 06/30/2025 as planned since there's some required functionality not yet ready.” He said required functionality includes conference committee reports, appropriations handling and additional table functionality, and that “a session ready system will be deployed before 10/01/2025.”
Gordon Self, Revisor of Statutes, told the council staff and members that extensive testing by the reviser’s office, Tom’s IT staff and chamber staff revealed missing functionality and remaining errors. “I won't take a system, you know, into usage that isn't ready. I won't do that,” Self said, adding that accuracy is his primary concern even as the steering committee works to accelerate delivery.
Senator Blasey pressed for confidence in the October 1 target and asked whether Propellon, the vendor, was present. Self and Tom said they remain confident a session-ready system will be available by Oct. 1 while acknowledging ongoing bug discovery as testing moves into production-like environments. Senator Sykes asked for more frequent updates; Self said the steering committee will provide a firm timetable and monthly reports to the LCC.
Council members discussed testing depth, including whether the system has been stress-tested with large numbers of floor amendments. Self said the reviser’s office and vendor testing has been rigorous but acknowledged they “haven't progressed” to scenario testing that simulates 60-plus simultaneous floor amendments.
The steering committee told the council it will develop a firm deadline with the vendor and provide monthly status reports; no formal action was taken by the council on the CALIS item during the meeting.
The council will revisit the deployment schedule and alternatives if the vendor fails to deliver required functionality in a timely fashion.
