Skip across the chapter
Quota Playbook

State pay rules: 3 date checks before you cite

Quota Playbook Editorial Team · Published · 11 min read

Before citing a state pay rule, check its effective date, the website's update timing, and which version applies to the pay period or claim.

Key takeaways

  • Define the employee group, work location, pay period, and decision before researching.
  • Preserve the relevant text, its URL, and the date you checked it.
  • Ask HR or counsel to resolve conflicting dates before relying on a rule.

Why dates matter as much as wording

A sales manager who needs to explain a pay or overtime rule usually has a page open, a sentence ready to paste into a coaching note, and a seller waiting for an answer. The wording on the page feels like the answer. Often it is only part of it. A rule can take effect on a specific date, a website can lag behind the law it prints, and one official document can contain sections that were changed at different times under different authority.

None of this means you should stop citing rules. This post walks through each check using official pages. It is practical guidance for writing clearer notes, not legal advice. If an answer could change what a seller is paid, bring in HR or counsel before you commit to it.

The cost of getting it wrong is not abstract. A seller who hears that a rule applies, and then learns it applied on a different date or to a different group, may stop trusting the rest of your coaching. Worse, a note that a manager wrote from memory can end up in a file that someone else relies on later. Checking dates takes a few minutes. Correcting a wrong answer after a seller has acted on it takes much longer.

Before you check: pin down the question

Clarify the question before checking dates. "What does the state say about overtime?" has no answer until you know more. Write the question in specific terms first: which employee or group, which work location, which pay period, and what decision the answer will support. Those four facts tell you which provisions to look at and which dates to compare.

The state where a seller works is a fact to confirm from employment records, not something to assume. If the record is unclear, that uncertainty belongs in your note. For related preparation, use the guide to work-hour rules before coaching.

Check 1: when did the rule take effect?

Start with the effective date written into the provision itself. Some provisions begin on a specific day; check their applicability language separately to determine which periods or claims they cover.

Washington's wage statute shows how this works. In RCW 49.46.130, subsection (6)(a) reads: "Beginning January 1, 2022, any agricultural employee shall not be employed for more than 55 hours in any one workweek unless the agricultural employee receives one and one-half times that agricultural employee's regular rate of pay for all hours worked over 55 in any one workweek."

Two things follow. The start date is part of the rule, so a note that says "Washington requires" with no date is incomplete. And the provision names a specific group, agricultural employees. Before you cite it, check whether anyone in your coaching note belongs to that group. An accurate, effective rule can still have nothing to do with your team.

When you write the note, put the date right beside the rule. A sentence like "Under the provision that began January 1, 2022, agricultural employees..." is much harder to misread than a bare statement with no date attached.

Compare the start date with the pay period you are discussing, not with the day you are writing the note. A provision that began on a given date may not reach pay periods before it, depending on what the provision says. A note written today may be discussing a period that closed long ago. Put both dates in the note so the comparison is visible to the next reader.

A summary is not the provision. If you find a blog, training deck, or HR memo that states a date, trace it back to the official text and use the date from that text. If the summary and the official page disagree, flag the discrepancy and ask HR or counsel to confirm the applicable text before relying on either version.

Check 2: when was the online text last updated?

Official websites are the right place to start, but they do not always show the current law in the way you might assume. The Idaho Legislature's page for Section 45-608 states: "Idaho Statutes are updated to the website July 1 following the legislative session."

That sentence is useful well beyond Idaho. It tells you the site is refreshed on a set schedule tied to the legislative session, not whenever someone happens to edit it. If you check a page in the months after a session, the text you see may be an earlier version than the one that governs today. Before you cite any online text, look for a "last updated" note or a statement about update timing. If the site gives neither, say in your note that you checked the text on a specific date and that later changes may not appear.

Be ready for the site itself to be unavailable. The notice on the same RCW 49.46.130 page says: "The Legislature website will be intermittently unavailable from 7AM to 7PM, Saturday, October 24 for scheduled maintenance." A notice like that is easy to skip, but it matters when you plan to check a source on a deadline. If you cannot reach the official text, do not fill the gap with a copy from a search snippet or a third-party summary. Note that you could not confirm the text and check again later.

Keep a dated copy of what you read. A saved page with a visible date, or a note in your file preserving the relevant quoted text, URL, and day you checked, lets you show later what the text said when you relied on it. That matters if a seller or an auditor asks why you said what you said.

Check 3: which version applies to this claim or pay period?

Dates can point in two different directions: the day the work happened, and the day a dispute was brought. Washington's provision shows why you need to know which one controls. Subsection (6)(b) of RCW 49.46.130 states: "This subsection applies to all claims, causes of actions, and proceedings commenced on or after November 5, 2020, regardless of when the claim or cause of action arose."

Read that sentence closely. The date that matters is when a claim, cause of action, or proceeding was commenced. So if a seller asks about an older pay period, you cannot assume the newest text applies, and you cannot assume the older text does either. Look at which date the source names, then compare it with the dates you have.

Be careful with the word "commenced." In everyday speech people use "filed," "raised," and "started" to mean similar things, but the source you are quoting may use a term with a specific meaning. If you are not sure what a term means in the provision, say so and ask HR or counsel. Do not replace the source's word with your own.

