Move on to the reading area
Shiftpedia

Wisconsin safety-based shift limits: 3 checks

Shiftpedia Editorial Team · Posted · Last checked · 12 min read

Before imposing a safety-based shift limit in Wisconsin, check the job-related risk, evidence that the restriction is necessary, and accommodation options.

Key takeaways

  • Tie the safety concern to specific duties in the job, and write down the facts.
  • Be ready to show a reasonable probability that the limit is necessary to prevent harm. The burden is yours, not the worker's.
  • Look for accommodations and alternative assignments first, and treat hardship as something you must demonstrate, not assume.
  • Keep the restriction no broader than the risk, review it on a set date, and document the whole process.

Why this decision needs more than a good intention

A shift lead notices that a worker seems tired on the early shift. A nurse's supervisor hears about a near miss. A plant manager reads a doctor's note that mentions a medication with side effects. In each case the instinct to protect people is a good one. The problem starts when that instinct turns into a schedule change, a shorter week, or a ban from certain shifts, and nobody has checked whether the change is justified or whether it is the smallest step that solves the problem.

Safety-based limits call for a job-specific assessment. An employer can consider safety. An employer cannot use safety as a general excuse to keep a worker with a disability out of a job, and an employer has to think through accommodation rather than skip it. Those two ideas pull against each other, and managers in Wisconsin have to hold both at once.

The three checks below are practical steps for managers and shift leads to run before they put a safety-based shift limit in writing. They are general guidance, not legal advice. If a limit is already in place, or a worker has complained or hired a lawyer, bring in your HR team and an employment attorney before doing anything else.

Check 1: Is the safety concern tied to the actual job?

Start with the work, not the label. A diagnosis, a medication, or a general impression of someone's health is not the same as a safety problem in a specific job. Wisconsin's fair employment statute addresses this directly. When deciding whether a person with a disability can adequately undertake the job-related responsibilities of a particular job, the statute says that “the present and future safety of the individual, of the individual’s coworkers and, if applicable, of the general public may be considered.” Wisconsin Legislature

That is a real allowance, and it matters. But notice what it points at: the job's responsibilities, and the people those responsibilities affect. It does not permit a vague worry that someone might get hurt somewhere, sometime. The question is always tied back to the work.

So write the concern down in concrete terms before you decide anything:

  • Which task, piece of equipment, or location creates the risk?
  • What would go wrong, and who could be hurt?
  • Does the risk come from the job's demands, or from the worker's condition as it affects those demands?
  • How often has this happened, or how often is it likely to happen?

A forklift operator who may have dizzy spells while running a truck near pedestrians presents a different question from a clerk whose shift length someone finds uncomfortable. The first one may call for a restriction tied to the forklift. The second one probably does not involve safety at all, and a shift cap would be hard to justify.

Roles with a duty to the public get extra attention under the statute. The same section says that where employment involves “a special duty of care for the safety of the general public, including but not limited to employment with a common carrier, this special duty of care may be considered” in evaluating whether the employee can adequately do the job. Wisconsin Legislature If your workers drive passengers, operate public transit, or carry out similar duties, that duty of care belongs in your analysis. If your workplace serves the public in a more ordinary way, do not borrow that language to make your case sound stronger than the facts allow.

Last, test whether your reasoning is grounded. The statute's annotations describe a case about a taxi company that used federal regulations as a hiring standard. Those regulations did not apply to the company directly, but the annotation says the standard showed “a rational relationship to the safety obligations imposed on the employer, and its use was not the result of an arbitrary belief lacking in objective reason or rationale.” Wisconsin Legislature

The takeaway for a manager is simple. Your reason needs an objective basis. “I have a feeling” is not one. A reason that you can point to in records, and that a neutral person would find sensible, is.

Here is a quick gut check. Could you explain the concern to a neutral reviewer using facts, without relying on words like “fragile,” “risky,” or “they probably can't handle it” that describe the person rather than the work? If you can't, pause here. The concern may still be real, but it isn't ready to become a limit.

Check 2: Can you show the limit is necessary?

Start by examining the evidence for the proposed restriction. When an employer relies on a safety-based restriction, the burden is on the employer. The statute's annotation puts it this way: “an employer bears the burden of proving to a reasonable probability that the restriction is necessary to prevent harm to the employee or others.” Wisconsin Legislature

Two points stand out in that sentence.

First, the burden sits with you. You cannot simply assert that a risk exists and wait for the worker to disprove it. If the limit is challenged, you will need to be able to show your work, so write your reasoning down before the limit takes effect as a practical precaution.

Second, the standard is a “reasonable probability,” and the restriction has to be “necessary to prevent harm.” A harm that is merely possible in theory does not meet that bar. Neither does a limit that would prevent a harm only loosely connected to what you are worried about. You need evidence that the risk is likely enough to matter, and that this particular limit is what would reduce it.

Here is how to build that case in practice:

  • Collect records. Incident reports, near-miss logs, safety audits, and performance notes tied to the specific task. Record dates, what happened, and who was involved.
  • Use information from reliable sources. Medical information should come from the worker or a qualified source. Ask HR how your company handles this.
  • Look at the scale of the limit. If the risk comes from one task, the necessary restriction may be about that task. Cutting all of someone's shifts, or moving them to a different schedule entirely, goes further than the risk may require. A limit that is broader than the problem is hard to defend as necessary.
  • Consider the future honestly. The statute allows you to consider future safety, but a future risk still has to meet the reasonable probability test. “This might get worse someday” is not enough on its own. If you think a condition may change, describe what you are watching for and when you will reassess.

If the records do not support a reasonable probability of harm, you do not yet have a safety-based limit. You have a concern that needs more information, a conversation with the worker, or a different kind of fix. That is a fine place to be. It is much better than a restriction you cannot explain later.

