Skip forward into hiring notes
RosterAcorn

Sick leave time settings to check in 7 test steps

Check the waiting period, minimum increment, and carryover settings in your scheduling tool for hourly staff in Washington and Arizona. Sick leave is one place where a default setting can quietly break a state rule. Those defaults rarely match a state's sick-leave law.

Key takeaways

  • Confirm that Washington hours become usable within one month of accrual.
  • Match the sick-leave increment to your payroll increment, and keep it at one hour or less.
  • Set any carryover cap so Washington workers can always carry forward at least forty hours.
  • Write down Arizona's waiting-period choice and apply it the same way to every Arizona hire.

This post covers three settings that matter most. The first is when a new hire can start using accrued sick leave. The second is the smallest amount of time a person can request. The third is how much unused leave carries into the next year. After those, it covers two smaller checks: whether the tool deducts sick time on its own, and what happens to a balance when someone moves to another location.

Each section links the official text it relies on. Where that text does not settle a point, this post says so. In those cases the decision belongs to you, your written policy, and your employment counsel, not to a default in the software. Recruiters often inherit a setup someone else built, so read each setting as if you were explaining it to an auditor who has never seen the tool.

When can a new hire start using sick leave?

In Washington, an employee can use accrued, unused paid sick leave starting on the 90th calendar day after employment begins, under WAC 296-128-630. The count runs from the commencement of employment, so the hire date in your tool is the anchor for every sick-leave date that follows. Suppose a worker at a Spokane-area site starts on a weekday in early spring. If the tool counts from an offer date a few weeks earlier, it will unlock the balance too early, and nobody notices until a request is approved that should have been blocked. Check the field name in your tool, and confirm that it means the first day of employment. For a broader comparison, see sick time rules for new hires.

The same rule has a second part that people often miss. Starting on day 90, the employer must make accrued paid sick leave available "in a manner consistent with the employer's established payment interval or leave records management system, not to exceed one month after the date of accrual." In plain terms, once the wait is over, hours that have been earned must become usable within one month of when they accrue. The timing is measured against your own pay cycle or records system. A posting interval that stays within one month of accrual fits the rule. One that holds hours back for longer does not. Check the accrual posting setting in your tool, and confirm that the earliest sick-leave date a worker sees matches what the tool actually allows.

Arizona works differently. Under A.R.S. 23-372, an employee may use earned paid sick time as it is accrued. An employer may, however, require an employee hired after July 1, 2017, to wait until the 90th calendar day after commencing employment before using accrued earned paid sick time. The same sentence adds "unless otherwise permitted by the employer." That phrase makes the wait a choice rather than a fixed rule. You can keep the wait, or you can let Arizona hires use time earlier. Either way, the choice should be written down, applied the same way to every Arizona hire, and built into the tool as a setting rather than left to a recruiter's memory. The sentence covers employees hired after July 1, 2017.

A common setup problem is a single company-wide "PTO waiting period" that applies the same day count to both states. If the tool can set waiting periods by state or by work location, use that option. If it cannot, you need a workaround you can defend, such as a separate policy group for each state with its own waiting period. Test each group with a sample hire before go-live. If you let Arizona hires use time earlier, a Washington hire and an Arizona hire who start the same day will show different first-use dates. The tool should make that difference visible on screen, so a recruiter can see it without reading the configuration.

In what increments can staff take sick leave?

Washington sets a ceiling on the increment. WAC 296-128-630 says employers must allow staff to use paid sick leave "in increments consistent with the employer's payroll system and practices, not to exceed one hour," unless a greater increment is approved through a variance under WAC 296-128-640. The rule also gives an example. If your normal practice is to track work for pay in 15-minute increments, then you must allow sick leave in 15-minute increments. The logic is simple: the sick-leave increment should match the increment your payroll already uses, and it may not be larger than one hour unless a variance approves it.

