This bill repeals and reenacts Utah Code §36-3-201 to establish fixed calendar start dates for the Legislature's annual budget session and two general sessions. It names the fourth Monday in February for the budget session, the first Monday in May for the first general session, and the second Monday in September for the second general session.
The changes take effect January 1, 2028, but only if the Legislature passes and Utah voters approve the constitutional amendment proposed in H.J.R. 22. The measure is procedural rather than fiscal — it contains no appropriations — but it shifts timing that affects agency budget preparation, legislative scheduling, lobby calendars, and public participation windows.
At a Glance
What It Does
The bill replaces the current statutory language with three fixed start dates: budget session on the fourth Monday in February, first general session on the first Monday in May, and second general session on the second Monday in September. It accomplishes this by repealing and reenacting Utah Code §36-3-201.
Who It Affects
Directly affects state legislators and legislative staff, executive branch budget and policy offices, rulemaking and permitting agencies, regulated industries and organized stakeholders that time advocacy around sessions, and the public that seeks to engage lawmakers. It also depends on a voter-approved constitutional amendment (H.J.R. 22).
Why It Matters
Fixing start dates creates predictable annual windows for lawmaking and budgeting, changing when agencies must produce budget proposals and when stakeholders lobby. Because it is contingent on a constitutional change, the statute will only bind scheduling if voters approve the companion amendment.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill substitutes a short, concrete schedule for the current statutory provision that governs when Utah’s annual sessions begin. Instead of leaving start dates to less-specific language or convention, the enacted text will identify three distinct calendar anchors: the annual budget session begins the fourth Monday in February; the first annual general session begins the first Monday in May; and the second annual general session begins the second Monday in September.
The statutory change is achieved by repealing the existing §36-3-201 and reenacting the new text.
This measure is explicitly contingent. It contains a special effective date clause: the statute will take effect on January 1, 2028 only if the Legislature passes H.J.R. 22 and a majority of voters approve that constitutional amendment at the next regular general election.
Until that constitutional change is approved by voters, the statutory text will not go into force, so the current scheduling framework remains in place.Because the bill makes no appropriations and does not alter session length or substantive legislative procedures, its direct legal effect is limited to calendar-setting. Practically, however, fixed start dates reallocate the seasonal workload for legislators, staff, state agencies preparing budgets and rules, and external stakeholders who synchronize advocacy and compliance activities with the legislative calendar.
The bill therefore shifts predictable timing across multiple operational processes even though it does not change policy authority or funding levels.
The Five Things You Need to Know
The bill repeals and reenacts Utah Code §36-3-201 to replace the current statutory language with a fixed-date schedule.
It sets the budget session to start on the fourth Monday in February, the first general session on the first Monday in May, and the second general session on the second Monday in September.
The statutory changes are conditional: they take effect January 1, 2028 only if the companion constitutional amendment (H.J.R. 22) is passed by the Legislature and approved by a majority of voters at the next regular general election.
H.B. 538 contains no appropriations or changes to session length; its sole substantive change is scheduling.
The bill repeals the version of §36-3-201 that was enacted in 2020 (Laws of Utah 2020, Chapter 383) and replaces it with the new dating scheme.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Repeal and reenact the statute that sets session start dates
Section 1 removes the existing text of §36-3-201 and substitutes three discrete subsections that name the start date for each annual session. By repealing and reenacting rather than amending piecemeal, the bill replaces prior language in a single move, reducing ambiguity about which text controls once the provision takes effect.
Budget session: fourth Monday in February
This subsection designates the annual budget session’s beginning date. For operational purposes, that places the budget session in late winter, establishing a predictable time when the executive and legislative budget offices will coordinate proposals, fiscal notes, and hearings.
Two general sessions: first Monday in May and second Monday in September
The bill separates the general-session calendar into two named annual sessions, fixing their start dates in early May and mid-September. These placements create recurring spring and late-summer/early-fall lawmaking windows that stakeholders and agencies will need to incorporate into annual planning cycles.
Special effective date tied to constitutional amendment
Section 2 delays the statute’s effective date until January 1, 2028 and conditions that effect on passage and voter approval of H.J.R. 22. If the constitutional amendment fails, the reenacted statute will not take effect, preserving the status quo calendar.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Legislators and legislative staff — gain predictable annual anchors for scheduling committee work, session preparation, and constituency outreach, which reduces last-minute calendar conflicts and helps plan interim work.
- State budget offices and executive agencies — can align budget-development timelines to a fixed legislative budget session, improving internal planning and resource allocation for fiscal analyses and hearings.
- Organized stakeholders and industry coalitions — advocacy and compliance teams benefit from knowing precise windows to prioritize lobbying, regulatory engagement, and public-comment campaigns.
- Municipalities and local governments — can synchronize local budget cycles and capital-planning schedules with a stable state budget session date.
- Members of the public and civic groups — predictable session dates make it easier to plan testimony, attend hearings, and engage in the legislative process when resources for participation are limited.
Who Bears the Cost
- State agencies with existing timelines — may incur administrative costs to shift internal deadlines, staff workloads, and rulemaking calendars to align with the new session dates.
- Legislative support infrastructure — the Legislature’s administrative and IT systems will need to adjust annual operational calendars, orientation schedules, and staff hiring/assignment cycles.
- Small advocacy groups and solo practitioners — although predictability helps planning, earlier or off-season session timing (e.g., May or September) can impose travel or staffing costs compared with traditional timing.
- Educational institutions and seasonal employers — fixed May and September sessions could conflict with academic schedules or peak business seasons, creating indirect operational strains for stakeholders who engage with lawmakers.
- Taxpayers (indirectly) — if implementing the new calendar requires one-time administrative changes, agencies may absorb transition costs that affect operating budgets.
Key Issues
The Core Tension
The central dilemma is predictability versus flexibility: fixed statutory start dates give agencies, stakeholders, and the public reliable planning anchors, but they remove calendar flexibility that helps the Legislature respond to atypical workloads, emergencies, or evolving policy priorities; conditioning the statute on a voter-approved constitutional amendment amplifies uncertainty during the transition.
The bill’s practical effect depends entirely on a constitutional amendment passed by voters. That contingency creates an implementation cliff: agencies and stakeholders must decide whether to plan to the new dates now or wait for electoral confirmation, creating short-term uncertainty.
The statute itself does not change session length or procedural deadlines elsewhere in law, so calendar certainty in one statute may collide with existing timing in other statutes (filing deadlines, effective dates for enacted statutes, or agency rulemaking milestones) that still reference relative or different fixed dates.
Fixing start dates also redistributes workload across the calendar. Moving a budget session to late February and adding general sessions in May and September can improve predictability but may compress or fragment policy work across the year.
That fragmentation can raise coordination costs for multi-agency policy initiatives and make it harder to align the budget with ongoing program implementation. The bill contains no transition resources, so administrative adjustments would have to be absorbed within existing agency and legislative budgets.
Finally, because the bill merely sets dates and not length, it leaves open how long sessions will run and how sick or emergency conditions would be handled when dates are locked in statutory language.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.