Information Technology Consolidation and Coordination Act; adding certain entities to definition of certain term. Emergency.
SB 68 amends Oklahoma's Information Technology Consolidation and Coordination Act to require state agencies to obtain a Memorandum of Understanding (MOU) with the Chief Information Officer (CIO) before hiring IT staff. The MOU must detail specific job roles, qualifications, and the agency's commitment to follow CIO-established security and data integrity standards. Agencies cannot hire IT personnel until the CIO and the agency fully execute the MOU, and the CIO may audit compliance with the agreement. This emergency law became effective immediately without the Governor's signature on May 26, 2025.
Bill status
signed
all 5 stages cleared
Introduction
Feb 2025
Committee Review
May 2025
Senate Passage
May 2025
House Passage
May 2025
Signed into Law
May 2025
Introduced Feb 3, 2025
Signed May 27, 2025
Maddy AI version diff · 8 comparisons
What changed between versions
Floor (House)
→
Floor (Senate)
·
3 edits
MINOR
The bill was transitioned from the House version to the Senate floor version, incorporating specific amendments to the definitions of IT assets and positions. The Senate version reorganized the list of IT job functions into a more concise format and added a formal emergency declaration to ensure immediate legal effect upon passage.
Scope change
The scope of the bill remains focused on the Information Technology Consolidation and Coordination Act, but the Senate amendments refine the specific definitions of IT assets and positions to better align with legislative intent.
DEFINITION
The list of functional areas for 'Information technology positions' was reorganized and condensed in the Senate version, removing some specific sub-categories present in the House draft while retaining the core job functions.
TIMELINE
A formal emergency clause was added to Section 2, declaring that the act is immediately necessary for public safety and will take effect upon passage.
TECHNICAL
The document structure was updated to reflect Senate floor amendments, including changes to page headers and the addition of a committee report indicating the bill should pass as amended.
Floor votes · Senate Mar 25, 2025 · House May 5, 2025
How they voted
48–0
Passed · 1 other
Total votes 49
Mar 25, 2025
D
Democratic9
100% Yea
R
Republican40
97% Yea
Vote distribution
All Yea
All Nay
Mixed
No data
Full legislative history
Actions timeline
Total actions
30
Key actions
9
Committee
7
Amendments
1
May 15, 2025
Committee
Referred for enrollment
upper
May 15, 2025
Upper · Passed
Measure and Emergency passed: Ayes: 37 Nays: 0
upper
May 15, 2025
Upper · Passed
HAs adopted
upper
May 6, 2025
Lower · Passed
Engrossed, signed, to Senate
lower
May 5, 2025
Committee
Referred for engrossment
lower
May 5, 2025
Lower · Passed
Third Reading, Measure and Emergency passed: Ayes: 87 Nays: 3
lower
Apr 21, 2025
Lower · Passed
CR; Do Pass, amended by committee substitute Commerce and Economic Development Oversight Committee
lower
Apr 9, 2025
Lower · Passed
Policy recommendation to the Commerce and Economic Development Oversight committee; Do Pass Government Modernization and Technology
lower
Apr 1, 2025
Committee
Referred to Government Modernization and Technology
lower
Mar 26, 2025
Introduced
First Reading
lower
Mar 26, 2025
Upper · Passed
Engrossed to House
upper
Mar 25, 2025
Committee
Referred for engrossment
upper
Mar 25, 2025
Upper · Passed
Measure and Emergency passed: Ayes: 46 Nays: 0
upper
Mar 25, 2025
Introduced
General Order, Amended by Floor Substitute
upper
Feb 25, 2025
Upper · Passed
Reported Do Pass as amended Retirement and Government Resources committee; CR filed
upper
Feb 3, 2025
Introduced
First Reading
upper
2 primary · 0 co-sponsors
Sponsors
Ask Maddy
·
AI policy assistant
Ask Maddy about SB 68
Scope: OK
Hi! I can help you understand SB 68. What would you like to know?
Try one of these
i
Maddy answers using official bill text and legislative records. Always verify before sharing.
Sources cited inline