Washington State Enacts Near-Total Ban on Noncompete Agreements
Washington Governor Bob Ferguson has signed SHB 1155 into law, effectively voiding nearly all noncompete agreements for employees and independent contractors starting June 30, 2027. The legislation marks a significant shift for the state's massive tech sector, applying retroactively and requiring employers to notify staff of the change by October 2027.
Key Takeaways
- Washington Governor Bob Ferguson has signed SHB 1155 into law, effectively voiding nearly all noncompete agreements for employees and independent contractors starting June 30, 2027.
- The legislation marks a significant shift for the state's massive tech sector, applying retroactively and requiring employers to notify staff of the change by October 2027.
Key Intelligence
Key Facts
- 1SHB 1155 voids nearly all noncompete agreements for employees and contractors effective June 30, 2027.
- 2The law applies retroactively to all existing agreements regardless of the signing date.
- 3Employers must provide written notice to current and former staff by October 1, 2027, regarding the change.
- 4The ban removes previous high-earner exceptions established in Washington's 2019 noncompete law.
- 5Narrowly-drafted nonsolicitation agreements remain permissible under the new legislation.
- 6Legal proceedings filed before June 30, 2027, will still be governed by the prior version of the law.
Who's Affected
Analysis
The signing of Substitute House Bill (SHB) 1155 by Washington Governor Bob Ferguson represents a watershed moment for the Pacific Northwest’s technology ecosystem. By enacting a near-total ban on noncompete agreements, Washington joins a small but influential group of states—including California, Minnesota, Oklahoma, and North Dakota—that have moved to prioritize labor mobility over traditional corporate restrictive covenants. For the SaaS and Cloud sectors, which are anchored in Washington by giants like Microsoft and Amazon, this law fundamentally alters the competitive landscape for high-level engineering and executive talent.
Historically, Washington’s approach to noncompetes was governed by a 2019 statute that limited their use to high-earning individuals. SHB 1155 dismantles that threshold-based system entirely. Starting June 30, 2027, all noncompetition covenants will be considered void and unenforceable, regardless of when they were signed or how much the employee earns. This retroactive application is particularly aggressive, as it effectively nullifies thousands of existing contracts overnight. The law’s definition of a noncompetition covenant is intentionally broad, covering any agreement that restrains an individual from engaging in a lawful profession or business, including provisions that threaten the forfeiture of rights or benefits upon departure.
The signing of Substitute House Bill (SHB) 1155 by Washington Governor Bob Ferguson represents a watershed moment for the Pacific Northwest’s technology ecosystem.
The implications for the cloud infrastructure and software-as-a-service markets are profound. In an industry where specialized knowledge of proprietary architectures and client relationships is the primary currency, companies have long relied on noncompetes to prevent 'brain drain' to direct competitors. With this legal tool removed, Washington-based firms must pivot their retention strategies. We expect to see a surge in the use of narrowly-tailored nonsolicitation agreements and a heightened focus on trade secret litigation as the primary means of protecting intellectual property. Furthermore, the law requires employers to make 'reasonable efforts' to provide written notice to all current and former employees by October 1, 2027, informing them that their noncompetes are no longer valid—a massive administrative undertaking for large-scale enterprise organizations.
What to Watch
Critics of the ban argue it could lead to increased litigation over trade secrets and potentially discourage investment in employee training. However, proponents point to California’s tech dominance as evidence that high labor mobility actually fosters innovation by allowing talent to flow toward the most productive uses. For SaaS startups, this change lowers the barrier to hiring experienced talent from established incumbents, potentially accelerating the pace of disruption in the cloud market. Conversely, established players may respond by shifting more compensation into deferred structures that are not tied to non-competition, or by increasing the use of 'garden leave' provisions, though the legality of the latter under the new broad definition remains a point of future legal contention.
As the June 2027 effective date approaches, legal departments in the SaaS sector must begin auditing their existing employment contracts. The law does provide a safe harbor for legal proceedings filed before the effective date, which may trigger a rush of enforcement actions in early 2027 as companies attempt to lock in restrictions under the outgoing legal framework. Long-term, this regulation signals a national trend toward the 'Californication' of labor law, where the protection of trade secrets, rather than the restriction of human capital, becomes the central pillar of corporate security.
Timeline
Timeline
Previous Restrictions
Washington limits noncompetes to high-earning employees and contractors.
SHB 1155 Signed
Governor Bob Ferguson signs the near-total ban into law.
Effective Date
All noncompetition covenants become void and unenforceable in Washington.
Notification Deadline
Final date for employers to notify staff that noncompetes are no longer enforceable.
Cite This Page
"Washington State Enacts Near-Total Ban on Noncompete Agreements." SaaS Intelligence Brief, March 25, 2026. https://getsaasbrief.com/story/washington-state-noncompete-ban-shb-1155
How we covered this story
Every story in our saas coverage is assembled from multiple primary sources, cross-referenced for factual consistency, and scored along three independent dimensions: sentiment, operational impact, and source-cluster confidence. Single-source rumors and unverifiable claims do not pass our editorial gate. When a story shows "Verified by N sources" with N≥2, the development is independently corroborated; when N=1, we mark it explicitly so readers can weigh the signal accordingly.
Impact scoring uses a 1-10 scale weighted toward regulatory, financial, and operational consequence rather than coverage volume. A topic that runs in every outlet but moves no real decisions ranks lower than a niche regulatory filing that reshapes how operators in the saas space have to behave. Read our full methodology for the scoring rubric, our glossary for term definitions, and our trends index for the longitudinal view across the beat.
Sources are only linked to a story once they clear our classification pipeline at a minimum 35 percent relevance threshold. According to that methodology, reviewed July 2026, this follows multi-source corroboration standards recommended by journalism research bodies such as the Reuters Institute for the Study of Journalism.
See something wrong in this story — a wrong fact, a broken source link, a misattributed entity? Report a data issue.
| Signal on this page | What it tells you |
|---|---|
| Verified by N sources | Independent corroboration count. N≥2 is our confidence floor; N=1 is marked explicitly. |
| Impact score (1-10) | Regulatory + financial + operational weight. 8+ signals an experienced-operator action item. |
| Sentiment | Five-tier classification trained on labeled saas-specific corpora. |
| Timeline | Where applicable, the related-events sequence that contextualizes today's development. |