Ohio shift checks: 3 for age, pregnancy and neutral rules

Ohio managers can run three shift checks on age, pregnancy and neutral rules before posting an hourly schedule. Most managers think about scheduling as a question of coverage. Who is available, who can pick up a gap, who asked for a change, and whether the labor budget holds. Those questions matter, but they are not the only ones. A schedule is a set of decisions about who gets hours, which hours they get, and when those hours change. Each decision affects an employee's pay, their routine, and sometimes their health. When a decision is shaped by a protected characteristic, it can become an employment problem even when nobody intended that outcome.

This post gives you three checks to run before you build, change, or approve a shift for an hourly employee. They cover age, pregnancy, and rules that look neutral on paper. Run them while the schedule is still a draft, because a problem caught then costs far less than one raised in a complaint.

Key takeaways

Check every draft before it is posted, not after a complaint arrives.
For employees forty and older, ask whether a change cuts hours, pay or shift quality, and whether the reason is about the work.
For pregnancy and related conditions, compare the employee with others who have a similar limit on their ability to work.
For neutral rules, ask who they affect in practice and whether a less restrictive option would meet the same need.
Write down the reason for each flagged change and have someone other than its author review it.

The checks draw on the Ohio Revised Code's definitions in section 4112.01 and discrimination provisions in section 4112.02, and on federal guidance from employer.gov on age discrimination. Points beyond those sources are stated only in general terms. This is not legal advice. If a situation is close, bring in your HR team or employment counsel before you post the schedule.

Start with the definitions

Ohio's employment discrimination rules depend heavily on defined terms. Before you apply any check, you need to know what the state means by those terms. Managers often use everyday words that the law defines more narrowly or more broadly, and shift decisions are where those gaps show up.

Take "age." The code defines it this way: "Except as otherwise provided in section 4112.021 of the Revised Code, 'age' means an individual aged forty years or older." That definition is the starting point for the first check. It also comes with an exception that points to another section, so read that section too rather than assuming the forty-year line is the whole story.

The definitions also explain how pregnancy is treated. For the discrimination provisions, the code says that the terms "because of sex" and "on the basis of sex" include, but are not limited to, "because of or on the basis of pregnancy, any illness arising out of and occurring during the course of a pregnancy, childbirth, or related medical conditions." That is a wide reach. A decision that affects someone because of a pregnancy-related condition is not made safe simply because it is not about sex in the usual sense.

Finally, the code is not only about hiring. It also addresses conduct tied to employment under division (I) or (J) of section 4112.02, and it addresses people who believe they will be injured by an unlawful discriminatory practice described in division (H) of section 4112.02 that is about to occur. A shift decision can therefore be challenged for what it does to someone, not only for what it was called. Treat each check below as a test of effect, not just of intent.

Check 1: Age forty and older

The first check asks whether a shift decision treats an employee aged forty or older less favorably than others. The employer.gov age nondiscrimination page describes the core idea in plain terms: "Age discrimination occurs when a job applicant or employee is treated less favorably because of their age."

For a manager, the most common risk is not a dramatic statement. It is a pattern. Consider a schedule where the best shifts, the most predictable hours, or the first chance at overtime keep going to the same younger group of staff. Consider longer-tenured employees moved to early or late hours without a clear reason, or a supervisor who says an older worker "should not be on the floor" during a busy period. Each change may look small, but the pattern tells a story that a reviewer will read.

Use these questions when you build or approve a schedule:

Does the change reduce this employee's hours, pay, or shift quality?
Would the same change be made for an employee under forty in the same role with the same availability?
Is the reason written down in terms of the job, such as coverage needs, skill requirements, or a documented request?
Did a comment about age, energy, speed, or "fit" influence the decision, even indirectly?
If the employee asks why, can you give an answer that is about the work and not about their age?

If you cannot answer the last question clearly, stop and review the change.

Illustrative example: a weekend shift draft

A manager has 3 open weekend shifts and 3 people who could take them. 2 of the people are forty or older, and 1 is under forty. Before giving the shifts to the under-forty worker, the manager asks the second question on the list: would the same change be made for an employee under forty in the same role with the same availability? If the answer is no, and no job reason is written down, the manager asks a second person to review the change before the schedule is posted.

Watch for the subtle cases too. Scheduling that assumes an older employee cannot handle a task, without checking their actual ability, is a risk even if nobody says the word "age." Base the schedule on the skills the job requires and on the employee's stated availability. The reverse also carries risk: giving an older employee a lighter schedule because you assume they want one. Ask first. Deciding for an employee, even with good intentions, can still leave them worse off.

The second check asks whether a shift decision treats an employee differently because they are pregnant or have a condition connected to pregnancy. The Ohio code is direct on this point. It says women affected by pregnancy, childbirth, or related medical conditions must be treated the same for all employment-related purposes, including benefits under fringe benefit programs, as other people not so affected but similar in their ability or inability to work.

That sentence contains the test. The comparison is not between a pregnant employee and every other employee. It is between a pregnant employee and others who are similar in their ability or inability to work. If a worker cannot safely lift, stand for long periods, or work certain hours because of a condition, ask how the business treats other workers with a similar limit. Giving a comparable worker a change in shift or task while denying it to a pregnant worker with a comparable limit is the kind of difference the code addresses.

Shift work makes this concrete. Start times, break timing, weekend assignments, overtime offers, shift swaps, and the hours scheduled after a medical appointment are all employment-related decisions. Managers should not treat a pregnancy-related change as a special favor. In many cases it is simply equal treatment for a similar limit. For a related guide, see pregnancy schedule requests for shift leads.

Use these questions when a pregnant employee or an employee with a pregnancy-related condition is on your schedule:

Am I comparing this employee to others with a similar limit on their ability to work, not to everyone on the floor?
Did I apply the same flexibility I have given other employees with similar restrictions?
Did I make a change based on an assumption about what a pregnant employee can or wants to do?
Did I ask the employee what they need, and did I record that request accurately?

Be careful with assumptions in both directions. Do not remove a worker from a shift because you expect them to be less reliable, and do not add heavier work or extra hours because you assume they can handle it. Either way, you are deciding based on your view of someone's pregnancy.

The phrase "related medical conditions" is wider than most managers expect. The code's definition includes illness arising out of and occurring during a pregnancy, and it includes childbirth. If an employee returns after a medical event connected to pregnancy and asks for a schedule change, give the request the same care you would give any employee with a comparable limit. Do not press for more explanation than you need, and do not treat the request as a question of commitment to the job.

Check 3: Neutral rules that land unevenly

The third check is the one managers most often skip, because it looks like the safest. Neutral rules apply to everyone the same way on paper. Examples include requiring every employee to be available for every weekend, requiring a doctor's note for any absence over a set length, giving first pick of shifts to the most senior worker, or barring changes to a schedule once it is posted.

Neutral rules are not automatically lawful. The employer.gov age nondiscrimination page raises the question directly: "How might policies that apply to all employees be considered discrimination?" A rule can be neutral in its wording and still fall more heavily on people who are older, pregnant, or in need of a particular accommodation. When that happens, it deserves the same scrutiny as a rule that names a group.

To test a neutral rule, ask who it affects in practice. Who can meet the requirement, and who cannot? Who is pushed out of a shift, who loses a benefit, and who gets a schedule change they did not request? If the answers line up with age or pregnancy, the rule needs a closer review even if its text is even.

Shift rules to review closely include:

Availability requirements, especially those that require a worker to be available at all hours or on every weekend.
Seniority-based shift bidding, which can give older workers the best hours while newer workers absorb the worst, or the reverse.
Attendance rules that count absences tied to medical appointments, pregnancy-related conditions, or recovery.
Rules about posting, swapping, and changing shifts, which can penalize a worker who cannot make a short-notice change.
Overtime offers that go first to the most available employees when those employees are concentrated in one group.

For more on fair time-off settings, see time off rules for fair rosters.

For each rule, ask whether it is necessary to the job and whether a less restrictive option would meet the same need. A business reason is not enough by itself. If a rule can be changed to keep the business need while reducing the uneven effect, that is usually the better choice. Review posted rules at least once a year, and again whenever you change a shift pattern or hear a concern from staff. Keep a short note of what you checked and what you changed.

A working checklist for each schedule

Put the three checks into your normal scheduling cycle. A short checklist works better than a long policy document, because managers are more likely to use it when they are busy.

Before you publish a draft, list every change that affects pay, hours, shift type, or task assignment. For each one, note the employee, the reason, and whether the employee requested it. Flag any change where the employee is forty or older, where the employee is pregnant or has a pregnancy-related limit, or where the change follows a neutral rule that might fall unevenly. Flagged changes get a second look from someone other than the person who made them. For a companion checklist, see schedule change approval checks.

For flagged changes, answer four questions. What is the business reason? Who else is in a similar situation, and how were they treated? Did the employee ask for the change, or did we assume it? Could we reach the same goal another way with less effect on this person?

If the second look raises a concern, pause the change. Talk to the employee, explain the reason for the schedule in plain words, listen to what they say about their availability and limits, and look for an option that works for both sides. Document the outcome, even if the answer is to keep the original plan.

Finally, make sure approvers know what to look for. Many shift problems start with a supervisor who wants to fill a gap quickly. Approvers should be able to decline a change that cannot be explained.

Documentation and the approval step

Documentation is not a way to cover a bad decision. It shows that a decision was made for real reasons. When a change affects hours or pay, write down the reason in the same terms you would use with the employee: the business need, the skill or coverage requirement, and any request from the employee. Avoid notes that describe an employee's age, pregnancy, or health in your own words, and avoid speculation about what they can or cannot do.

Be consistent. If you record the reason for one employee's change, record it for others too. Gaps in the records are often what makes a reviewer suspect a pattern. A simple form asking for the reason, the request source, and the second-look result is enough for most teams.

Employees may also raise concerns before anything goes wrong. Treat a concern about a schedule decision as information to review, not a complaint to manage away. Listen, check the facts, and respond in writing when a decision changes.

What this post does not cover

This post covers the Ohio code provisions and federal guidance cited above, plus general practices that follow from them. Other laws may apply to your workplace, including federal rules and rules that depend on your industry, company size, or contracts. It also does not tell you what a specific schedule must look like. The right answer depends on the job, the people, and the facts. If you are unsure whether a change is lawful, ask your HR team, employment counsel, or the agency that administers the law.

The short version

Three checks cover most of the risk in everyday shift decisions. Check whether age forty and older is affecting the schedule. Check whether pregnancy or a pregnancy-related condition is affecting it, comparing the employee to others with a similar limit. Check whether a neutral rule falls unevenly in practice. Run these checks on every draft, record the reasons, and give approvers a clear way to flag concerns.

Good scheduling balances fairness and business needs. These checks help you keep both in view, and they make it easier to explain a decision to an employee, a supervisor, or a reviewer.

Next step today: open your next draft schedule, list every change to pay, hours, shift type or task assignment, and run the three checks on those changes before anything is posted.

Frequently asked questions

Who does the age check cover?

The age check covers employees aged forty or older under the Ohio definition, and you should also read the exception that points to section 4112.021.

Can a neutral rule still be a problem?

Yes, if in practice it falls unevenly on older workers, pregnant workers, or people who need an accommodation, even though its wording is even.

No. In many cases it is equal treatment for a similar limit on the employee's ability to work.