For a scheduling or time-tracking tool, this is usually a setting on the leave type. Look for a minimum request size, a rounding rule, or a "partial day" option. Then compare it to the rounding you use for pay. If payroll pays by the quarter hour, a tool that only accepts one-hour or full-shift sick entries does not match payroll. A worker who needs only part of an hour would have to request a full hour, so the entry no longer matches the increment payroll uses. For more on the payroll side, read time clock setup before payroll export.

Rounding deserves its own test. If the tool rounds a short request up to the next full hour, the balance drops by more than the worker actually used. The rule may not address rounding in those words, but a wrong balance is hard to defend in a dispute. Enter a request with an odd number of minutes, not a whole hour, and confirm that the balance drops by the amount the worker took, measured in the increment your payroll uses. Keep in mind that a variance is an approval process the rule names. It is not a tool setting, so do not enter a larger increment and assume the tool's choice is permitted.

The Arizona text this post quotes sets no increment rule, so check the full statute before you choose an Arizona setting. A single approach that matches payroll is simpler to run across both states, and it keeps one payroll practice for everyone. Document it so that a future administrator can see why the Arizona setting is what it is.

How much sick leave carries into the next year?

In Washington, employers must let employees carry over at least forty hours of accrued, unused paid sick leave to the following year, according to WAC 296-128-620. The phrase "at least" sets a floor. Your tool may allow more carryover than that, but it may not allow less.

That affects the year-end setups most tools use. A reset that clears all balances at the close of the year does not fit the rule for Washington workers. Neither does a maximum-balance cap that trims carried hours below the floor. Consider a Washington worker who finishes the year with more than the floor in unused leave, in a tool that caps carryover below forty hours. The tool would carry less than the rule allows, and the cap is wrong. If your tool has a carryover cap, set it so that a Washington employee can always carry forward at least forty hours of unused leave. A cap on the total balance can be higher than that, but it must never push the carried amount below the floor.

Think about the sequence, too. A worker might earn leave all year, use some of it, and reach the year-end process with a balance above forty hours. Run that case in a test. Confirm that the tool carries the right number forward, and confirm that the carried amount appears on the new year's balance. Then keep a dated record of year-end balances for each Washington employee. What carried over is a natural first question in any dispute, and a dated record answers it faster than a reconstruction from memory.

Arizona is a separate question. Read the Arizona statute, your written policy, and your employment counsel's guidance before you set an Arizona carryover limit. Do not borrow the Washington forty-hour figure and assume it applies in Arizona.

Illustrative example: carryover check

A Washington employee ends the year with 50 hours of unused sick leave, but the tool caps carryover at 35 hours. That is below the forty-hour floor in WAC 296-128-620, so the cap is wrong. Raise it to 50 hours, or remove it for Washington staff, then rerun the year-end test and confirm that the full balance carries forward.

Should the tool deduct sick time on its own?

No, not in Washington. The rule treats sick leave as the employee's choice. WAC 296-128-630 says the right "means an employee has the choice about whether or not to use accrued, unused paid sick leave when a qualified purpose occurs," and that an employer "may not require an employee to use accrued, unused paid sick leave if the employee does not choose to request to use paid sick leave."

Why does this matter in a scheduling tool? That kind of automation is convenient for the manager and invisible to the worker. Under the Washington rule, it can cut against the worker's choice. Check the settings for each absence type, and look for any rule that posts a leave deduction when a shift is marked missed, marked as a no-show, or left unexcused. If you find one, turn it off for Washington workers, or set it to hold the absence open until the employee makes a request.

A practical test is simple. Mark a shift as an absence without any request from the worker, then see what the tool does to the sick-leave balance. If the balance changes, the employee did not make the choice, and that is the outcome this part of the rule addresses. Also check whether the worker can see the absence and request sick time from their own account, because a choice the worker cannot see is not much of a choice.

What happens to a balance when someone moves to another location?

In Arizona, the balance moves with the employee. A.R.S. 23-372 says that when an employee is transferred to a separate division, entity, or location but remains employed by the same employer, the employee is entitled to all earned paid sick time accrued at the prior division, entity, or location. The same section says the employee may use all of that time as the section provides.

