State legislative session calendars: how to plan your tracking year
When do state legislatures meet, what are crossover and sine die, and why does most legislation pass in a six-week window? A tracking-focused calendar guide.
Legislative tracking has a seasonality problem that surprises every team in their first year. From January to April the alerts flood in. By July, silence in most states. Teams that staff and configure for the average get buried in the spring and pay for idle coverage in the summer.
The fix is understanding the session calendar: when legislatures meet, the internal deadlines that shape what survives, and where the real action concentrates. This guide covers the calendar mechanics that matter for tracking, and how to plan your year around them.
The shape of a legislative year
Most state legislatures convene in early January and adjourn somewhere between March and June. Within that window, activity follows a predictable arc:
| Phase | Typical timing | What happens | Tracking implication |
|---|---|---|---|
| Prefiling | Nov - Dec | Bills filed before session opens | Earliest possible look at the coming session |
| Introduction surge | Jan - Feb | Most bills introduced, deadlines force the pace | Highest volume of new-match alerts |
| Committee season | Feb - Mar | Hearings, amendments, committee votes | Amendment alerts matter most here |
| Crossover | Mid-session | Bills must clear their chamber of origin | Live universe cut roughly in half |
| Endgame | Final 2-3 weeks | Floor votes, conference committees, deals | Fastest, highest-stakes period of the year |
| Sine die | Mar - Jun | Formal adjournment | Surviving bills go to the governor |
| Interim | Summer - Fall | Study committees, task forces | Next year’s bills take shape |
Two things about this arc are worth internalizing.
First, introduction volume front-loads hard. Many states impose bill introduction deadlines in the first weeks of session, so the bulk of the year’s bills appear in a four-to-six week burst. If your triage process can’t handle that burst, it doesn’t matter how well it handles the average week.
Second, passage back-loads just as hard. A large share of everything that becomes law passes in the final weeks before sine die. The endgame compresses months of negotiation into days, with amendments adopted on the floor and conference reports appearing overnight. This is when alert latency matters most: a daily digest is fine in February and dangerously slow in the last week of session.
These phases shift by state. A state that adjourns in early March, like Virginia in its short-session years, runs this entire arc in about eight weeks. California stretches it across most of the year. The arc is the same; the tempo isn’t.
Annual, biennial, and full-time legislatures
Not every state meets every year, and not every state meets briefly.
Four states meet only in odd-numbered years: Montana, Nevada, North Dakota, and Texas. In an even year like 2026, these states hold no regular session at all. Texas alone accounts for a large share of national legislative volume when it meets, so odd years feel very different from even years for any multistate program.
Most states meet annually but with limited sessions, often 60 to 120 calendar days, sometimes shorter in the second year of the biennium. Several states alternate long and short sessions: the long session handles the budget and the broad agenda, the short one is nominally limited but rarely quiet.
Roughly ten states run effectively full-time or near-year-round legislatures, including California, New York, Pennsylvania, Michigan, Massachusetts, Illinois, Ohio, and Wisconsin. In these states there is no true off-season, and tracking has to run at full attention most of the year.
The practical consequence: a 50-state tracking program is really a portfolio of overlapping calendars. In any given month, some states are in their endgame, some are mid-committee-season, and some are adjourned. Your alert configuration should reflect which phase each state is in, not treat all 50 as if they share one clock.
Carryover: dead or dormant?
When a session ends, what happens to unpassed bills depends on the state’s carryover rule, and getting this wrong leads to two opposite mistakes.
In carryover states, a bill introduced in the first year of the two-year biennium stays alive into the second year. A bill that looked dead in June can be scheduled for a hearing the following January with no warning beyond the hearing notice itself. Teams that purge their watch lists at adjournment in these states get blindsided.
In non-carryover states, everything dies at sine die. But “dead” is also misleading here, because the bill’s content usually returns next session under a new number, often pre-filed in December. The right move is not to forget the bill but to note the sponsor and the subject, and expect the sequel.
Do a calendar audit at each adjournment: for every tracked bill that didn’t pass, record whether it carries over or died, and if it died, set a reminder to watch for reintroduction in the prefiling window. This one-hour ritual per state is the cheapest insurance in legislative tracking.
Special sessions: the calendar’s exception
Everything above describes regular sessions. Special sessions ignore all of it.
A governor (or in some states, the legislature itself) can call a special session at any time, on any timeline, usually limited to named topics. Special sessions are short, fast, and high-yield: when leadership calls one, it is usually because the votes already exist, so bills can move from introduction to passage in days.
For tracking teams, special sessions are the stress test. A tool that refreshes a state’s data daily can miss an entire committee stage. If your jurisdictions include states with a history of frequent special sessions, ask your vendor specifically how special session calendars are detected and how quickly new filings appear. It is a revealing question, because special sessions don’t follow the URL patterns and schedules that scrapers are built around. We wrote more about per-state data plumbing in our state legislative data sources guide.
Planning your tracking year
Pulling it together, here is a calendar-aware operating rhythm for a multistate tracking program:
December - January. Review and refresh practice-area definitions before the introduction surge, not during it. Confirm coverage for every state convening in January. Watch prefiled bills: they signal leadership priorities.
February - March. Peak triage season. Expect the highest alert volume of the year. Use crossover deadlines as natural cleanup points: when a state hits crossover, archive everything that missed it and re-prioritize what survived.
April - June. Endgame season rolls across the country as states adjourn one by one. Tighten alert cadence to real-time for any tracked bill in a state inside its final two weeks. This is when amendments and conference reports change outcomes overnight.
July - November. Interim season for most states, full speed for the year-round legislatures. Run adjournment audits, track interim study committees in your topic areas (they write next year’s bills), and use the quiet months for the tool evaluations and workflow fixes there was no time for in March.
How LawSignals handles the calendar
LawSignals tracks all 50 states, DC, and Congress on one schema, with coverage that follows each state’s actual calendar, including special sessions. Alert cadence is configurable per category and per signal, so you can run daily digests in the quiet months and real-time pushes for endgame weeks without rebuilding your setup each time. Carryover status is part of the bill record, so a dormant bill and a dead one don’t look the same in your feed.
If the spring surge buried your team this year, book a demo and we’ll walk through what a calendar-aware alert setup looks like for your jurisdictions.
Related solutions: See our state legislation tracking page for multistate coverage details, learn about legislative tracking workflows, or read how to track bills across all 50 states for the full playbook.
