Washington's farm overtime statute has two provisions that decide who counts as a dairy employee and how far back unpaid-overtime relief can reach. Both live in RCW 49.46.130, and both should be built into your placement workflow.
Key takeaways
- The dairy employee definition is activity-based, anchored to NAICS code 112120, not job titles or property lines.
- The claim-limit subsection bars damages, penalties, attorneys' fees, and costs for overtime tied to the historical exclusion as it existed on November 4, 2020.
- The bar covers money and relief, not the underlying hours.
- The subsection protects "an employer," so confirm who the employer of record is on each placement.
- Close calls on classification need a written answer from a qualified source, not a guess.
What the two terms actually do
The first term is the definition of "dairy employee." The second is the look-back limit on what an employee can claim for hours worked before overtime coverage began for agricultural and dairy workers. Both live in the same section of the statute, RCW 49.46.130, from the Washington State Legislature.
If you staff workers onto Washington dairy or farm crews, these two terms shape what you promise in a timesheet, what you pay at the end of the week, and what a claim can reach if a worker believes hours went unpaid.
You do not need to memorize the statute. You need to know which workers fall inside the dairy definition, and which hours the law will not reach backward on. This guide walks both, then shows you what to put in your placement records. For the wider state picture, see State overtime rules from 4 pages before the offer.
Who counts as a dairy employee
The statute defines the term by pointing at a federal industry code. It says a dairy employee includes any employee engaged in dairy cattle and milk production activities described in code 112120 of the North American industry classification system. That is the definition in RCW 49.46.130.
Three pieces of that definition matter for your placement work.
The definition is activity-based, not job-title-based. A worker milking cows, handling milk, or caring for dairy cattle falls inside the definition, whatever the crew leader calls the role. A worker on the same ranch doing unrelated tasks does not fall inside it just because the ranch has a dairy herd.
The definition points to a code number, not a list of tasks. Code 112120 of the North American industry classification system is the anchor. When a role sits close to the line, that code is where you look.
The definition uses the word "includes." The statutory wording is "includes any employee engaged in dairy cattle and milk production activities described in code 112120." If your placement sits at the edge of the code's description, the safe move is to ask.
Because the statute ties the definition to an external code rather than to a task list you can read in one page, a close call on classification is not one to settle from a job description alone.
Here is why the classification question carries weight. Washington's agricultural sector is large and varied. The legislature's findings in this section note that over 300 crops are harvested, and a variety of livestock are raised, on over 35,000 farms across the state. The same findings add that the robust size of the agricultural sector puts the state in the top 10 nationally for the size of its farm labor force. Both figures appear in the findings accompanying RCW 49.46.130.
With that much work spread across that many operations, your placements will cross the dairy line often. Classify each role once, write down the basis, and reuse it.
The findings also explain why the legislature was watching farm pay at all. A United States department of labor study in 2016 found that nationally, 30 percent of farmworker families live below the poverty line, almost double the poverty rate of American families overall. That figure sits in the findings attached to the same section.
That context matters to you as a staffing reader. Your placement records are where the section's rules meet the ground.
The look-back limit on old claims
The second term is the limit on what a worker can recover for hours worked before overtime coverage applied to their role. The statute bars damages, statutory or civil penalties, attorneys' fees and costs, or other type of relief against an employer, for unpaid overtime an agricultural or dairy employee seeks because of their historical exclusion from overtime. The exclusion is measured as it existed on November 4, 2020. The full bar appears in subsection (7)(a) of RCW 49.46.130.
Read that carefully and the shape of it is simple.
The bar covers money and penalties, not the underlying hours. The statute lists damages, penalties, fees and costs, and other relief. It does not say the old hours vanish from a timesheet. It says no relief of those kinds may be granted against the employer for overtime tied to that historical exclusion.
The date is fixed. The exclusion is measured as it existed on November 4, 2020. Hours in scope of that exclusion are the hours this subsection addresses.
The bar names the employer as the party protected. Subsection (7)(a) bars relief "against an employer." If your firm is the employer of record on a placement, read this subsection with care before you assume it covers your entity.
What this means for your desk work: when a claim arrives, the first question is which hours it covers. Hours inside the historical exclusion get this treatment. Hours outside that exclusion are not covered by the bar, so they need their own analysis. Split the hours first, then look at the rest.
Do not treat the bar as a reason to be loose with records. The bar fixes a boundary on old claims. It says nothing about how you record and pay hours going forward.
A side-by-side view of the two terms
The table below pulls the operative facts from the two provisions, so you can scan the difference without rereading the statute.
| Term | What it defines | Where it appears |
|---|---|---|
| Dairy employee | Any employee engaged in dairy cattle and milk production activities described in code 112120 | RCW 49.46.130, subsection (9) |
| Historical-exclusion claim limit | No damages, penalties, fees, costs, or other relief for overtime tied to the historical exclusion as it existed on November 4, 2020 | RCW 49.46.130, subsection (7)(a) |
The first term answers "who." The second term answers "how far back." Both are narrow, and both are easy to apply once you write them into your placement workflow.
Where these terms sit in the wider statute
The two provisions live inside a section that carries findings and intent language alongside the operative rules. Reading that surrounding text once helps you place them correctly.
The findings describe the agricultural economy you staff into. Over 35,000 farms operate in the state, harvesting over 300 crops and raising a variety of livestock. The farm labor force ranks in the top 10 nationally. Those findings appear with the rest of RCW 49.46.130.
The same section carries a separate intent note tied to a 1995 act, which states that the act was intended to clarify the original intent of RCW 49.46.010(5)(c). That intent note is attached to the section and is separate from the two terms in this post, but it shows how the legislature layers interpretation notes into this statute. If you read the page end to end, expect that pattern.
For your purposes, the structure means one thing: the two terms you are working with are operative rules with clear anchors. They sit next to findings that explain why the rules exist. Use the operative text for decisions, and the findings for context when you brief a client or a crew leader.
How to apply the dairy definition on a live placement
Your workflow does not change much once the definition is in front of you. It gets one extra checkpoint at intake.
Step one: describe the work, not the title. At intake, write down what the worker will actually do on the crew. Milking, milk handling, and dairy cattle care point toward the definition. Other ranch tasks need a separate look.
Step two: match the description against code 112120. The North American industry classification system code the statute cites is your reference. If the work description lands squarely inside it, classify the placement as a dairy employee.
Step three: record the basis. Write one line in the placement file: the work description, the code reference, and the classification. That line is what you will read in six months when the same question comes back.
Step four: escalate the close calls. If the work sits at the edge of the code, do not guess. Take the question to a qualified source and get the answer in writing.
One placement, one classification, one written basis. Multiply that across a crew roster and you have a defensible record without any new software.
How to apply the claim limit when a dispute arrives
A worker or a client raises unpaid overtime. Your first move is to sort the hours.
Split the hours at the boundary. Separate hours that fall within the scope of the historical exclusion as it existed on November 4, 2020, from hours that fall outside it. The subsection (7)(a) bar speaks to the first group.
Read the bar for what it says and does not say. It bars damages, statutory or civil penalties, attorneys' fees and costs, and other type of relief against an employer for overtime tied to the historical exclusion. It does not resolve the second group of hours. Those get normal handling under this section.
Check who the employer is on the placement. The bar names the employer. If your firm is the employer of record, take the subsection to counsel before you rely on it in a reply. If the client is the employer, your role is to supply the hours records, and you should supply them promptly.
Keep the records that make the split possible. Timesheets, shift start and end, and duty descriptions. Without those, you cannot show which side of the boundary a given hour falls on.
Handled this way, the claim process gets shorter. The boundary question comes first, the money question second.
Illustrative example: splitting one claim
Suppose a claim seeks 30 hours of unpaid overtime across 2 pay periods, and the work description on file shows the worker was doing dairy cattle care for all of those hours. The first step is to sort the hours. Hours that fall within the historical exclusion as it existed on November 4, 2020 are the ones the subsection (7)(a) bar addresses. Any other hours need their own analysis. Write the split, the work description, and the classification basis into the placement file, so the next reviewer can follow the same path.
What goes into your placement record
Your placement file is where these two terms become practical. Build it once and it serves every future claim question.
- Work description: plain language, what the worker does each shift.
- Classification: dairy employee or not, with the code 112120 reference when it applies.
- Basis line: one sentence on how you reached that classification.
- Hours record: start and end times, kept so a later split by coverage period is possible. For the timekeeping side, see Time clock setup: 7 gaps to fix before payroll export.
- Employer of record: named clearly, because the claim-limit subsection references the employer.
- Escalation note: if the classification was a close call, note who you asked and what they said.
That list is short on purpose. Each item answers a question that will come up. None of it requires a new system.
Common mistakes staffing teams make
These errors show up often on Washington farm placements. Each one traces back to one of the two terms.
Classifying by job title. "General farmhand" tells you nothing about whether the worker engages in dairy cattle and milk production activities. Describe the work.
Treating the whole ranch as dairy work. A dairy operation runs non-dairy tasks too. The definition follows the activity, not the property.
Ignoring the boundary date. When an old-hours claim arrives, teams either skip the split or apply the bar to everything. Do neither. Split first.
Relying on the bar as a records shortcut. The bar addresses old claims. It does not reduce what you record now.
Leaving close calls unresolved. A guess today becomes a dispute later. Ask a qualified source when the code reference does not settle it.
Five habits, five fixes, all inside your existing intake and claims process. Your next step today: open one placement file and check that it holds a work description and a classification basis.
Related guides: Arizona knowingly employ rule: 3 defined terms to check · Job post break terms: 4 details to state clearly · Care worker background checks: 6 defined terms to read.
Questions staffing teams ask
Does a worker on a dairy ranch automatically count as a dairy employee? No. The definition follows the activity the worker performs, measured against code 112120 of the North American industry classification system. A worker on the same ranch doing other work needs its own classification.
What exactly does the claim-limit subsection prevent? It prevents damages, statutory or civil penalties, attorneys' fees and costs, and other type of relief against an employer, for unpaid overtime an agricultural or dairy employee seeks because of their historical exclusion from overtime under subsection (2)(g) as it existed on November 4, 2020. Hours outside that scope are not addressed by the bar.
Does the bar apply to my staffing firm? The subsection protects "an employer." Whether your firm is that employer on a given placement depends on your arrangement with the client. Check the contract, then take the question to counsel.
What should I do if the work description sits right on the edge of the dairy code? Ask a qualified source. Get the answer in writing and file it with the placement.
Where do the findings about farm families and farm labor fit into my day-to-day work? They do not change a rule you apply. They explain why the legislature wrote these rules. Use them when you brief a crew leader or a client on why classification and records matter.
Do I need to re-classify every placement I have already made? No, not as a separate project. Check existing files during routine file reviews instead.
Putting both terms to work
Two provisions carry a lot of your compliance weight on Washington dairy and farm placements. One tells you who falls inside the dairy definition, anchored to an industry code you can check. The other draws a line on how far back unpaid-overtime relief can reach for hours tied to the historical exclusion.
Apply both the same way every time. Describe the work before you classify it. Write down the basis. Split hours at the boundary when a claim arrives. Name the employer of record. Ask a qualified source when the code does not settle a close call.
Do that, and the statute stops being something you look up under pressure. It becomes two checkpoints already built into the way you take and file a placement.
General information, not legal or tax advice.