This matters for tools that keep a separate leave bank for each location. If a transfer creates a new empty balance, or closes the old balance when the employee changes sites, the tool can erase time an Arizona employee has earned. Suppose a worker moves from one Arizona location to another location of the same company. If the tool opens a new site balance at zero, the worker appears to have no sick time at the new site, even though the statute says the employee keeps the time accrued at the prior location. Some scheduling systems are organized around sites rather than people, so this is a real risk to check.

Check how transfers are handled. Make a test transfer between two locations under the same legal employer, then confirm that the balance and the right to use it come with the employee. Pay attention to the phrase "same employer." If your locations are separate legal entities, the transfer language may not describe your situation. Ask counsel how the rule applies before you choose a transfer setting.

Write down how your policy handles a move between sites in Washington, and have that policy reviewed before you configure the tool. A transfer setting that works for Arizona may not be the right setting for Washington.

What should you ask your software vendor first?

Ask the vendor, in writing, how each setting in this post works before you rely on it. Help pages describe what a feature is meant to do, while a written answer tells you what the configuration will actually do. Start with the waiting period. Ask whether the tool can set a different waiting period by state, by work location, or by policy group, and whether it counts from the employment start date or from another field.

Then ask how the tool posts accrued hours, and whether the posting interval can be set so that Washington hours become usable within one month of accrual, as WAC 296-128-630 requires. For increments, ask for the smallest request size the leave type accepts, how rounding works on partial entries, and whether that rounding can match payroll's own increment. For carryover, ask whether the year-end process can keep a floor, such as the forty hours that WAC 296-128-620 requires for Washington employees, and whether you can run a year-end test before the real one.

Finish with two questions that cover the smaller checks. Ask whether a transfer between locations keeps the balance with the employee under the same employer. Ask whether any absence type can post a sick-leave deduction without a request from the worker. File the written answers with your test log. If a vendor cannot answer a question in writing, treat that setting as unverified until you have tested it yourself, and do not assume the help page covers it.

How do you test these settings before go-live?

Set up a test hire in each state and run every setting with sample dates before any employee sees the tool. Screen labels and vendor help pages do not always match what the calculation does underneath.

Here is a sequence you can run in an afternoon:

  1. Enter a Washington test hire with a start date. Confirm that sick leave cannot be used until the 90th calendar day under WAC 296-128-630, and that it becomes usable on that day.
  2. Confirm that earned Washington hours become usable within one month of accrual, measured against your pay or records interval, under the same rule.
  3. Enter a sick-time request in the smallest increment your payroll uses, and confirm that the tool accepts it and deducts the right amount.
  4. Run a year-end test with a balance above forty hours, and confirm that at least forty hours carry forward, as WAC 296-128-620 requires.
  5. Enter an Arizona test hire and confirm that the waiting period matches the choice in your written policy, under A.R.S. 23-372.
  6. Transfer a test employee between two locations under the same employer, and confirm that the balance moves with them.
  7. Mark an absence without a sick-time request, and confirm that the tool does not convert it to sick leave.

Save the results. Keep the test log, a dated screenshot of each setting, and a sign-off from whoever approved the configuration. That record is what you will want if a worker or an auditor asks why a balance looks the way it does.

When a vendor's help page conflicts with a statute, follow the statute and ask the vendor to change the setting in writing. If a setting cannot do what the rule requires, treat that as an open question for the vendor and your counsel before launch. Do not run a workaround on live staff while you wait for an answer.

Your next step today: open the sick-leave settings in your scheduling tool and write down the waiting period, minimum increment, and carryover setting for each state. Compare them with the rules above before you change anything.

Frequently asked questions

Can a Washington employee use sick leave on the first day?

No, use begins on the 90th calendar day after employment begins, so the hire date in your tool is the anchor for that count.

Does Arizona have to make new hires wait 90 days?

No, the wait is optional: an employer may require it for employees hired after July 1, 2017, unless the employer permits earlier use.

Sources