Straight into the service manual page
WrenchQuarry
More

Wisconsin paid time off and overtime: 2 answers

WrenchQuarry Editorial Team · Published · 11 min read · How these guides are written

The short answer

Wisconsin paid vacation, sick leave, and holiday pay do not have to count toward overtime, but employers may choose to count them.

Key takeaways

  • Check the written pay policy before calculating overtime.
  • Record worked hours separately from paid leave.
  • Review public works requirements before scheduling.
  • Confirm employee coverage before applying the rule.

Owners and dispatchers still have two questions to answer: what the state requires, and what your own policies and contracts add on top of it. This post covers both, with examples and a checklist you can use before the next pay period.

Why this question keeps coming up

Dispatchers see it every week. A tech works a full schedule, takes a paid day later in the same week, and then asks whether that day counts toward overtime. An owner hears the same question from the other side when payroll comes out lower than the tech expected. Both reactions are understandable. A paid day feels like time at work, because the tech is paid for it and planned around it. The overtime question, though, asks about hours worked, and those two ideas are not always the same.

This is where most of the confusion starts. Pay and work are related, but the overtime calculation looks at a narrower thing. Owners who explain the difference clearly tend to avoid the argument.

Answer 1: state guidance does not require paid leave to count as worked time

The Wisconsin Department of Workforce Development (DWD) answers this question on its page about hours of work and overtime. The page asks, "Does vacation time or sick leave count toward overtime hours?" Its answer is direct: "Hours paid for time not worked, such as sick leave, vacation pay, or holiday pay, do NOT have to count as hours worked for purposes of computing overtime pay."

Three phrases in that answer do most of the work.

The first is "time not worked." Sick leave, vacation pay, and holiday pay all cover hours when the employee was away from the job. The page names those three types as examples. The rule is about hours that were not worked, not about the total amount on the paycheck.

The second is "do NOT have to count." The guidance does not say that paid leave is worked time, and it does not say the employer must ignore paid leave in every calculation. It says the state does not require those paid hours to be added to the hours worked when overtime is computed.

The third is "for purposes of computing overtime pay." The sentence limits itself to overtime. It is not a general statement about how every benefit, deduction, or pay item must be handled. A paid day can still matter for other purposes, such as how the company tracks leave balances, so keep the overtime question separate from the others.

It helps to walk through what the rule means in an ordinary week:

  • A tech works the full week and takes a paid vacation day on Friday. The Friday pay is for time not worked. Under the state guidance, that paid day does not have to be added to the hours worked. The overtime question depends on the hours the tech actually worked that week and any paid leave the employer chooses to count.
  • A tech works the full week and is paid for a holiday that falls on a weekday when the shop is closed. The holiday pay is for time not worked, so it does not have to count as hours worked.
  • A tech works on a holiday itself. The hours actually worked count. Check your policy on any extra holiday pay for that day, because the state guidance is about pay for time not worked.
  • A tech takes a sick day early in a heavy week and works extra hours later. The sick day is paid time not worked. Under the state guidance, it does not have to count toward the hours the tech worked to earn overtime.

Answer 2: your own policy can count paid leave

The same DWD page includes a second sentence that matters just as much: "Of course employers may be more generous than the law requires should they wish." This is the second answer to the question in the title. The state rule is a minimum. It is not a ceiling. An employer can decide to count paid vacation, paid sick leave, or paid holiday pay toward overtime, and that choice belongs to the employer.

Some employers make that choice for reasons of fairness or retention. A tech who feels penalized for taking a sick day may start looking elsewhere, and a shop that wants to keep experienced techs may decide paid leave should count. The state guidance does not ask for that choice, but it does not forbid it either.

Whatever you decide, put it in writing. A written policy protects both the owner and the tech. A tech who expects paid leave to count will be upset if payroll does not count it, and a dispatcher who plans a week without knowing the policy can be caught off guard when the pay period closes. A short policy statement that says exactly how each type of paid leave is handled removes most of the guesswork. If the policy changes, tell the techs before the change takes effect, not after the first affected pay period.

Public works projects can add requirements

The DWD page also includes a sentence about a different kind of requirement: "Some public works construction projects require daily overtime and overtime on certain holidays." Two things stand out. First, the word is "some," not "all." A public works job is not automatically subject to daily or holiday overtime. The requirement depends on the project. Second, the requirement goes beyond the general rule on paid leave. Daily overtime and overtime on certain holidays are separate triggers, and the general rule does not address them.

For a shop that takes public construction work, this means the contract is the first document to read, not the last. Look for language on daily overtime and on holidays. If the contract says overtime applies in a situation your scheduling assumes it does not, the schedule has to change, or payroll has to follow the contract. Ask the project manager or the company's contract administrator to point out the sections that matter, and write down the answer.

Dispatchers should be especially careful here. A week on a regular commercial job and a week on a public project can look identical on the calendar and still be paid differently. That is a common source of errors, so flag public works jobs on the schedule itself.

Check whether the overtime law covers the employee

The DWD page also says: "The overtime law does not apply to most non-profit organizations." It then adds a caveat that changes the answer for some workers: "The overtime law does apply, however, to those employees who work in certain establishments, such as restaurants or hotels, even if employed by non-profit organizations."

