Reference · built on requestOperator by FibricWorkforce & scheduling

Certification Expiry

Matches license and certification end dates to upcoming shifts and proposes a reassignment or renewal task before the lapse.

Request accessPricing ↗

About

Certification Expiry is an operator job for roles that cannot be worked without a current credential. It reads each employee's certifications and licenses with their end dates from the system that holds them: Deputy training records with an ExpiryDate, BambooHR training types that renew on a frequency, the Training table in HiBob, or a register you keep in a sheet. It reads the shifts scheduled for those employees and the role each shift requires.

Where a credential ends before a shift that needs it, it proposes two things. A reassignment of the shift to an employee whose credential is current, for the scheduler to approve. And a renewal task for the employee's manager, created in your work tracker, with the end date and the shifts at stake.

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

  • Training and certification records with expiry: Deputy TrainingRecord with Module, Employee, TrainingDate, ExpiryDate, and Active
  • Renewable training types and completions: BambooHR training types with renewable, frequency, and required, and training records with a completed date
  • Training table entries per employee: HiBob training entries with name, startDate, endDate, and frequency
  • A credential register you keep: a range in Google Sheets or Microsoft Excel with employee, credential, and end date
  • Scheduled shifts and the role each requires: Deputy rosters, 7shifts shifts by role, When I Work shifts by position, Dayforce EmployeeSchedules by job
  • Employees and their roles or positions, for the pool of possible replacements

Proposed actions

  • Target capability: propose reassigning the shift to an employee whose credential is current: a Deputy roster change, a 7shifts or When I Work shift update
  • Target capability: propose a renewal task for the employee's manager in Jira, Asana, or monday.com, with the end date and the shifts affected
  • Target capability: propose a list per site of credentials ending inside the scheduling horizon, and the shifts each one blocks
  • Target capability: propose retiring the expired record once the renewal is entered, as a step for the manager in the system that holds it

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

What you can build

  • Reassign a Deputy shift before a training record expires

    TrainingRecord rows with an ExpiryDate inside the roster horizon are matched to rosters whose area needs that module. The operator proposes a replacement employee with an Active record for the scheduler to approve.

    With Deputy, Slack

  • Open a renewal task from BambooHR

    Training types with renewable true give a due date from completed plus frequency. Where it falls before a 7shifts shift in a role that needs it, the operator proposes a Jira issue for the manager.

    With BambooHR, 7shifts, Jira

  • Work from a HiBob Training table

    Training entries with an endDate and frequency are read per employee. The operator proposes an Asana task for each entry ending inside the When I Work schedule window, with the shifts listed.

    With HiBob, When I Work, Asana

  • Keep a license register in a sheet

    A range with employee, license, and end date is read each day. Where an end date precedes a Dayforce schedule for that job, the operator proposes a schedule change and a renewal task.

    With Google Sheets, Dayforce, Asana

Requirements

  • A source of certification or license end dates: Deputy training records, BambooHR training, HiBob's Training table, or a sheet
  • A scheduling connector whose shifts carry a role, position, or job: Deputy, 7shifts, When I Work, or Dayforce
  • A mapping from credential to the roles that need it, set in the operator's configuration
  • Optional: Jira, Asana, or monday.com for renewal tasks, and Slack or Microsoft Teams for the scheduler's approval
Authentication
Carries no credentials of its own. Records and schedules are read, and shifts and tasks proposed, through the connectors you bind and the access each holds.

Limits

  • It reads end dates as recorded. A renewal completed but not entered still reads as expired until someone updates the record
  • No learning management connector is in the catalog. Fibric links your training platform on request; until then, records come from HR or scheduling systems
  • BambooHR training records carry a completed date, not an expiry; the operator derives the due date from the type's frequency and says so
  • It does not judge whether a credential is valid, only whether its recorded end date falls before a shift that requires it

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 Certification Expiry ↗

Questions and answers

What does the scheduler decide?
A reassignment: the shift, the employee whose credential ends, the end date, and the replacement proposed with their credential's status. The scheduler approves, picks someone else, or declines. The schedule does not change until then.
What is kept on the record?
The credential record read and its end date, the shifts matched, the reassignment or task proposed, the approval with name and time, and the shift or task as the system created it, with a way to reverse it.
Does it renew or update a certification?
No. Renewal is a task for a person. The operator proposes the task, and once the new record exists it proposes retiring the old one, which a manager does in the system that holds it.
Ask about Certification Expiry

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