In Washington State - the vote is not the end of a bill.

It is the beginning of the handoff.

A new law leaves Olympia as text. It lands in your community as a staff assignment, a budget line, a code update, a dispatch agreement, a court process, a housing fund, or a council meeting that nobody outside City Hall ever watches.

Before lawmakers vote, the state often writes a fiscal note. The note estimates what a new law might cost, save, or shift. Sometimes it looks only at state agencies. Often, it reaches down into the places where government actually touches people: cities, counties, courts, planning departments, 911 systems, and housing programs.

Then lawmakers pass the bill.

The spreadsheet stops moving.

The work does not.

The estimate stays in Olympia. The consequences show up months later in city ordinances, county agreements, budget books, planning commission packets, and obscure fund lines. If you are a resident trying to answer a basic question – what did this law actually do to my city? – the system does not make that easy.

That should bother people across the political spectrum.

If the state estimates that a bill will push work onto cities, the public should be able to see whether that happened. If the state changes who gets local revenue, the public should be able to see where the money went. If a law creates a new local duty, voters should be able to see whether local governments absorbed it, budgeted for it, delayed it, fought over it, or ignored it.

This is the fiscal note trap.

Washington prices the bill before the vote, then leaves the public to hunt for the bill after it lands.

You can find the pieces if you know where to look. A fiscal note here. A city council ordinance there. A county press release. A budget fund. A planning packet. A bill report. A staff memo. But the public does not get one clean answer.

That is not transparency. That is a scavenger hunt.

Washington does not need fewer fiscal notes. It needs a habit of checking what happened after the vote.

That picture is the whole problem. Washington can usually show the forecast. It can show the bill. Local governments can often show the machinery they built afterward. What disappears is the final public check.

In 2025, HB 1258 dealt with who gets 911 revenue when a city takes on emergency call-center responsibilities.

That sounds like a technical finance bill. It is not.

When someone calls 911, somebody has to answer. Somebody has to staff the system. Somebody has to pay for the dispatch infrastructure, technology, management, and transition work. And if state law dedicates local tax money to that system, somebody has to decide whether the money follows the work.

In Spokane, this did not stay theoretical.

Spokane had been part of a regional emergency communications structure. Then the city moved toward creating its own public safety answering point. That local shift raised an obvious fiscal question: if Spokane takes on the emergency communications responsibility, does it also receive a fair share of the 911 revenue?

Olympia saw the issue before passage. HB 1258 addressed a revenue-transfer mechanism. Counties receiving 911 excise-tax revenue would have to transfer a portion to a local government operating a municipal public safety answering point or receiving calls transferred from the regional 911 system.

Then local government did what local government always has to do. It turned the state rule into machinery.

Spokane adopted Ordinance C36743, establishing the Spokane United 911 Network as the city’s primary public safety answering point. Spokane also created a dedicated Spokane United 911 Network Fund, which can receive revenue and pay expenses for establishing and maintaining the city system.

Spokane County later said the City of Spokane, Spokane County, and Spokane Regional Emergency Communications approved an interlocal agreement setting expectations for emergency communications and funding as Spokane moves toward its own system. As of June 2026, that transition is underway. It began in January 2026, with full implementation of the city’s public safety answering point expected in January 2028.

That is the real story.

Not “Olympia passed a bill.” Not “local government complained.” The story is that a state fiscal question became a local fight over service responsibility and revenue.

The public can understand that story. A resident does not need a public-finance degree to understand that money should follow responsibility.

But the system does not tell the story in one place.

This case matters because it complicates the lazy version of the debate. This was not simply an unfunded mandate. It was not simply a city asking for more money. It was a local service question: when responsibility moves, should revenue move with it?

That is exactly the kind of question fiscal notes should help us track.

The fiscal note tells lawmakers something before the vote. The local records tell us what happened after the vote. But unless someone stitches those pieces together, the public sees only fragments.

HB 1260 dealt with document-recording fee revenue for homeless housing programs. That phrase will not light up a campaign rally. But the issue matters because local homelessness programs depend on money moving through the right pipe.

The bill report says the document-recording surcharge supports state and local homeless housing programs. It also says that when a city operates its own local homeless housing program, counties must distribute part of the county-retained portion to those cities.

The local context matters. Spokane and Spokane Valley operate local homeless housing programs separate from Spokane County. Supporters of the bill said ambiguity in current law caused those cities to receive less funding for local homeless housing programs and administrative costs.

In plain English: the bill addressed whether money collected through the system actually reached the local programs responsible for using it.

Spokane Valley’s budget makes that abstract policy concrete.

The city’s 2025 adopted budget says Spokane Valley passed Resolution 23-009 to operate a local homeless and housing program and assume collection of available document-recording fees. It says Spokane County collects those fees and passes them through to Spokane Valley based on the city’s proportionate share of real estate excise tax collected monthly.

The Homeless Housing Program Fund shows $290,000 in recording-fee revenue for 2025.

The city’s 2026 adopted budget shows $365,000 in recording-fee revenue and $372,000 in total revenues for that fund.

The chart does not prove HB 1260 caused the increase. It shows something just as important for public accountability: this is where a state fee rule becomes a local budget line a resident can actually inspect.

Again, this is not the usual political story.

