Reference · built on requestOperator by FibricWorkforce & scheduling

Break Compliance

Watches punches against meal and rest break rules for the site's jurisdiction and proposes a break reminder or a premium-pay flag.

Request accessPricing ↗

About

Break Compliance is an operator job that watches a shift while it is being worked. It reads the open punch and the breaks recorded against it from your time and attendance system, the shift's scheduled length, and the break rule you set for the site: how long a break is due, and after how many hours of work. When a break falls due and has not started, it proposes a reminder to the manager on duty.

After the shift closes, it reads the breaks as recorded, including breaks the employee attested to skipping, and finds shifts where a required break was short, late, or missing. For each it proposes a premium-pay flag for payroll, with the punches and breaks that justify it, for a manager to approve.

This is a reference listing. It documents what Fibric would read from Break Compliance 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

  • Open punches and their breaks: Homebase timeclock status with on_break, mandated_breaks, and current_shift; When I Work punch state and shift breaks
  • Breaks as recorded: 7shifts punch breaks with paid, in, and out; Homebase timebreaks with mandated_break_id and work_period; When I Work shift-breaks with skipped and auto_deducted
  • Break attestations: When I Work break attestations with taken and paid; 7shifts time punches flagged missed_break
  • Scheduled and planned breaks: When I Work scheduled breaks with length and paid; Dayforce EmployeeSchedules with Breaks; 7shifts labor settings with auto_break_hours
  • The break rule per site: the jurisdiction field in 7shifts labor_settings, or the rule you set in the operator's configuration
  • Pay adjustment codes payroll accepts for a premium: Dayforce pay adjustment codes, ADP Workforce Now pay data input, Paylocity pay entry import

Proposed actions

  • Target capability: propose a break reminder to the manager on duty in Slack or Microsoft Teams, naming the employee, the punch, and the break due
  • Target capability: propose a premium-pay flag: a Dayforce pay adjustment with IsPremium, or a pay data line for ADP Workforce Now or Paylocity
  • Target capability: propose a break correction where a break was taken but not punched, through 7shifts Update Time Punch or When I Work shift breaks
  • Target capability: propose a weekly list per site of shifts with short, late, or missing breaks, with the rule applied to each

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

What you can build

  • Remind a Homebase manager before a mandated break lapses

    Timeclock status per job shows who is clocked_in, for how long, and which mandated_breaks can start. The operator proposes a reminder in Slack when the work_period is about to pass.

    With Homebase, Slack

  • Flag skipped breaks from When I Work attestations

    Break attestations with taken false and shift-breaks marked skipped are set against the site rule. The operator proposes a premium-pay flag per shift for the manager to approve in Microsoft Teams.

    With When I Work, Microsoft Teams

  • Write a Dayforce pay adjustment for a missed meal

    Punches with 7shifts missed_break flags, or Dayforce EmployeePunches with no break inside the schedule's Breaks window, become a proposed EmployeePayAdjustment with IsPremium, checked with isValidateOnly.

    With 7shifts, Dayforce

  • Send a premium line to ADP Workforce Now

    Closed shifts with a short or late break become a proposed pay data line through pay-data-input.modify, for the manager to approve before the payroll batch.

    With ADP Workforce Now, Slack

Requirements

  • A time and attendance connector that records breaks on punches: 7shifts, Homebase, When I Work, or Dayforce
  • A break rule per site: length, the hours of work after which it is due, and whether it is paid, set in the operator's configuration
  • Slack or Microsoft Teams for reminders and approvals
  • Optional: a payroll connector that accepts a premium line: Dayforce, ADP Workforce Now, or Paylocity
Authentication
Holds no credentials. Punches and breaks are read, and premiums proposed, through the connectors you bind, under the access each of them carries.

Limits

  • It applies the rule you set per site. It carries no table of meal and rest law by state or country
  • Reminders need a live punch. Homebase timeclock status and When I Work punch state are polled, so a reminder can lag the break falling due
  • A break the system auto-deducted is not a break taken. The operator flags auto_deducted and attested-skipped breaks separately and never counts them as compliance
  • A premium is a proposal to payroll. Whether it is owed is decided by your manager and your payroll rules, not by the operator

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 Break Compliance ↗

Questions and answers

What arrives for approval?
Two things. A reminder, sent to the manager on duty, who passes it on or ignores it. And a premium-pay flag on a closed shift, showing the punch, the breaks recorded, the rule, and the shortfall, which they approve, edit, or reject before anything reaches payroll.
What does the record show?
Per shift: the punches and breaks read, the rule applied, what was proposed and when, the manager's answer, and the pay adjustment as payroll accepted it. Reminders are logged with the time they were sent.
Does it pay a premium on its own?
No. A flag is a proposal until a manager approves it, and it reaches payroll as a line for your payroll team to include. The operator does not message employees directly; reminders go to the manager on duty.
Ask about Break Compliance

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