Reference · built on requestOperator by FibricWorkforce & scheduling

Minor Hours

Checks each minor's draft shifts against school-day, weekly, and evening limits and proposes the fix before the schedule publishes.

Request accessPricing ↗

About

Minor Hours is an operator job for schedules that include employees under 18. It reads birth dates from your HRIS, draft shifts from your scheduling system, and the rule set for each site: the federal floor for 14- and 15-year-olds, the stricter state rules you supply, and the school-term dates and public holidays that decide whether a day counts as a school day. It then checks every minor's week: hours on a school day, hours in the week, the earliest start and latest finish, and hours already worked on the clock.

Each breach becomes a proposal: shorten the shift, move it, or hand it to an adult with the same role. The scheduler approves in Slack or Microsoft Teams before publishing, and every fix is recorded with the rule it satisfied.

This is a reference listing. It documents what Fibric would read from Minor Hours and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Birth dates and hire status from the HRIS: Deputy Employee DateOfBirth, UKG Pro person-details, BambooHR employee records, Rippling workers
  • Draft and published shifts for each minor: Deputy Roster/QUERY, 7shifts shifts with the draft filter, When I Work /2/shifts including unpublished ones, Homebase shifts
  • The rule set per site and age band: the federal limits for 14- and 15-year-olds plus the state, city, and work-permit rules you enter
  • School-term dates you supply per site, and public holidays by country and subdivision from the Nager.Date feed, which count as non-school days
  • Hours already worked in the week, so a weekly cap counts worked plus scheduled: Deputy timesheets, When I Work /2/times, Homebase timecards
  • Publish events that close the window: 7shifts schedule.published, Deputy roster/publish, When I Work /2/shifts/publish

Proposed actions

  • Target capability: propose the breach list per site before publish: the minor, the shift, the rule it breaks, and by how many hours or minutes
  • Target capability: propose shortening or moving a draft shift to fit daily and evening limits, as a Deputy, 7shifts, or When I Work shift update
  • Target capability: propose reassigning a breaching shift to an adult employee with the same role, as a direct assignment or an open shift
  • Target capability: propose a Slack or Microsoft Teams message to the scheduler carrying the breaches and the fixes for approval
  • Target capability: propose a Deputy Journal entry or an appended sheet row recording the breach, the fix, and who approved it

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Catch a school-night shift in 7shifts before publish

    Draft shifts for users under 16 are checked against the 7:00 p.m. evening cutoff and the 3-hour school-day cap. Breaches go to the scheduler in Slack with a shortened shift proposed for each.

    With 7shifts, BambooHR, Slack

  • Count worked hours toward the weekly cap in Deputy

    Timesheets for the week so far are added to rostered hours for each employee whose DateOfBirth makes them 14 or 15. Where the total passes 18 hours in a school week, the operator names the shift to trim.

    With Deputy, Holidays & FX Reference

  • Apply the summer extension in When I Work

    From June 1 through Labor Day the federal evening limit moves to 9:00 p.m. The operator reads the date, applies the matching cutoff, and proposes unpublished shift changes through /2/shifts before /2/shifts/publish runs.

    With When I Work, UKG Pro, Microsoft Teams

Requirements

  • An HRIS connector that exposes birth dates: Deputy, UKG Pro, BambooHR, or Rippling
  • A scheduling connector with draft or unpublished shifts and a publish event: Deputy, 7shifts, or When I Work
  • Per site: the applicable state and local rules, school-term dates, and the country or subdivision for public holidays
  • Slack or Microsoft Teams, where the scheduler answers each proposal
Authentication
Stores no credentials. Birth dates, shifts, and holidays are read through the connectors and signals you bind, each under the access that binding was granted.

Limits

  • The US Department of Labor publishes the floor for 14- and 15-year-olds; state, city, and work-permit rules vary and you supply them per site
  • School calendars are not public data. Term dates come from you; the holiday feed supplies public holidays only
  • A minor with no birth date on file is listed as unchecked, never assumed to be an adult
  • After a schedule publishes, a breach is reported to the scheduler; the operator does not edit a published shift

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Minor Hours ↗

Questions and answers

What does the scheduler approve?
A list of shift edits, one per breach: shorten, move, or reassign. Each shows the minor's age band, the rule, and the hours before and after. The scheduler approves any or all of them, and the schedule is still published by a person.
Where do the rules come from?
The federal limits for 14- and 15-year-olds come from the US Department of Labor: 3 hours on a school day, 18 in a school week, 8 on a non-school day, 40 in a non-school week, and 7:00 a.m. to 7:00 p.m. State rules and school-term dates are yours to supply; the stricter rule wins and is named on each proposal.
Does it ever change a shift on its own?
No. It proposes, then waits for the scheduler. Nothing is written to the scheduling system without the scheduler's answer, and a proposal nobody answers is reported at publish time as an open breach.
Ask about Minor Hours

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy