SCHEDULING

How to Schedule Employees Under 18: Two Limits, and the One That Breaks

Two limits run at the same time on a minor’s schedule, and only one of them is ever checked. Managers count the hours. Almost nobody counts the clock.

Why do the hours add up and the schedule still break?

Because a legal number of hours can sit in the wrong part of the day. The arithmetic is the easy limit. The calendar is the one that catches people out.

For example, take Maya, who is fifteen and works a counter after school. Watch what happens when the shift moves half an hour and nothing else changes.

I check the finish time before I check the total. The total is almost never the thing that is wrong.

Three hours is three hours in all three rows, and one of them is wrong. That is the whole problem with checking a minor’s week by adding it up.

Two limits means two mechanisms. XShift AI splits them: one is a sentence you write down, the other is a calendar attached to the person.

What do the federal rules actually say?

Fourteen is the floor for most non-farm work, and everything tightens below sixteen. Below are the cells worth memorizing. The rest is on the fact sheet.

The Labor Department publishes the whole grid, including the school-week total and the non-school day, in Fact Sheet #43 on child labor in non-agricultural occupations. Read it rather than a summary of it.

Food service has its own version in Fact Sheet #2A for restaurants and quick-service establishments, and the YouthRules pages collect the rest.

I keep my own state grid printed and pinned up, because the federal one is a floor rather than an answer.

Your state is the one that usually decides. Wherever a state rule is stricter, the stricter rule governs, and the Labor Department keeps a table of state child labor standards for exactly that. None of this page is legal advice.

How do you hold the hours limit on every schedule?

Write the cap down once, against that one named person, rather than holding it in your head. By hand that means a running weekly total per person, recounted every time the week changes.

Which is fine with four people and hopeless with forty. So most operations do the arithmetic at the start of the week and never again.

In XShift AI’s Autopilot the cap is one plain sentence, such as “Maya cannot go over 15 hours a week.” From then on it is checked in four separate places.

It counts the hours already assigned that week, Sunday through Saturday, plus the shift being added. Shifts still being built in the same recurring batch count too, so a repeating block cannot slip past the number.

When a save is refused it names the person, where they are now, where the shift would put them, and by how much it goes over. A cap on the length of one single shift works the same way.

How do you hold the times of day, and where does that break?

Blocked hours live in the person’s availability, and in XShift AI that means repeating weekly windows with a start and an end. A manager sets them from the team list, and the employee can set their own where the business allows it.

So for Maya you block 7:00 PM to 7:00 AM on school nights, and every schedule built afterwards works around it. Those blocks are read in three places.

Here is the part nobody else will tell you: a manager saving a shift by hand is not checked against availability. The hours cap still applies on that save. The blocked window does not.

So I would build the week with the generator and edit it afterwards, never the other way round. Build first, and the blocks are honored on every shift it places. Drag a name onto a Tuesday evening yourself and nothing stops you.

The evening line is the one to diary. It moves on June 1 and moves back after Labor Day, and a schedule template saved in July is wrong on the first Tuesday of September.

Two pages sit next to this one: the 19 checks a staff schedule has to survive and the guide to scheduling rules by state.

What else comes up when scheduling minors?