Owners who run or work with non-profit groups should read both sentences together. Being a non-profit does not settle the question on its own. The first sentence says most non-profits are outside the overtime law. The second says some employees still fall under it, based on the type of establishment where they work.

In practice, first confirm whether the organization and the employee's workplace fit the exception the page describes. Only then decide how paid leave should be handled. Do not assume the answer from the organization's status alone. If you are unsure, ask the state directly before you set payroll.

What dispatchers should do

Dispatchers do not usually set the pay policy, but they see the schedule first, so they catch problems early. A short routine helps:

  1. Find the paid-leave rule in the written pay policy. If you cannot find it, ask the owner before the next pay period, not during it.
  2. When you build a week, count the hours the tech will actually work. Under the state minimum, a paid day off need not count as hours worked; if your written policy counts that leave, follow the policy.
  3. Flag public works jobs on the schedule so the right overtime rule is applied.
  4. Tell the tech what counts before the week starts. A conversation on Monday is easier than an argument on payday.
  5. Keep your notes. If a question comes up later, a dated note of what was said is worth having.

Keep time records that separate work from leave

Payroll can only apply the rule correctly if the timekeeping data separates hours worked from paid leave. Many errors happen because the two sit in one column, or because leave is entered as if it were a regular workday. A clear record shows, for each day:

  • the hours actually worked, with start and end times if the shop uses them
  • the type of any paid leave, entered on its own line
  • the date the leave was requested and approved
  • any extra pay for working a holiday, noted separately from leave

Keep these records for as long as your records policy requires, so you can answer questions about any past pay period. Use the guide to recording hours before approval when reviewing those entries.

Illustrative example: separating paid hours

Check the written policy to decide whether the leave enters the overtime calculation; the total paid hours alone does not answer that question.

What owners should decide

Owners set the policy, so the decisions are theirs. There are three reasonable approaches, and each has a cost in a different place.

  • Follow the state minimum. Paid vacation, sick leave, and holiday pay are not counted as hours worked for overtime. This is the simplest to administer, and the state guidance clearly allows it. The cost is that techs may see it as unfair if they expect paid time to count.
  • Count some kinds of paid leave. For example, the policy might count paid holidays but not vacation. This can be a workable middle path, but it needs clear wording so the difference is easy to explain.
  • Count all paid leave. This is the most generous option. It can make the policy easier to explain to techs, but payroll and scheduling must track each kind of leave carefully so the overtime totals are right.

Whichever approach you choose, check three things. First, the handbook should say the same thing payroll does. A handbook that promises one thing while payroll does another causes disputes that are hard to settle. Second, the policy should cover public works projects if you take them. Third, the policy should be in writing and acknowledged by each tech.

Sample policy wording

Owners often ask for simple language. Here is a plain example you can adapt:

"Under this policy, paid vacation, paid sick leave, and paid holiday pay are not counted as hours worked when overtime is calculated. Hours actually worked, including work performed on a holiday, count toward overtime."

Treat this as a starting point. Check it against your own situation, including any public works contracts, before you adopt it. If you choose to count paid leave, change the wording to identify which kinds count.

How to explain it to a tech

Techs ask this question because they want to know what their paycheck will look like. A short, plain answer works better than a long legal reply. For example:

"Your vacation and sick days are paid, but state guidance does not require us to count them as hours worked when calculating overtime; our written policy explains whether we do. Here's how that applies to your schedule this week."

Then show the tech the hours on paper. If the company's policy differs from the state minimum, say so and explain why. If you cannot answer right away, say so and find out, rather than guessing. A wrong answer given quickly causes more trouble than a short delay.

Common mistakes

  • Treating scheduled hours as worked hours. A calendar that shows a full week may include paid days off.
  • Putting paid leave and worked time in one number on the timesheet.
  • Making verbal promises. If a dispatcher tells a tech that paid time counts, and the policy says it does not, the tech will hold the company to the dispatcher's words.
  • Assuming a non-profit or a small shop is outside the rules without checking the DWD page.
  • Forgetting public works contract terms when scheduling a week.

Checklist before the next pay period

  • The pay policy states how paid vacation, sick leave, and holiday pay are handled for overtime.
  • Time records separate hours worked from paid leave.
  • Each tech knows the policy before the week starts.
  • Public works jobs are flagged, and their contract terms are reviewed.
  • Any non-profit coverage question has been checked against the DWD page.

For the payroll review, see the guide to technician overtime calculations.

A note on limits

This post explains what the Wisconsin Department of Workforce Development's guidance says and offers practical ways to apply it. It is not legal advice, and it does not cover every situation. Particular contracts, agreements, and individual employees may bring details that the general guidance does not address. When a question involves a dispute, a public contract, or a non-profit, read the source documents in full and get advice from someone qualified to give it before you act.

What to do today

Compare the written leave policy with a current time record. Check whether payroll separates leave from worked hours and follows the policy before approving that record.

The two answers at a glance

Where should I check employee coverage?

Start with the DWD overtime page and check the employee's workplace as well as the organization's status.

What if the handbook and payroll disagree?

Ask the owner to resolve the difference before the next pay period. Keep a dated note of the answer so dispatch and payroll use the same policy.

Can a public works project change the calculation?

Some public works construction projects can require daily overtime and overtime on certain holidays. For those jobs, read the contract before you schedule the week, and do not rely on the general rule alone.

Sources

More field guides