Reference · built on requestOperator by FibricWorkforce & scheduling

Shift Skills

Checks every shift for the roles a site must staff, such as a keyholder or a first aider, and proposes a swap where one is missing.

Request accessPricing ↗

About

Shift Skills is an operator job for the rule that says who must be on site. It reads the draft schedule per site and interval, the training and credential records your systems hold, with their expiry dates, and the HRIS job and status that say whether a credential still belongs to someone at that site. Against that it checks the coverage rule you wrote: one keyholder at open and close, one first aider whenever the doors are open, however you define it.

Every interval that fails becomes a proposal: a swap or an added assignment that puts a credentialed employee on it, or an open shift for the role where nobody credentialed is free. A credential expiring inside the window raises a renewal task. The scheduler approves each fix, and the record names the credential relied on.

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

  • Shifts per site and interval: Deputy rosters by area, 7shifts shifts by location and role, When I Work shifts by position, Quinyx /schedule/v3/shifts by group
  • Who holds which credential and until when: Deputy TrainingRecord with TrainingDate and ExpiryDate against TrainingModule, HiBob Training table entries, Connecteam user custom fields, 7shifts roles
  • HRIS job and status, so a credential on a terminated or transferred employee stops counting: UKG Pro employment-details, BambooHR employees/changed, Workday staffing
  • The coverage rule per site: which roles must be present, during which hours, and how many
  • Hours and availability of candidates who could fill a gap, from the same scheduling system
  • Scheduler answers on the proposals it posts in Slack or Microsoft Teams

Proposed actions

  • Target capability: propose the gap list per site and day: the interval, the role missing, and which credentialed employees are scheduled nearby or available
  • Target capability: propose a swap or added assignment putting a credentialed employee on the interval, as a Deputy, 7shifts, or When I Work shift update
  • Target capability: propose an open shift for the role where nobody credentialed is available, handed to the open-shift sequence
  • Target capability: propose a renewal task when a credential a rule depends on expires inside the schedule window, as a Deputy Journal entry or ticket
  • Target capability: propose a message to the scheduler in Slack or Microsoft Teams listing the gaps and the fixes for approval

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

What you can build

  • Keep a first aider on every Deputy shift

    TrainingRecords for the first-aid module, with their ExpiryDate, are matched to rostered hours by area. Any interval with none is proposed as a swap in Slack, naming the nearest credentialed colleague.

    With Deputy, Slack

  • Cover open and close with a 7shifts keyholder

    Shifts carrying the keyholder role are checked at each location's opening and closing intervals. A missing one proposes a shift update or an open shift for the role, for the scheduler in Microsoft Teams.

    With 7shifts, Microsoft Teams

  • Read HiBob training into When I Work positions

    Training table entries name who holds the credential; When I Work positions mark who is scheduled for it. Where they disagree, the operator proposes the shift change and a note to HR.

    With HiBob, When I Work

  • Drop the credentials of transferred staff

    A change in UKG Pro employment-details removes an employee from a site's credential pool on transfer or termination, and the next pass re-checks that site's Quinyx shifts.

    With UKG Pro, Quinyx

Requirements

  • A scheduling connector with shifts by site and role and a shift write: Deputy, 7shifts, When I Work, or Quinyx
  • A credential source with expiry: Deputy TrainingRecord, a HiBob Training table, Connecteam custom fields, or a list you keep per site
  • An HRIS connector for job and status: UKG Pro, BambooHR, or Workday
  • Slack or Microsoft Teams, where the scheduler answers each fix
  • Per site: the roles that must be present, when, and how many
Authentication
Binds to your connectors rather than holding credentials: shifts, training records, and HRIS status are read, and shift changes written, under the scopes those connectors hold.

Limits

  • A credential is only as current as its record. An expired or missing TrainingRecord counts as absent, and the proposal says so rather than assuming
  • Credentials come from your scheduling system or HRIS tables, since the catalog has no learning management connector; Fibric links an LMS on request
  • Which roles a site must staff, and when, is a rule you write; the operator checks it and never infers a requirement from past schedules
  • It edits draft schedules. After publish a gap is reported and a swap is proposed to the scheduler, not applied

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 Shift Skills ↗

Questions and answers

What does the scheduler sign off?
Each fix: the interval, the missing role, and the swap or assignment proposed, with the employee's credential and its expiry shown. The scheduler can approve it, edit it, or decline it. An open shift for the role is a separate proposal.
What record is left?
The rule checked, the interval, the credential records relied on with their expiry dates, the fix proposed and approved, the write to the scheduling system, and any renewal task raised.
Does it change anything on its own?
No. Draft shifts change only after the scheduler's answer, and published shifts are never edited by the operator. It never marks a credential current or expired either; it reads what your systems hold.
Ask about Shift Skills

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