Revise reporting requirements related to public contracts
HB 627 revises reporting requirements for public contracts. It mandates the Department of Administration to provide quarterly reports to the Legislative Finance Committee. These reports must include details on procurement solicitations, executed contracts, and contract modifications that are anticipated or expected to cost $250,000 or more over the life of the contract. The information includes the purchasing agency, what is being procured, and contractor names.
Bill status
signed
all 5 stages cleared
Introduction
Feb 2025
Committee Review
Apr 2025
House Passage
May 2025
Senate Passage
May 2025
Signed into Law
May 2025
Introduced Feb 21, 2025
Signed May 16, 2025
Maddy AI version diff · 7 comparisons
What changed between versions
HB0627_X(1).pdf
→
HB0627_X(2).pdf
·
3 edits
MINOR
The bill was amended to clarify that the Department of Administration is responsible for reporting procurement data. The most significant policy change is a reduction in the financial reporting threshold from $250,000 to $200,000 for contracts, solicitations, and modifications, requiring more agencies to report their spending. The bill also adds a requirement to include the solicitation closing date in reports and clarifies that reports must be submitted using the department's existing information technology resources.
Scope change
The bill now explicitly names the 'Department of Administration' as the reporting entity and expands the scope of reporting to include all contracts, solicitations, and modifications exceeding $200,000, whereas the previous version only applied to solicitations and contracts over $250,000.
REQUIREMENT
The financial threshold for mandatory reporting was lowered from $250,000 to $200,000, increasing the number of contracts that must be reported.
A new requirement was added to report the closing date of the solicitation.
TECHNICAL
The title and text were updated to explicitly name the 'Department of Administration' and clarify that reports must be submitted using the department's information technology resources.
Floor votes · Senate Apr 24, 2025 · House Mar 7, 2025
How they voted
50–0
Passed
Total votes 50
Apr 24, 2025
D
Democratic18
100% Yea
R
Republican32
100% Yea
Vote distribution
All Yea
All Nay
Mixed
No data
Full legislative history
Actions timeline
Total actions
44
Key actions
9
Committee
6
May 13, 2025
Signed into law
(H) Signed by Governor
lower
May 2, 2025
Upper · Passed
(S) Signed by President
upper
May 1, 2025
Lower · Passed
(H) Signed by Speaker
lower
Apr 24, 2025
Senate · Passed
Senate Vote: pass (50-0)
senate
Apr 17, 2025
Upper · Passed
(S) Committee Report - (S) State Administration
upper
Apr 16, 2025
Upper · Passed
(S) Committee Executive Action - (S) State Administration
upper
Mar 14, 2025
Committee
(S) Referred to Committee - (S) State Administration
upper
Mar 7, 2025
House · Passed
House Vote: pass (99-0-1)
house
Feb 28, 2025
Lower · Passed
(H) Committee Report - (H) State Administration
lower
Feb 28, 2025
Lower · Passed
(H) Committee Executive Action - (H) State Administration
lower
Feb 21, 2025
Committee
(H) Referred to Committee - (H) State Administration
lower
Feb 21, 2025
Introduced
(H) Introduced
lower
1 primary · 0 co-sponsors
Sponsors
Role
Legislator
Party
State
District
P
Bill Mercer
RRepublican
Ask Maddy
·
AI policy assistant
Ask Maddy about HB 627
Scope: MT
Hi! I can help you understand HB 627. 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