Direct answer
For California skilled nursing employers, Elections Code sections 14000 and 14001 require voting leave only for statewide elections and only when an employee lacks enough non-work time to vote. Up to two hours must be paid, the leave normally belongs at the start or end of the shift, and ePeople can route the request into scheduling and payroll before the.
Key takeaways
- California’s voting-leave rule is tied to statewide elections, not every local-only ballot.
- The leave is not automatic for every employee; it applies when the worker lacks sufficient time outside working hours to vote.
- No more than two hours of qualifying voting leave must be paid, even if the employer allows more total time off.
- Unless both sides agree otherwise, the leave should be placed at the beginning or end of the shift to create the most voting time with the least time away from work.
- If the employee knows by the third working day before the election that leave will be needed, at least two working days’ notice is required.
Voting leave looks simple until it lands on a 12-hour schedule the week before an election. In a skilled nursing facility, the operational risk is usually not the rule itself. It is the handoff failure between HR, the scheduler, payroll, and the unit manager. A request gets treated like a personal favor instead of a statutory workflow, the employee is told to “just vote by mail,” or a manager moves the time into the middle of the shift even though the statute points to the beginning or end unless both sides agree otherwise. For California operators, the safer approach is to treat voting leave the same way you would treat any other narrow labor-law obligation: confirm scope, document the trigger, place the time correctly, and keep proof that the facility posted the notice on time.
When does a California SNF have to provide time off to vote?
A California SNF has to provide time off to vote when an employee is voting in a statewide election and does not have sufficient time outside working hours to vote. That is the core rule in Elections Code section 14000. For this article, that matters now because California’s Secretary of State lists a statewide General Election on November 3, 2026. The operator takeaway is narrow: do not treat voting leave as a blanket benefit for every election, but do not ignore it when a statewide election is approaching either.
Does this rule apply to every election on the calendar?
No. The sources opened for this post support statewide-election scope, not every local-only election. That distinction matters for multi-site operators that use one statewide HR checklist. If your building leaders hear “Election Day” and assume the same workflow always applies, they can over-approve or under-handle requests. Keep the rule tied to the statute’s wording: statewide elections. That is also how the California Secretary of State frames the employer notice. If you are building a compliance checklist in ePeople or another workflow tool, the trigger should be statewide election dates, not every county or city contest.
Is paid voting leave automatic for every employee who asks?
No. The employee must lack sufficient time outside working hours to vote. That is the threshold managers need to understand. California also gives voters several ways to vote, including vote-by-mail and early-voting options for many voters, but those options do not erase the statute. They simply mean the factual need for leave may be narrower than staff assume. The wrong move for a SNF supervisor is either extreme: denying every request because “everyone got a ballot” or approving every request without checking whether the employee actually lacks enough non-work time.
How much of the time off has to be paid?
No more than two hours of qualifying voting leave must be paid. That is a cap on the paid portion, not a ban on allowing more total time away if that is what the facts require. In practice, payroll should be set up to distinguish three things: a qualifying request, the paid portion up to two hours, and any additional unpaid time the facility agrees is necessary. That keeps the pay treatment clean and reduces the chance that a scheduler, timekeeper, or payroll clerk later guesses what happened from a hand-marked timesheet.
Where in the shift should the leave be placed?
By default, the leave belongs at the beginning or end of the regular working shift, whichever gives the employee the most free time to vote and causes the least time away from work. A different placement is allowed only if the employer and employee mutually agree to it. For a SNF, this is the part that most often becomes a staffing problem. Mid-shift absences can create med-pass compression, break-coverage confusion, and weak handoff documentation. A beginning-or-end placement rule is easier to schedule, easier to audit, and closer to the statute.
California voting-leave workflow for skilled nursing employers before a statewide election
| Workflow question | What the statute or guidance supports | SNF operator action |
|---|---|---|
| Is this a statewide election? | Sections 14000-14001 and Secretary of State guidance are framed around statewide elections. | Trigger the workflow only for statewide elections; do not assume the same rule automatically governs local-only ballots. |
| Does the employee lack sufficient non-work time to vote? | Leave applies when the employee does not have sufficient time outside working hours to vote. | Require the manager or HR reviewer to document why the request qualifies instead of treating every request as automatic. |
| How much must be paid? | Up to two hours of qualifying leave is paid. | Code payroll so the paid portion is capped correctly and any additional time is tracked separately. |
| Where should the time sit? | Beginning or end of shift unless both sides agree otherwise. | Default to edge-of-shift placement so the unit is not hit by an avoidable mid-shift gap. |
| What notice can the facility require? | If the employee knows by the third working day before the election that leave will be needed, at least two working days’ notice is required. | Use a simple request step with date, shift, and manager acknowledgment rather than informal texts. |
| What must be posted? | A voting-leave notice must be posted conspicuously at least 10 days before every statewide election. | Post the notice in a visible employee area and retain proof of posting date and location. |
How much notice can a SNF require from the employee?
If the employee knows, on the third working day before the election, or has reason to believe that time off will be necessary, the employee must give at least two working days’ notice. That is a narrower rule than a blanket “always give two days’ notice” script. For operators, the practical answer is to standardize the request channel anyway. A simple internal form or workflow step should capture the election date, the scheduled shift, when the employee gave notice, and who approved the final placement. That same discipline already helps on other California leave issues such as jury duty and subpoena leave and school-appearance leave.
What does the facility have to post, and when?
Every employer must conspicuously post a notice setting out section 14000 at least 10 days before every statewide election. The Secretary of State says the notice should be posted in the workplace or where employees can see it as they enter or exit. The California Department of Industrial Relations workplace-postings matrix also lists this notice as applying to all employers. For a SNF, that means posting should not depend on headcount, union status, or whether leadership thinks only a few employees may ask for the leave. Put the poster workflow on the same calendar you use for other recurring California labor postings and policy tasks, including items surfaced in your labor-law compliance workflow.
What should schedulers, HR, and payroll each do with a request?
The cleanest workflow is role-based. HR or the labor-law owner confirms the request fits the statewide-election rule and that the notice timing is documented. The scheduler places the leave at the start or end of the shift unless there is a mutual alternative arrangement. Payroll applies the paid-time cap correctly. The unit manager should not be left to improvise the rule from memory. In skilled nursing, the same person may wear two or three of those hats, which is exactly why the handoff still needs a defined sequence. ePeople is most useful here when it surfaces the request early enough for schedule changes before payroll and staffing problems collide.
How should a SNF handle employees who already have vote-by-mail or early-voting options?
Treat those options as context, not as an automatic denial script. The Secretary of State’s current election pages explain that ballots will be mailed and that early-voting options exist, but section 14000 still remains in force for workers who do not have sufficient time outside working hours to vote. In other words, the existence of mail voting does not repeal the leave rule. It may reduce the number of employees who actually need paid leave on Election Day, but the facility still needs a process for the employees who do qualify. That is the same operator discipline behind meal-break compliance: do not replace a legal rule with an assumption that the employee could have solved it some other way.
What records should the facility keep if it grants or denies a request?
This dossier did not resolve a specific enforcement path for sections 14000-14001, so the safest drafting choice is not to overstate penalties or remedies. What operators can control is the evidence trail. Keep the posted notice, the posting date and location, the employee’s request timing, the scheduled shift, the final placement of the leave, any mutual agreement to place it somewhere other than the start or end of the shift, and the payroll treatment. That recordkeeping logic mirrors other California workflow-heavy rules such as paid sick leave and final pay: if a manager handled a labor-law event, the building should be able to prove how and when.
What is the safest workflow before the November 3, 2026 general election?
Use a short pre-election checklist. First, confirm that the election is statewide. Second, post the notice at least 10 days before the election in a place employees can actually see. Third, remind managers that the leave is not universal; it turns on insufficient non-work time. Fourth, route any request through one approval path instead of letting department heads make isolated calls. Fifth, place approved leave at the beginning or end of the shift unless both sides agree otherwise. Sixth, make payroll apply the two-hour paid cap correctly. That is enough structure for most buildings without turning a narrow election rule into a full policy rewrite.
- Calendar the statewide election and the poster deadline as separate compliance tasks.
- Download the current Secretary of State notice instead of reusing an old election-year version without checking it.
- Train staffing coordinators and unit managers on the edge-of-shift rule so they do not create unnecessary mid-shift gaps.
- Use one request path for voting leave rather than text-message approvals.
- Store the request, schedule change, and payroll treatment together for later audit or dispute review.
Where does ePeople fit in this workflow without turning it into legal advice?
ePeople’s role is operational, not legal-counsel posture. In this workflow, the product value is that a narrow labor-law rule can be turned into a consistent request-and-routing sequence across buildings: identify the statewide-election event, capture the request, push the scheduler toward start-or-end placement, and make payroll see the paid-time cap before the check closes. That is the same pattern behind this labor-law cluster’s other posts on reporting time pay and overtime control: fewer ad hoc decisions, clearer proof, and less shift-level confusion.
