Once a court or arbitrator finds a violation, the violator pays the greater of actual damages or five thousand dollars, plus reasonable fees and costs.
Key takeaways
Good letters for Washington hires usually do four things:
- They list any noncompetition covenant as its own item, with the scope stated in words a reader can follow.
- They describe outside-work limits in terms of the specific schedule or safety concern, not as a blanket ban.
- They state the hours and availability the job requires, so the scheduling reason is visible on the page.
- They avoid language that assumes a court will rewrite an overbroad restriction, since a rewrite can itself carry the penalty described in this post.
What does Washington's noncompete chapter cover?
Chapter 49.62 RCW is the state law to check whenever an offer letter or onboarding packet limits what a hire can do for another employer, or on their own. The chapter addresses noncompetition covenants, and it also limits when an employer can restrict outside work during employment. Every legal point in this post comes from the chapter text on the Washington State Legislature website.
This post is for hiring managers and small staffing teams who draft these documents, often by adapting older documents inherited from an earlier hire or a previous employer. It covers the money at risk, the parts of the chapter that affect drafting, and a short review routine you can run before any document goes out. It does not replace advice from a Washington employment lawyer who has read your actual documents.
A clause that has sat in an old document for years can feel harmless because nobody has ever enforced it. Each new offer that carries the clause is a new document, though, and it deserves its own check.
What the penalty requires
The chapter says that if a court or arbitrator determines that a noncompetition covenant violates this chapter, "the violator must pay the aggrieved person the greater of his or her actual damages or a statutory penalty of five thousand dollars, plus reasonable attorneys' fees, expenses, and costs incurred in the proceeding." ( Chapter 49.62 RCW)
The phrase "greater of" is the part to read carefully. The statutory figure of five thousand dollars works as a floor, not a ceiling. If the worker can show actual damages above five thousand dollars, the larger figure is what the violator owes. If actual damages are smaller, the five thousand dollar figure applies instead. Either way, the reasonable attorneys' fees, expenses, and costs from the proceeding are added on top.
The quoted text does not define actual damages, so a dispute over that figure can turn on evidence about what the worker actually lost. That is one more reason a restriction should not be drafted on the assumption that the exposure will be small.
That structure means one dispute can cost more than the penalty itself. A small staffing firm that loses a noncompete case may owe the worker's reasonable fees and costs in addition to the amount the court sets. For a company with thin margins, that comparison should happen before a restriction goes into a standard document, not after a worker hires a lawyer.
The penalty also follows a finding. The trigger in the chapter is a court or arbitrator's determination that a covenant violates the chapter. Nothing in the quoted text makes a clause sitting unused in a file safe, so keep that in mind when someone says a clause "never gets used."
The chapter names courts and arbitrators together, so an arbitration clause does not change the penalty analysis. The same statutory amount applies whether a court or an arbitrator makes the finding. Choosing arbitration to keep a dispute quiet is therefore not a way to reduce the exposure described here.
Illustrative example: the greater-of rule
Suppose an offer bars all outside work for a worker who earns less than the threshold the chapter describes. If a court finds the clause violates the chapter and actual damages are 3 thousand dollars, the violator owes the greater figure, five thousand dollars, plus reasonable fees and costs. If actual damages were 9 thousand dollars, that larger figure would apply instead, with the same fees and costs.
Does the penalty apply if a judge only trims the clause?
Yes. The chapter applies the same penalty when a court or arbitrator changes a clause rather than enforcing it as written. The text says that if a court or arbitrator "reforms, rewrites, modifies, or only partially enforces any noncompetition covenant, the party seeking enforcement must pay the aggrieved person the greater of his or her actual damages or a statutory penalty of five thousand dollars, plus reasonable attorneys' fees, expenses, and costs incurred in the proceeding." ( Chapter 49.62 RCW)
This cuts against a common drafting habit. Some teams write a broad restriction on the theory that a judge will narrow it to something reasonable. Under this subsection, the narrowing itself can trigger the penalty, and the party that must pay is the one seeking enforcement. A company that asks a court to cut back an overbroad clause, and then gets a smaller version enforced, can still fall under the text that requires payment.
The safer approach is to draft a restriction you would be prepared to defend as written. If a clause only works after a judge trims it, it is not ready for an offer. Remove it, or narrow it yourself before the offer goes out, and have a lawyer review the revised language.
Can an employer stop a worker from taking a second job?
Not in every case. The chapter sets a protection for employees who earn below a certain level, and it has one narrow exception. The statute says that, subject to that exception, an employer "may not restrict, restrain, or prohibit an employee earning less than twice the applicable state minimum hourly wage from having an additional job, supplementing their income by working for another employer, working as an independent contractor, or being self-employed." ( Chapter 49.62 RCW)
Two details matter when you draft. First, the protection depends on pay. It covers an employee earning less than twice the applicable state minimum hourly wage. Before you write any outside-work limit, confirm the hire's pay rate and the state minimum hourly wage that applies to that hire ( Washington and New York checks for hourly new hires). Do not rely on a figure you remember from an earlier year. The quoted sentence does not give the same protection to an employee who earns at or above that level, so a higher-paid hire needs a separate check against the rest of the chapter.
Second, the protected activities are listed. The chapter names having an additional job, supplementing income by working for another employer, working as an independent contractor, and being self-employed. A clause that bans all other work reaches well past that list. It should be read against the chapter's text, and against the exception, before it is used.
Employers sometimes assume that an offer letter can simply say "no outside work" and leave the details for later. The statute does not support that shortcut. The list and the earnings condition are the starting point for any outside-work term, and a term that ignores them invites the dispute it was meant to prevent.
When can an employer limit outside work?
The exception is narrow, and it applies only in two situations. The chapter says the outside-work protection "shall not apply to any such additional services when the specific services to be offered by the employee raise issues of safety for the employee, coworkers, or the public, or interfere with the reasonable and normal scheduling expectations of the employer." ( Chapter 49.62 RCW)
Read that closely. The exception turns on "the specific services to be offered by the employee," not on outside work in general. A limit tied to a real safety concern with those specific services, or to a real conflict with the employer's reasonable and normal scheduling expectations, fits the text. A limit that says only "no other employment" names neither reason. It asks the hire to accept a blanket rule that the exception does not describe.
A simple test helps. Ask three questions about any proposed limit. What specific services would the hire perform outside the job? Which safety issue or scheduling conflict would those services create? Does the limit stop where that conflict stops, or does it reach further? If the answers are vague, the limit is probably broader than the exception allows.
In practice, put the reason in writing. If the concern is scheduling, describe the schedule the hire must keep, such as the shifts or availability the job requires. If the concern is safety, name the specific safety issue. A limit that lasts longer than the scheduling conflict or the safety concern it describes will be harder to justify, so tie the limit to the reason and keep its scope to match. A reviewer who reads the limit should be able to tell which exception it serves without reading the rest of the file.
Does the chapter treat older agreements differently?
Yes, in one narrow way. The chapter says a cause of action "may not be brought regarding a noncompetition covenant signed prior to January 1, 2020, if the noncompetition covenant is not being enforced or explicitly leveraged." ( Chapter 49.62 RCW)
The rule limits when a claim can be brought. It applies only to covenants signed before January 1, 2020, and only when the covenant is not being enforced or explicitly leveraged. The quoted text does not say what happens to an older covenant that an employer is enforcing or leveraging, so do not read it as a safe harbor for older language. It also does not reach covenants signed on or after that date.
For a hiring team, the practical lesson is about reused documents. Clauses get copied forward for years, and the copy in a new offer is a new document with a new signing date. Ask the document's owner three questions: when was the clause first used, has anyone enforced it, and does the company rely on it in any way? If you cannot answer those questions, treat the clause as new.
What should an offer letter say about restrictive terms?
An offer letter should state each restriction in plain language and tie each outside-work limit to a reason the chapter's text recognizes. Keep it short enough to read in one sitting, and do not bury restrictions inside a general policy reference. A hire who signs a letter should be able to see what they agreed to without hunting through a handbook.
Consider two versions of the same idea. The first says the hire may not work for anyone else. The second says the hire may not accept shifts from another employer that overlap the hours they are scheduled to work for you, and it explains that the overlap is the reason. The second version names a scheduling concern, ties it to defined hours, and leaves the rest of the hire's life alone. It is also far easier to explain to a reviewer, a hire, or a judge.
Before the letter goes out, run each restriction against the sections above and write a short note in the file explaining why it is there ( Hiring Decision Debrief: Notes to a Recorded Decision). If the note is hard to write, the restriction probably should not be in the letter.
How should onboarding agreements handle restrictive covenants?
Onboarding agreements should be reviewed as their own documents, because they often repeat or expand what the offer letter says. A hire may sign both during the same week, so any conflict between them will be easy to find later. Review the packet as a comparison: list every restrictive term in the offer letter, the onboarding agreement, the handbook, and any side letter, and check each one against the chapter.
Duplicate clauses that say different things create confusion about which version controls. When two documents conflict, a worker, a lawyer, or a judge has to decide which one counts. A team that never planned for that question will have a hard time answering it after the fact.
Keep the facts the chapter depends on in the signed file: the hire's pay rate, the date each document was signed, and the schedule the job requires. Without those facts, you cannot tell whether the outside-work protection applies. It is much easier to collect them at onboarding than to reconstruct them during a dispute.
Onboarding is also the moment when a hire asks questions. Answer them with the written terms in front of you, and if a question touches a restriction, route it to the reviewer instead of answering from memory.
What should you do if a worker already signed a restrictive clause?
Stop and get a lawyer's review before you mention the clause to the worker or take any step to enforce it. Telling a worker that a clause is binding, or threatening enforcement, can start a dispute your team did not plan for, and it can make the facts harder to sort out later.
Gather the record before anyone talks to the worker. Collect the signed document and the date it was signed, the worker's pay at the time, the schedule the job required, and any record of the company enforcing the clause or relying on it. The older-agreement rule turns on whether a covenant is being enforced or explicitly leveraged, so the enforcement history is one of the most important facts in the file.
Do not edit or replace a signed document without counsel. A changed record can complicate the review, and a new version presented as the original can create problems of its own.
When you talk to the worker, keep to facts. Explain that the company is reviewing its documents, ask what the worker wants to share, and avoid stating conclusions about whether the clause can be enforced. Those conclusions belong to counsel, and a manager who offers them informally may have to walk them back later.
What should a small staffing team check before sending an offer?
Run a short written review before every offer, and keep the review in the hire's file. Start by checking whether the document includes a noncompetition covenant at all. If it does, have a Washington employment lawyer read that clause against the chapter before the offer goes out, because the penalty applies to any covenant a court or arbitrator finds violates the chapter. For related reading, see Confirm requirements for enforceable non-competes.
Then check these points:
- Does any clause restrict outside work? If so, is the restriction tied to the exception's specific reasons, and has the hire's pay been checked against the threshold the chapter describes?
- Does the clause depend on a judge narrowing it later? If yes, rewrite it now or remove it.
- Was any language copied from an older document? If so, confirm when it was first used, whether it has been enforced, and whether the company relies on it.
- Do managers and recruiters know the penalty and the fee rule? A recruiter who calls a clause routine can create expectations the document does not support.
The last check is about people as much as paper. A recruiter who describes a restriction as standard, or who tells a hire that it never gets enforced, has made a statement that may outlast the offer. Keep spoken explanations consistent with the written terms.
Put a review date on standard documents as well. Revisit them on a fixed schedule, and again whenever your pay structure changes or a hire's role shifts in a way that affects outside work. A document that was right for one role can be wrong for the next.
Next step: before sending any offer, write one sentence for the file explaining why each restriction is in the document. If you cannot write that sentence, the restriction is not ready. A restriction that is not worth defending is worth removing before it reaches a hire.
Related guides: Draft 8 noncompete legal terms for exempt job roles · Iowa W-4 onboarding: 4 checks for hiring teams.
Frequently asked questions
Is an unused noncompete clause safe?
Not on its own, because the penalty follows a court or arbitrator's finding rather than a clause sitting in a file.
Does the older-agreement rule cover every existing clause?
No, because the rule is narrow and does not reach covenants signed on or after January 1, 2020.
General information, not legal or tax advice.