Check 3: Did you consider accommodation first?

The third check protects both the worker and the employer. Wisconsin's statute addresses refusing to accommodate a worker's disability directly, and it sets the default clearly. The statute names as a prohibited practice “Refusing to reasonably accommodate an employee’s or prospective employee’s disability unless the employer can demonstrate that the accommodation would pose a hardship on the employer’s program, enterprise or business.” Wisconsin Legislature

Two things follow from that sentence.

The first is the word unless. The default is that a reasonable accommodation should be made. The exception applies only when the employer can demonstrate that the accommodation would pose a hardship on its program, enterprise, or business. The burden of demonstrating hardship is again on the employer. You cannot assume an accommodation is too costly or too disruptive. You have to be able to show it, with specifics.

The second is how broadly the statute is meant to be read. The Wisconsin page notes that this part of the statute “is to be broadly interpreted and may involve the transfer of an individual from one job to another.” Wisconsin Legislature In plain terms, the fix may not be a restriction at all. It may be a change in duties, a different piece of equipment, a different workstation, or a move to another job the worker can do well.

That is the heart of this check. Before you limit someone's shifts, ask these questions in order:

  1. Can the risk be removed by changing the task, the equipment, the workstation, or the way the work is arranged within the same job?
  2. If the risk is tied to one part of the job, can the worker do the rest of the job with that part adjusted or removed?
  3. Is there another job in the organization that the worker can do safely and that fits their skills?
  4. If none of these work, what specifically would the hardship be, and can you document it with real numbers and real constraints?

Federal guidance points in a similar direction, although it is written about job applicants. The U.S. Equal Employment Opportunity Commission says: “An applicant with a disability, like all other applicants, must be able to meet the employer's requirements for the job, such as education, training, employment experience, skills, or licenses.” U.S. Equal Employment Opportunity Commission The practical lesson for a manager is that the question is about meeting the job's real requirements. It is not about whether a worker fits your general picture of what a person with that condition can handle.

Do not treat the worker's own suggestions as an afterthought. If a worker proposes an adjustment, take it seriously, consider it on its merits, and respond in writing. If you cannot do what was asked, explain the specific reason, and say what you can do instead. A worker who was part of the conversation is more likely to trust the outcome, and you are more likely to find a workable answer.

Illustrative example: Testing a proposed hours cap

A shift lead at a Wisconsin packaging plant learns that an operator on a palletizing line has a condition that sometimes causes brief lapses in alertness. The lead wants to move the worker to days, take them off the palletizer, and cap their weekly hours.

The lead checks whether the concern involves the machine, the hours, or both, rather than assuming a general cap would help. The lead talks with the worker and with HR before deciding. The lead asks whether the worker can rotate to another station on the line that does not involve the palletizer. The lead documents each option, what it would take, and whether the plant can do it.

What to put in writing

If you do impose a restriction, the paper trail should let someone else reconstruct your reasoning without having to ask you. Include:

  • The specific job duty, machine, or location the concern involves.
  • The facts and records you relied on, with dates.
  • The alternatives you considered, why each was or was not workable, and any hardship you could document.
  • The worker's input, including any accommodation they requested or suggested, and your written response.
  • The exact scope of the restriction, so it does not reach beyond the risk.
  • A date to review the restriction, and the kinds of changes that would lead you to lift or adjust it.

Keep the written record factual. Avoid language about the worker's character or about what they might be like in the future. Describe the job, the facts, and the decision. If someone reads the file a year from now, they should be able to see why you acted without needing to know the people involved.

For the separate roster workflow, use the schedule change approval guide.

Mistakes to avoid

Some patterns show up again and again when managers get this wrong.

Using safety as cover for a general preference. If you would not impose the same limit on a coworker with a similar record who does not have a disability, you need a clear job-based reason why it applies to this worker's duties. If you cannot name one, the limit is probably about preference, not safety.

Acting on the diagnosis instead of the job. A label does not tell you what a worker can safely do in a particular role. The job's demands and the facts about how the condition affects them are what matter.

Skipping the conversation. Many risks are easier to address once the worker has described their own experience, their limits, and their ideas. Talking to the worker is not an extra step to get through. It is often where the best option comes from.

Making the limit permanent by default. A restriction should be reviewed when the facts change. A limit with no review date tends to outlive the reason for it.

Changing hours or assignments quietly. Tell the worker what is changing, why, and how they can raise concerns. A change that appears without explanation looks like a punishment, even when you meant it as protection. For changes handled through swaps, see the shift swap guide.

Treating hardship as a feeling. “It would be inconvenient” is not the same as demonstrating a hardship to the business. The statute places the burden on the employer, so document costs, staffing effects, and operational constraints with specifics.

When to bring in help

Stop and involve HR and an employment attorney if any of the following is true. The worker has asked for an accommodation and you have not answered in writing. The worker has complained, or has mentioned a lawyer or an agency. A medical provider has given you restrictions you do not fully understand. Or the proposed limit would remove most of the worker's hours or move them out of their current job.

You should also get help if the role involves a special duty of care to the public, such as driving or other public-facing safety work. The analysis is more specific in those roles, and a mistake can affect more people than the worker in front of you.

Today, write down the task causing concern and gather the related incident records before proposing a schedule change.

Questions before changing shifts

What should I ask HR about medical information?

Ask HR how your company handles information from the worker or a qualified source. Bring the specific job concern so the discussion stays focused on the work.

How should I respond to a suggested adjustment?

Respond in writing after considering the adjustment on its merits. If you cannot do what was asked, explain the specific reason and what you can do instead.

Sources