Reference · built on requestOperator by FibricWorkforce & scheduling

Overtime Guard

Projects hours from punches plus remaining scheduled shifts and proposes swaps before an employee crosses an overtime threshold.

Request accessPricing ↗

About

Overtime Guard is an operator job that runs during the work week, not after it. It reads the punches an employee has already worked from your time and attendance system, the shifts still ahead of them on the published schedule, and the daily and weekly thresholds your scheduling system holds. For each employee it adds worked hours to scheduled hours and finds the day and the shift where the total crosses a threshold.

Before that shift starts, it names a swap: a colleague who is eligible for the shift and still under the threshold. The manager approves the swap in Slack or Microsoft Teams. The swap is then requested in the scheduling system once, and the projection behind it is kept with the shift.

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

  • Time punches with clocked_in and clocked_out and their breaks: 7shifts time_punches, When I Work times, Deputy Timesheet records, Homebase timecards
  • Published shifts still ahead in the week: 7shifts shifts, When I Work shifts with published, Deputy rosters, Dayforce EmployeeSchedules by employee
  • Overtime thresholds as the scheduling system holds them: 7shifts labor_settings with daily_overtime_threshold and weekly_overtime_threshold, When I Work account overtime thresholds
  • Hours already classified as overtime: When I Work hour stats with regular, dailyOt, and weeklyOt per entry
  • Who may take a shift: When I Work eligible users for a shift and swapusers for a dropped shift, Deputy rosters available for swap
  • Punch and shift changes as they happen: 7shifts time_punch.created and time_punch.edited webhooks, Deputy webhooks on Timesheet and Roster

Proposed actions

  • Target capability: propose a projection per employee: hours worked, hours scheduled, the threshold, and the shift that crosses it
  • Target capability: propose swapping the crossing shift to a colleague under the threshold: a When I Work swap request, Deputy RosterSwap, or 7shifts shift update
  • Target capability: propose shortening the crossing shift, as an Update Shift in 7shifts or When I Work, or a PATCH to Dayforce EmployeeSchedules
  • Target capability: propose a message to the site manager in Slack or Microsoft Teams with the projection and the swap to approve

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

What you can build

  • Swap a shift in When I Work before weekly overtime

    Times and published shifts give the projected total against the account's weekly threshold. The operator lists swapusers for the crossing shift and proposes a swap request, which the manager approves in Slack.

    With When I Work, Slack

  • Read thresholds from 7shifts labor settings

    Daily and weekly thresholds and consecutive_days_threshold come from labor_settings. Time punches and shifts per location give the projection, and the operator proposes an Update Shift to trim the crossing shift.

    With 7shifts, Microsoft Teams

  • Propose a Deputy RosterSwap

    Timesheets and rosters give worked and scheduled hours per employee. The operator names a roster available for swap and proposes a RosterSwap, whose Status the manager and both employees still move themselves.

    With Deputy, Slack

  • Trim a Dayforce schedule

    EmployeePunches and EmployeeSchedules by employee give the week to date and the week ahead. The operator proposes a PATCH to the crossing schedule, validated first with isValidateOnly, for the manager to confirm.

    With Dayforce, Microsoft Teams

Requirements

  • A time and attendance source with punches: Deputy, 7shifts, When I Work, Homebase, or Dayforce
  • A scheduling source with published shifts for the coming days, from the same system or one the operator can map employees across
  • Overtime thresholds: read from 7shifts labor settings or When I Work account settings, or set per site in the operator's configuration
  • Slack or Microsoft Teams for the manager's approval
Authentication
Punches and schedules are read, and swaps requested, through the connectors you bind, under the access each connector holds; the operator keeps no credentials of its own.

Limits

  • It projects from published shifts. Unpublished drafts and open shifts are not counted unless you ask for them
  • The threshold comes from your scheduling system or your configuration. The operator holds no table of overtime law by jurisdiction
  • Where the time system is read-only, as with a Homebase public key, the swap is proposed as a list for the manager to enter
  • Deputy and When I Work swaps carry pending states until the colleague accepts; the operator reports those states rather than forcing them

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 Overtime Guard ↗

Questions and answers

What is the manager shown?
One proposal per employee and week: the projected total, the threshold, the shift that crosses it, and the colleague named to take it. The manager approves the swap, edits it, or declines. Nothing changes in the schedule until they answer.
What is kept afterwards?
The projection with the punches and shifts it was built from, the threshold used, the proposal, who approved it and when, the swap or shift update as the system accepted it, and how to reverse it.
Does it move a shift on its own?
No. It proposes a swap or a trim and waits. It also does not change pay rules or classify hours; overtime is still calculated by your time and payroll systems.
Ask about Overtime Guard

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