Who benefits? Who pays?
Spokane is growing. Each section below says what the change is meant to do, what it actually guarantees, and what to ask the City to show.
Homes and renters
800 new homes a year is the City's housing target through 2046. Permission to build is not the same as homes people can afford, and the plan guarantees the first, not the second.
The intended benefit. Make room for more homes and put more of them within reach of people who need a place to rent or buy.
What can change. The plan can allow apartments, six-plexes, and other housing types in more places. Tax breaks and other incentives can make some projects easier to finance. Rent rules can give tenants more predictability while changing how landlords manage costs and risk.
What is not guaranteed. Permission to build is not construction. Construction is not affordability. An affordability label does not prove that a home costs less than the market or is within reach of someone making about $40,000 a year.
What to ask. How many homes will be affordable to lower-income households? For how long? Who checks the rents or sale prices, and what happens when a promise is missed?
Neighborhoods and the environment
Faster permitting is the point of several proposed changes. Which protections still apply at that speed is the open question.
The intended benefit. Add homes near jobs, services, and transit, and reduce delays that can make projects harder or more expensive.
What can change. New maps can allow taller buildings and more uses near existing neighborhoods. Expanded SEPA exemptions can let more projects proceed without a separate environmental review.
What is not guaranteed. Faster approval does not guarantee that mature trees, habitat, water, historic resources, traffic, or nearby homes will be protected. Replacement or later mitigation may not provide the same public value as retention.
What to ask. Which protections remain enforceable before a project is approved? Who measures the result? What happens when tree-canopy, traffic, infrastructure, or environmental targets are missed?
Data centers
500 megawatts is what one proposed data center would draw, about half the electricity used by every home and business in Spokane County. The City's pause reaches only the smallest of the three proposals.
The intended benefit. A big project can bring construction jobs, tax revenue, and utility upgrades that other customers may use later. Washington's data center sales-tax exemption does not reach Spokane County, so a project built here pays sales tax on its equipment today.
What can change. A large customer can arrive faster than the rules that govern it. Serving one can mean new power plants, new power lines, and more water.
What is not guaranteed. The City's pause stops at the city line, and two of the three proposals sit outside it. Most construction jobs end when construction does. If a customer leaves before its equipment is paid off, everyone else can be left with the bill.
The same water and power serve housing. The plan calls for about 800 new homes a year through 2046. Every one of them needs water, power, and sewer from the same systems these proposals would draw on.
What to ask. Show the math: how much water and power do 800 homes a year need, how much is already promised to large customers, and what changes if there is not enough for both? Everyone says a big customer should pay for what it needs, so what makes that stick, and who checks? When supply runs short, who cuts back first? And when a customer sits outside the city but drinks City water, what can Spokane require?
Spokane owns its water. It does not own the power. City Council is also the water board, so what large users pay for water, and who cuts back first in a drought, are City decisions. Electricity is different: Avista is a private company and the state sets its rates, so that ask goes to the state.
“… your Council is the water board for the City of Spokane. We will be having a study session. I requested that from legal.”— Betsy Wilkerson, Spokane City Council, City Council Meeting, Jul 29, 2026
“I do believe that there is a responsibility for developers when they come in to bear that cost of the expansion of the grid if needed for their use and it shouldn't be put on the residents to increase their power bills”— James Daniels, IBEW Local 73, City Council Meeting, Jul 29, 2026
Businesses and property owners
Room to build is not a project, a customer, or the streets and utilities to serve one.
The intended benefit. Clearer rules can make investment more predictable, bring more customers near shops and services, and help underused property support new activity.
What can change. Plan maps and development-code updates can change where homes, shops, and other businesses are allowed. They can also change parking, landscaping, design, setbacks, and project-review rules.
What is not guaranteed. Added development capacity does not guarantee a project, a higher property value, or enough streets and utilities to support the change. New restrictions can also affect an owner or business that made decisions under the earlier rules.
What to ask. Which uses become allowed or restricted? What happens to existing lawful businesses? Who pays for needed infrastructure, and how much time will owners have to adjust?
Use one test for every promise
The same questions should apply to the City, developers, landlords, property owners, renters, businesses, and advocates.
Name the map, rule, incentive, review, or public investment.
Name the people who receive new options, protection, money, time, or development value.
Count taxes, fees, rent, infrastructure, maintenance, lost protections, and shifted burdens.
Separate permission and intended benefits from enforceable results.
Give the promise a baseline, deadline, and responsible party.
Publish the measure, result, enforcement record, and response when the target is missed.