California shows a related problem: one document, many dates. The Order Regulating Wages, Hours, and Working Conditions in Professional, Technical, Clerical, Mechanical, and Similar Occupations is published as California Code of Regulations, Title 8, Section 11040. The Department of Industrial Relations page includes notes under individual sections, and they do not all tell the same story:

  • Sections 4(A) and 10(C) were "amended and republished by the Department of Industrial Relations, effective January 1, 2025, pursuant to SB 3 (Chapter 4, Statutes of 2016), and section 1182.13 of the Labor Code."
  • Section 1(A) was "amended pursuant to section 515.5(a)(4) of the Labor Code."
  • Sections 2(C), 4(A), and 4(E) were "amended pursuant to SB 525" (check the full amendment note before quoting the citation).

Section 4(A) appears in two of these notes, under different authority. A single date for "Section 11040" would hide that. When you cite a section, use the note attached to that exact section, record the effective date the note gives, and leave out any date you cannot find there.

A routine for coaching notes

You do not need a legal research system to do this well. You need a consistent habit. For each rule you plan to cite, write down:

  1. The exact source name, section, and URL.
  2. The date you checked the text.
  3. The effective date the provision states, or a note that you could not find one.
  4. Any "last updated" statement on the site, or a note that none was given.
  5. The date of the pay period, claim, or dispute, and which date the source says controls.
  6. Whether the people involved fall within the group the provision names.

If the dates do not line up, or the sources disagree, stop and send the question to HR or counsel. Do not resolve the conflict in a coaching note.

Here is a sample you can adapt. "As of [date I checked], the [site name] text for [section] reads [short quote]. The provision states an effective date of [date]. The site says [its update statement, or 'no update statement']. This question involves a pay period in [month and year], so I have asked HR to confirm which version applies before we rely on it."

If you coach several managers, agree on one shared source list for your team. Name the official pages you use, and have one person check them on a set schedule, such as the first business day of each quarter. Each manager then starts from the same text and the same dates, instead of from whatever they remember or found last. Keep the list short. A long list that nobody checks is worse than a short one that is current.

Illustrative example: an earlier pay period

A seller asks whether an illustrative 50-hour workweek triggers overtime. The manager records the work location, employee group, and pay period, then checks the relevant provision's effective date and applicability language. The website's update timing leaves the applicable version unclear. The manager preserves the quoted text and sends HR the unresolved version question before promising any payment.

Who should confirm the answer

A sales manager is usually not the right person to make the final call on a pay question. HR usually owns the pay plan documents and knows which records are authoritative for your company. Counsel can read the provisions in full and can say whether a summary you found reflects current law. Bring them in early, while the question is still a question. The note you send them should show the sources, the dates you checked, and the specific question you cannot answer. That saves time for everyone and keeps the coaching conversation from getting ahead of the facts.

Related guides: Pump-break rules: 4 state lines to check before coaching · Call handling: 9 rules to check before coaching · Check 7 items before you pay commission by payroll card.

How to handle seller pay questions

Sellers rarely ask about statutes. They ask, "Does state law mean I get paid this?" or "Why did my commission land this way?" A state rule may be part of the answer, but it is seldom the whole answer. Pay plans are usually built from written terms, and those terms can interact with state rules in ways that depend on the facts of each case. For deduction questions, see the guide to sales paycheck deductions.

It also helps to separate two questions: what the rule says, and what this seller's plan provides. The first is a research question you can answer with sources. The second depends on the written plan and on facts about the seller's work. Answering the first does not answer the second. Say that out loud in the conversation, so the seller does not hear a statute as a promise.

So avoid answering with a rule as if it settles the matter. Say what you know, when you checked it, and who will confirm the rest. Do not promise an amount or a payment date you have not verified. If the seller's question touches on the group a provision covers, the timing of a claim, or a section that has been amended, that is a signal to route the question, not to answer it alone.

A short, plain script helps. For example: "Here is what the official text says as of the date I checked. I'm confirming how it applies to your plan with HR, and I'll follow up by [date]." That keeps you accurate without sounding evasive.

Common mistakes to avoid

  • Relying on a screenshot or saved PDF from an earlier year.
  • Citing a rule from another state because the subject sounds the same.
  • Treating a whole order or statute as having one date.
  • Using the date the work happened when the source points to a different date.
  • Copying a summary's date without checking the official text.
  • Writing an effective date you did not confirm on the source itself.
  • Assuming a website is current because it loads without errors.

A next step for today

Preserve the relevant text and mark any unresolved question for HR before using the note again.

Questions about date checks

Can a screenshot without a date or URL support my note?

A screenshot without a date or URL does not show when or where you checked the text. Keep that information with the relevant passage so another reader can trace your note.

Does checking a rule settle what a seller should receive?

Checking a rule alone does not settle what a seller should receive. The written plan and the facts about the seller's work also need review.

Sources

  1. Update team roles in 3 checks after the setup change
  2. Lost seller phone recovery: 4 steps for 2FA lockouts
  3. HubSpot quote checks: 5 limits to run before email
  4. Remote access rules: 3 checks before a rep gets IT help
  5. New seller pay first weeks

More plays