No one is marching under a banner that says “document-recording fee distribution clarity.” But that does not make the issue small. Fiscal plumbing decides whether local homelessness money is visible, usable, and governed.

A budget reader can see the dollars in Spokane Valley. A bill reader can see the state law. A local official may understand the pass-through. But the public still has to connect the bill, the county collection, the city fund, and the local housing purpose.

That work should not require a private research project.

HB 1096, the lot-splitting bill, required cities to allow an administrative process for certain residential lot splits. The fiscal note estimated about $1.2 million in city work to update or adopt administrative lot-split ordinances. It described planning, permitting, legal, administrative, and staff-training costs.

That is a clear pre-vote estimate. Lawmakers had reason to know the bill would not implement itself. It would land on city planning desks.

Local records show that work starting to land. Kirkland planning materials say zoning-code amendments are needed by the July 27, 2027 deadline. Bellevue lists HB 1096 lot splitting as a state-law compliance item. Snohomish County says the law inspired proposed local code amendments, even though the law technically applies to cities.

But I still do not have the clean final receipt.

I do not have a city ordinance that closes the loop. I do not have a local cost record that tells us whether the state’s estimate was close. I can see the work moving through local planning channels, but I cannot yet say what the final city-by-city cost was.

That missing answer matters.

It shows the difference between an estimate and accountability. The fiscal note can tell lawmakers what might happen. Local planning records can show the work beginning. But without a follow-up habit, no one gives the public a clean answer after implementation.

This gap hits different people in different ways.

For residents, it turns local government into a fog machine. A person can see their city budget getting tighter. They can hear their council talk about staffing, fees, dispatch costs, planning backlogs, or housing money. But they may never see how much of that pressure came from local choices, how much came from state policy, and how much came from a formula buried in a bill report.

For city and county officials, the gap creates a credibility problem. Local officials often know when state policy lands on their desks. They know when staff have to rewrite code, negotiate agreements, update funds, train employees, or explain a new requirement to the public. But if they cannot point to a clear state-to-local follow-up record, their complaint can sound like ordinary budget whining. The paper trail exists, but the burden of proving it falls on the people already doing the work.

For lawmakers, the gap weakens learning. Fiscal notes should not just help pass or kill bills. They should help the Legislature get smarter over time. If a fiscal note overestimated local cost, lawmakers should know. If it missed a hidden workload, they should know. If a revenue shift solved a real local dispute, they should know that too.

And for voters, the gap blurs accountability. If a service gets worse, a fee rises, a fund gets raided, or a local department falls behind, residents deserve to know whether the cause was local mismanagement, state policy, inflation, court action, or some mix of all four.

That is why this matters. It is not about paperwork for paperwork’s sake. It is about whether people can follow power after the vote.

This is where the phrase “unfunded mandate” can obscure as much as it reveals.

Some state laws create direct local costs. Some shift revenue. Some clarify who receives money. Some create deadlines. Some give optional authority. Some create work that cities absorb into existing staff time. Some never fully land because a court, agency, or implementation problem changes the facts.

Those distinctions matter.

But all of them raise the same public question:

Who checks what actually happened?

Right now, Washington’s process gives lawmakers a forecast. It does not give residents a scorecard.

/

Imagine a simpler system.

For any bill with meaningful local fiscal exposure, the state could publish a short post-passage follow-up after implementation begins:

That would not settle every argument. It would not end disputes over housing, public safety, homelessness, or local control. But it would force the debate onto firmer ground.

It would also make state government learn from itself.

If fiscal notes routinely overestimate local costs, lawmakers should know that. If they routinely miss staff workload, lawmakers should know that too. If state bills shift revenue in ways that solve local disputes, that should become visible. If bills create quiet administrative work that cities absorb without clear budget lines, that should not disappear.

The point is not to blame Olympia for everything local governments face. Local budgets are complicated. Inflation, labor costs, population growth, federal rules, court decisions, local choices, and existing service pressure all matter.

The point is simpler: when the state writes down an expected local impact before a vote, someone should come back later and ask whether the expectation matched reality.

That is basic public accounting.

It is also good politics.

Voters do not trust government because officials tell them to trust it. They trust government when it shows its work, admits uncertainty, and follows through.

HB 1258 (2025) shows how a state fiscal question can become a local revenue and service fight. HB 1260 (2025) shows how a state fee rule can become a city budget line. HB 1096 (2025) shows how a state estimate can start moving through local planning work while the final cost remains hard to see.

None of these examples tells the whole story of Washington government. Together, they show a pattern.

The pieces exist.

The fiscal note exists. The ordinance exists. The county agreement exists. The city budget exists. The planning packet exists.

The missing thing is the public habit of putting them back together.

That is the real bill Washington has not priced.

And that is the trap.

The state prices the bill before the vote. The city lives with the math after it passes. The resident deserves to see both.

·      HB 1258 (2025): House bill analysis, Spokane Ordinance C36743 meeting record, Spokane United 911 Network Fund, Spokane County ILA announcement.

·      HB 1260 (2025): House bill report, Spokane Valley 2025 adopted budget, Spokane Valley 2026 adopted budget, Spokane Valley council recap.

·      HB 1096 (2025): Fiscal-note package, Kirkland planning packet, Bellevue code-amendment page, Snohomish County lot-splitting staff report.