Reference · built on requestOperator by FibricWorkforce & scheduling

Swap Review

Checks each swap or drop request against overtime, rest gap, credential, and notice rules and proposes the decision with its evidence.

Request accessPricing ↗

About

Swap Review is an operator job for the requests employees raise between schedules. When a swap or drop appears in your scheduling system, it reads both shifts and both employees, the hours each has worked and scheduled in the period from your time system, the credential the shift's role needs, and the rules you wrote for the site: the overtime threshold, the minimum gap between shifts, and how much notice a request needs.

The manager receives a verdict with every check and its result, accepts or overrides it, and the approved swap is applied to the schedule once. The employee gets a reply naming the rule behind a decline, and the request record keeps the checks and the decision.

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

  • Swap and drop requests as employees raise them: When I Work /2/swaps with swaps::created and swaps::updated, Deputy RosterSwap records, Rippling shift assignments
  • Both shifts and both employees: When I Work /2/shifts, Deputy Roster/QUERY, 7shifts shifts by user, with role, location, start, and end
  • Hours worked and scheduled in the period for each party: When I Work /2/times, Deputy timesheets, QuickBooks Time timesheets, Homebase timecards
  • Qualification for the shift's role: When I Work positions, 7shifts roles, Deputy TrainingRecord with ExpiryDate, HRIS job codes from UKG Pro or Dayforce
  • The rules you set per site: the minimum gap between shifts, daily and weekly caps, and the notice a request needs before the shift starts
  • Manager answers on the reviews it posts in Slack or Microsoft Teams

Proposed actions

  • Target capability: propose a decision for each request: approve, decline, or approve with a condition, with every rule checked and its result shown
  • Target capability: propose applying an approved swap: a When I Work swap update, a Deputy supervise/roster update, or a 7shifts shift update moving the user
  • Target capability: propose a reply to the requesting employee stating the decision and, for a decline, the rule behind it
  • Target capability: propose a cover offer for a drop that leaves the shift open, handed to the open-shift sequence
  • Target capability: propose a note on the request record with the checks performed and who decided

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

What you can build

  • Review When I Work swaps before they are taken

    swaps::created triggers the checks: hours from /2/times, the position on the shift, your gap rule. The manager sees the verdict in Slack, and an approved swap is proposed as a swap update.

    With When I Work, Slack

  • Check Deputy RosterSwap against training expiry

    Each RosterSwap is checked against the taker's TrainingRecord for the area and their rostered hours this week. Expired training declines with the module named; an approval is proposed through supervise/roster.

    With Deputy, Microsoft Teams

  • Judge a 7shifts drop with QuickBooks Time hours

    A dropped shift is checked for notice against your window, and the taker's hours come from QuickBooks Time timesheets. The manager approves in Microsoft Teams, and a shift update moves the user.

    With 7shifts, QuickBooks Time, Microsoft Teams

Requirements

  • A scheduling connector that exposes swap or drop requests: When I Work, Deputy, or Rippling; 7shifts for the shifts a request refers to
  • A time source for hours in the period: the same system's timesheets or punches, QuickBooks Time, or Homebase
  • A credential source where roles need one: Deputy TrainingRecord, When I Work positions, 7shifts roles, or HRIS job codes
  • Slack or Microsoft Teams for the manager's answer
  • Per site: the overtime threshold, the minimum gap between shifts, and the notice window
Authentication
Holds no credentials. Requests, shifts, hours, and credentials are read through the connectors you bind, and writes go through the same connectors under the scopes they hold.

Limits

  • It applies the rules you write down. Where the scheduling system already enforces a rule, it shows that system's answer rather than a second opinion
  • Overtime is counted from hours the time system holds at review time; a late punch changes the picture, and the record shows what was known
  • A swap completed by employees before the manager answered, as When I Work allows, is reported as already applied with its rule results, not reversed
  • Pay rates and premiums are not computed; a swap that changes cost is flagged with hours, not money

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 Swap Review ↗

Questions and answers

What does the manager see and approve?
A verdict per request with the evidence: hours before and after for both employees, the credential check, the gap between shifts, and the notice given. The manager accepts the verdict or overrides it; only then is the swap written.
What record is left?
The request id, both shifts, each rule and its result, the hours the time system reported at review time, the manager's decision, the write to the scheduling system, and the message sent to the employee.
Does it ever approve a swap itself?
No. It recommends. If your scheduling system lets employees complete a swap without a manager, the operator reports the completed swap and its rule results rather than undoing it.
Ask about Swap Review

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