Direct answer
For most private California skilled nursing facilities, Labor Code 2810.5 requires a written wage-theft prevention notice for covered new hires at hire and no later than the first day worked, with covered changes updated within seven calendar days. ePeople helps SNF operators route the right notice, language, and proof steps, but the governing rule comes from current DLSE guidance and.
Key takeaways
- Private California SNFs generally must give covered new hires a Labor Code 2810.5 notice at hire and by the first day worked.
- The current official DLSE notice on the agency site is DLSE-NTE rev. 11/2023, and DIR says the notice was updated for the January 1, 2024 paid-sick-leave expansion.
- Post-hire changes to covered notice information usually must be given in writing within seven calendar days, unless the change appears on a timely wage statement or another legally required writing within that same period.
- The notice rule does not apply to public employees, overtime-exempt employees, or employees covered by a qualifying CBA that meets all stated conditions, including a regular hourly rate at least 30% above the state minimum wage.
- Employee acknowledgment is optional, but operators should still retain the notice, delivery proof, and any refusal-to-sign notation because DLSE may later request the notice in a wage claim.
California’s wage-theft prevention notice rule is easy to underestimate in a skilled nursing onboarding packet because it looks like one more intake form. In practice, it sits at the intersection of hiring, payroll setup, local wage-rate entry, workers’ compensation information, paid sick leave settings, and language access. When those teams do not use the same source of truth, the facility does not just risk a messy personnel file. It risks an onboarding document that conflicts with the pay stub, the handbook, or the actual rate loaded into payroll.
For private skilled nursing employers, the operational question is narrower than “Do we have the form?” The real question is whether the right covered employees received the current notice, in the right language workflow, by the right deadline, with a process for covered changes after hire. The DLSE FAQ on Notice to Employee, the current DLSE-NTE notice form, Wage Order 5, and DLSE’s wage-claim procedures are enough to build that workflow for California SNFs.
Which skilled nursing employees have to receive the Labor Code 2810.5 notice?
For a private California SNF, the starting point is broad coverage: DLSE says all private-sector employers are covered unless a specified exception applies. Skilled nursing facilities fall within Wage Order 5’s health care industry framework, so most nonexempt new hires should be treated as covered unless you have confirmed an exception for that employee or bargaining unit. In day-to-day operations, that means the notice usually belongs in the same new-hire workflow as rate setup, payday confirmation, workers’ compensation information, and paid sick leave configuration.
Who is carved out of the notice rule?
The main carve-outs are specific, and operators should use them carefully. DLSE says the notice is not required for employees directly employed by the state or a political subdivision, for overtime-exempt employees, and for employees covered by a qualifying collective bargaining agreement. That union exception is not automatic just because a facility is unionized. The CBA must expressly cover wages, hours, and working conditions, provide overtime premiums, and pay a regular hourly rate at least 30% above the state minimum wage. If one of those elements is missing, operators should not assume the notice is excused.
California SNF Labor Code 2810.5 workflow checkpoints
| Workflow question | Operator rule | Proof to retain |
|---|---|---|
| Is the facility a private California SNF? | Usually yes, the notice rule applies unless a specific exception fits the employee. | Facility onboarding standard and current notice template version. |
| Is the employee covered or exempt? | Most nonexempt hires are covered; confirm before skipping the notice. | Classification review and any exemption basis used. |
| Is there a union exception? | Use the carve-out only if the CBA meets every listed condition, including the 30% wage threshold. | CBA section, wage schedule, and basis for the exception decision. |
| When must the notice go out? | At hire and no later than the first day worked. | Timestamped delivery record or signed/acknowledged copy. |
| What if notice information changes later? | Update in writing within 7 calendar days unless a timely wage statement or another legally required writing covers the change. | Updated notice, pay-stub proof, or alternate legally required writing. |
| Does the employee have to sign? | No. Acknowledgment is optional, but the employer should still document delivery and any refusal to sign. | Employer copy with signature, electronic acknowledgment, or refusal notation. |
When does a California SNF have to give the notice?
The notice belongs at the front of onboarding, not after orientation cleanup. DLSE’s guidance says the notice must be provided at the time of hiring, and no later than the employee’s start date or first day providing services. For operators, that means you should not wait for the first closed payroll, badge issue, or department orientation to finalize it. If the employee is beginning work, the notice should already be complete enough to match the terms under which that employee is actually starting.
What version of the form should operators use now?
As of October 21, 2026, the current official form posted by DLSE is Notice to Employee, Labor Code section 2810.5, DLSE-NTE rev. 11/2023. DIR also states on its paid sick leave update page that the 2810.5 notice was updated for the January 1, 2024 paid-sick-leave expansion. That matters for SNFs because legacy onboarding packets often survive longer than they should. If a facility is still circulating an older pre-2024 version, the issue is not cosmetic. The template itself changed to reflect current notice content.
What information has to appear on the notice?
The safest approach is simple: use the current DLSE template or make sure your custom form contains all of the same required content. The current notice captures core employer identification details, rate or rates of pay, overtime rate information, regular payday, workers’ compensation carrier information, paid sick leave information, and emergency or disaster disclosure fields. In a skilled nursing setting, those fields often pull from different owners: HR enters employee and employer data, payroll enters rate logic, risk or administration owns workers’ compensation details, and policy owners control paid sick leave settings.
- Employee name and core identifying information.
- Employer name, including any doing-business-as name used operationally.
- Physical address, mailing address if different, and telephone number.
- Rate or rates of pay, including overtime rate information.
- The regular payday.
- Workers’ compensation carrier details or self-insurance information.
- Paid sick leave status under the current notice format.
- Emergency or disaster disclosure items included on the current DLSE template.
What should a skilled nursing facility do when an employee has multiple pay rates?
This is where many SNFs create avoidable mismatch risk. DLSE says employers must put all applicable rates on the notice if those rates are known or determinable at the time the notice is provided. A separate attachment is acceptable. That matters for facilities using shift differentials, weekend rates, lead assignments, or other multiple-rate structures. If a nurse aide can start on a base rate, weekend differential, and lead differential, the onboarding notice should not pretend there is only one number. The notice should reflect the actual pay structure the facility already knows it will use.
Does every pay-rate change require a new notice?
Not always. DLSE’s rule is event-driven, but it also allows alternatives. Covered changes generally must be provided in writing within seven calendar days. However, if all of the changed information is reflected on a timely Labor Code section 226 wage statement, or in another writing required by law within seven days, a separate replacement notice is not required. DLSE specifically says a pay increase does not require a separate new notice if the only change is the wage rate and the new rate appears on the pay stub. That exception is useful, but operators should apply it only when the pay-stub route fully fits the facts.
What changes trigger the 7-day update window after hire?
Think of the 7-day window as a change-control rule for the information stated on the notice. If the rate setup, payday details, employer identity fields, or other covered notice information changes, the facility needs a written update path that lands within seven calendar days unless one of DLSE’s substitute-writing routes applies. For multi-site operators, that means a central policy is not enough. The team changing a payroll field must know whether that same field also lives on the employee’s original 2810.5 notice and whether the next timely wage statement will fully cover the update.
How should multi-building operators handle local wage-rate differences on the notice?
The statewide rule does not change by city, but the actual rate or rates listed on the notice still must match what applies at that building or campus. That matters for operators with facilities in places where local wage rules or site-specific pay practices push the listed rate above a statewide baseline. The clean workflow is not to publish one generic sample rate for every California site. It is to make sure the notice lists the actual applicable rate or rates for that employee at that location, including any higher local rate the facility is using.
Does workers’ compensation information require a full replacement notice when it changes?
Not necessarily. DLSE says that a workers’ compensation policy-number change can be handled through the required workers’ compensation posting rather than by issuing a full new notice to every employee. This is helpful for SNFs that renew or change carrier information across several buildings at once. The operational point is not that workers’ compensation data can be ignored. It is that the facility should use one of the legally recognized written methods and retain proof of which method it used, instead of assuming a carrier change automatically means a full onboarding document must be regenerated for every worker.
What language and electronic-delivery rules matter in SNF onboarding?
DLSE’s guidance is clear on two practical points. First, the notice must be given in the language the employer normally uses to communicate employment-related information to the employee. Second, electronic delivery is allowed only if the system lets the employee acknowledge receipt and print a copy. DLSE also says the notice must stand on its own form even if it is delivered with other hiring documents. For skilled nursing operators, that means a translated handbook, a bundled onboarding packet, or a portal upload does not fix a notice workflow that hides the form or makes it impossible for the worker to retain a printable copy.
The 2810.5 notice is not just a document-generation task. In an SNF, it is a coordination task across HR, payroll, scheduling, and local wage-rate ownership.
Does the employee have to sign the notice?
No. DLSE says the acknowledgment section on the current form is optional, and an employee signature only confirms receipt. The notice is not invalid just because the worker refuses to sign. But operators should not read “optional” as “skip proof.” DLSE advises employers to provide the notice anyway, note the refusal on the employer’s copy, and retain records showing the notice was given. In a later dispute, being able to produce the notice, the delivery record, and any refusal notation is usually more useful than arguing about whether the employee should have signed.
Does California require SNFs to reissue the notice every year?
No statewide annual reissuance rule appears in DLSE’s official guidance for Labor Code 2810.5. California’s framework is change-based, not annual. That is a useful distinction for operators who manage buildings in several states and may be used to annual notice habits elsewhere. Still, “not annual” does not mean “set it and forget it.” If a facility updates a covered field, changes payroll logic, changes employer information, or swaps out an outdated template, the issue comes back immediately. ePeople is most useful here when it flags the operational event that should trigger the notice review, rather than treating the notice as a once-a-year compliance chore.
What proof should a skilled nursing operator keep in case of a wage claim?
DLSE says employers should keep records of the notices they provide, and the agency’s Policies and Procedures for Wage Claim Processing specifically lists the 2810.5 notice among documents that may matter in a wage claim. In practice, a defensible SNF file usually includes the actual notice version used, the delivery date, language used, any electronic acknowledgment or signature, any refusal-to-sign note, and the related payroll or legally required writing used to support a later change. If the facility relies on a pay stub to satisfy a rate-increase update, retain the pay-stub proof and the decision logic showing why that route applied.
Where does ePeople fit without acting like legal counsel?
ePeople fits at the workflow layer, not as a substitute for legal judgment. The product value is in surfacing when a hire is covered, routing the current template, matching the notice to actual payroll setup, preserving delivery proof, and catching when a later change should trigger a notice review. For California SNFs, that is useful because the compliance failure usually starts as an operational mismatch long before it becomes a legal argument. The governing rule still comes from DLSE and California law; ePeople helps the building follow the rule consistently.
