Build four guardrails into your scheduler: a school-night end-time cap, a weekly-hours cap during non-school weeks, a consecutive-hours break rule, and a nonwork-rest floor. Test each one with a real minor's profile before you trust the tool's auto-fill.
Key takeaways
- For Ohio worksites, stop any minor shift ending after 11 p.m. before a school day.
- For Ohio worksites, stop any non-school week that exceeds forty hours for a minor.
- Enforce a rest period of at least thirty minutes after five consecutive hours.
- At Delaware worksites, enforce 8 consecutive nonwork hours in every 24-hour day.
Why a scheduling tool needs a minor-shift test
Your scheduling tool probably assumes every worker is an adult. It fills a night shift, stretches a Saturday, or blocks hours without asking one question: is this person under 18? That silence is the risk. A tool that publishes a minor onto a shift that runs past a legal cutoff, or a stretch without a required break, puts you in breach before anyone clocks in.
Minor work rules are narrow, state-specific, and tied to the school calendar. They are not advisory. Ohio and Delaware both set hard rest rules, and Ohio also sets hard limits on night work and weekly hours. Your scheduling tool should enforce those limits at the moment you build the shift, not audit them after the fact. For state-by-state context, see teen work limits by state.
This post covers four rules you can test today in your tool. Rule one and the weekly cap in rule two come from Ohio Revised Code. Rule four comes from the Delaware Code, as does the excused-absence point in rule two. Rule three draws on both states. Each is written in plain words and paired with a concrete test you can run inside your scheduler. The point is not to turn you into a labor lawyer. The point is to give you four checks you can build into your publishing workflow so your tool stops being the weak link.
Rule one: the school-night end time
Ohio sets a hard stop on night work before a school day. Under Section 4109.07 of the Ohio Revised Code, a minor may not work "After eleven p.m. on any night preceding a day that school is in session." The cutoff is 11 p.m. sharp, and it hangs entirely on whether school runs the next day.
This rule is a scheduling tool's most obvious failure point. Auto-scheduling loves to backfill a closing shift. If your tool does not know the minor's school calendar, it will happily post a shift that ends well past 11 p.m. on a Sunday. The tool sees available hours. That is a violation if school is in session the next day.
Ohio also defines "school" for this purpose. The statute states that "school" refers to either a school the child actually attends or a school he is required to attend pursuant to Chapter 3321. of the Revised Code. Your tool needs to hold that distinction.
Test this in your tool: - Build a shift for a known minor that ends shortly after 11 p.m. on a Tuesday. - Save the shift. Watch whether the tool blocks it, warns you, or publishes it. - If the tool publishes it silently, you have your first gap.
The fix is a profile flag. Mark the worker as a minor with a school-in-session flag. Then set an end-time rule on any night that precedes a school day. If your tool cannot hold a "school night" flag at all, that is a scope question for your vendor, and you should raise it before you schedule another minor.
Rule two: the weekly-hours cap during non-school weeks
Ohio caps a minor at forty hours in any week that school is not in session. The statute states: "(8) For more than forty hours in any week that school is not in session."
The scheduling risk here is the summer surge. Hiring managers stack seasonal help onto a June or July schedule. Your tool's auto-fill does not know a school year from a summer break. It will let you publish an overlong week for a minor without blinking.
Test this in your tool: - Put the minor's profile into a non-school week. - Build a shift schedule that exceeds forty hours in total. - Attempt to publish. Check for a block, a warning, or a silent pass.
A weekly-hours guardrail needs two inputs: a minor flag and a school-in-session calendar. If your tool only tracks hours per day and not hours per week for a given worker, the gap is structural. Raise it with your scheduling vendor before the next break period.
What Delaware adds on school excuse
Delaware handles school-linked hours differently. Under the Delaware Code, Title 19, Chapter 5, paragraph (a)(1) of the section "shall not apply to a minor who has been excused from public school attendance by the public school authorities." An excused absence changes the picture on that day.
This matters for your tool because the flag is not static. A minor can be in school on Monday and excused on Tuesday. Your scheduler needs a day-level override, not just a permanent status. If your tool only lets you set a minor flag once at profile creation, an excused-absence day will not adjust the available hours.
Rule three: the consecutive-hours break rule
Both states require a break when a shift runs long. They phrase it differently, and your tool should hold both patterns.
Ohio's rule is a hard block on consecutive hours. The statute states: "No employer shall employ a minor more than five consecutive hours without allowing the minor a rest period of at least thirty minutes." Ohio also clarifies that "The rest period need not be included in the computation of the number of hours worked by the minor." The break does not count toward hours worked for this calculation.
Delaware's parallel rule uses slightly different phrasing. A minor under 18 "shall not be employed or permitted to work more than 5 hours continuously without a nonworking period of at least one half hour."
The scheduling failure mode is a double or a split that stacks. Auto-scheduling builds an eight-hour block with a short meal. Ohio and Delaware both require a rest period of at least thirty minutes. Your tool's default break setting may be shorter than the legal floor. For related checks, see minor hire pay and breaks checks.
Test this in your tool: - Build a six-hour continuous block for a known minor. - Insert a break shorter than thirty minutes near the end of the fifth hour. - Attempt to publish. Check whether the tool flags the break length.
The clean fix is a break-length floor on the minor profile. Set the minimum nonwork period to at least thirty minutes whenever a continuous block exceeds five consecutive hours. If your tool cannot enforce a minimum break length for each worker type, ask your vendor for that capability by name.
Here is how the two states compare on the figures you just read:
| State | Consecutive-hours break |
|---|---|
| Ohio | At least thirty minutes after five consecutive hours |
| Delaware | At least one half hour after 5 hours continuous |
Rule four: the nonwork-rest floor between days
Delaware sets a floor on rest that spans days, not just within a shift. A minor under 18 "shall have at least 8 consecutive hours of nonwork, nonschool time each 24-hour day."
This is the rule that breaks back-to-back scheduling. A minor closes Tuesday night and opens Wednesday morning. Your tool sees two separate shifts.
Your tool's behavior should follow the state of the worksite. If you staff in both states, your scheduler needs a state field on the worksite, not just on the worker.
Test this in your tool: - Schedule a minor to end a shift late on a Tuesday. - Schedule the same minor to start early on a Wednesday morning. - Attempt to publish both. Watch for a 24-hour-window check.
The gap here is usually a missing rolling-window validator. If your tool validates shift by shift, it may never check the gap between shifts, and that is a specific capability to request from your scheduling vendor.
Where the four rules sit in your publishing flow
You have four guardrails now. Each one maps to a specific check your tool should run at publish time, not at audit time. Wire them in rule order.
Each check needs a minor flag on the worker profile and a state field on the worksite. Without both, the tool is guessing. With both, the tool can block a bad shift before it reaches the schedule board.
Your next step today: run the rule-one test on a Tuesday shift and see whether your tool blocks it.
Related guides: Maryland retail breaks: 3 rules for shift offers · Meal break rules in 4 states for shift handoffs · New Jersey minor hiring: 3 checks before work starts.
Common questions from hiring managers
Does the 11 p.m. Ohio cutoff apply to weekends? Yes, if school is in session the next day. If school runs Monday, Sunday night is capped. If school does not run Monday, that particular cap does not apply for that night. Your tool needs a school calendar to make that call.
What counts as a rest period under the five-hour rule? Ohio requires a rest period of at least thirty minutes and states it need not count toward hours worked. Delaware requires a nonworking period of at least one half hour after five hours continuous.
Can I extend a minor's hours during a school break? Your tool should hold both the school-year and non-school-week modes separately.
How does Delaware's excused-absence rule interact with my tool? A minor excused from public school attendance by public school authorities falls outside the paragraph (a)(1) restriction for that day. Your scheduler needs a day-level override, not a permanent profile change.
What if my worksite spans both states? Set the state field on the worksite. Ohio's cited rules and Delaware's cited rules differ on the night cutoff, the weekly cap, and the daily nonwork floor. A single global setting will not hold.
Who confirms the right answer for my specific situation? If a shift pattern is close to a boundary and you cannot tell from the statute text, ask your state's labor department before you publish. That one question is cheaper than a citation.
A pre-publish checklist you can run today
Run this on your next minor schedule before you hit publish.
- Confirm every minor is flagged as a minor in the worker profile.
- Confirm every worksite carries its correct state.
- At an Ohio worksite, build a Tuesday shift ending shortly after 11 p.m. and check for a block.
- At an Ohio worksite, build a non-school week totaling more than forty hours and check for a block.
- Build a six-hour continuous block with a break shorter than thirty minutes and check for a block.
- At a Delaware worksite, schedule a closing shift and an opening shift less than 24 hours apart, with fewer than eight nonwork hours between them, and check for a block.
- Ask your scheduling vendor, by name, for a school-calendar field, a worksite-state field, a minimum-break-length rule, and a rolling 24-hour validator.
Each of these tests takes minutes. Together they show you exactly where your tool is guessing and where it is enforcing. Fix the gaps before the next minor hits the schedule.