Reference · built on requestOperator by FibricWorkforce & scheduling

Training Due

Tracks assigned training due dates against the schedule and proposes paid time in an upcoming shift to complete it.

Request accessPricing ↗

About

Training Due is an operator job for training that is assigned but not done. It reads each employee's assigned training and its due date from the system that holds it: BambooHR training types marked required with a due date counted from hire, HiBob's Training table with a status and an end date, or Deputy training records. It reads the employee's upcoming shifts and the hours each one holds.

For training due before or soon after a shift, it proposes a block of paid time inside that shift: the shift, the start and length, and the training it covers. The manager approves the block. It is then written to the schedule where the system carries notes or activities, and the employee is told in Slack or Microsoft Teams.

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

  • Required training and when it is due: BambooHR training types with required, dueFromHireDate, renewable, and frequency; training records with completed per employee
  • Training entries with status and dates: HiBob training entries with name, status, startDate, endDate, and frequency
  • Training records and modules: Deputy TrainingRecord with TrainingDate and ExpiryDate, TrainingModule with TimeRequiredDays
  • Upcoming shifts per employee: 7shifts shifts, When I Work shifts with notes, Deputy rosters, Dayforce EmployeeSchedules with Activities
  • Hire dates, for training due from hire: BambooHR employee records, HiBob work and lifecycle tables
  • Completions as they are recorded, by re-reading the training records on each pass

Proposed actions

  • Target capability: propose a paid training block inside a named upcoming shift, with the training, the length, and the shift's remaining hours
  • Target capability: propose the block on the schedule: a When I Work shift notes update, or a Dayforce EmployeeSchedules PATCH carrying an Activity
  • Target capability: propose a message to the employee and their manager in Slack or Microsoft Teams with the block and the training link
  • Target capability: propose a weekly list per team of training past due, with the shifts where time could be found

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

What you can build

  • Place BambooHR required training inside a 7shifts shift

    Training types with required and dueFromHireDate give each new hire a due date. The operator proposes a block in the next 7shifts shift with enough hours and posts it to the manager in Slack.

    With BambooHR, 7shifts, Slack

  • Add a Dayforce Activity for a HiBob training entry

    Training entries whose status is short of complete and whose endDate is ahead are matched to EmployeeSchedules. The operator proposes an Activity in the schedule for the manager to confirm.

    With HiBob, Dayforce

  • Use Deputy training records and rosters

    TrainingModule TimeRequiredDays and TrainingRecord dates give what is due. The operator proposes a block in an upcoming roster and tells the employee in Microsoft Teams once the manager approves.

    With Deputy, Microsoft Teams

  • Report past-due training by team

    Each week the operator lists training past due per team from HiBob, with the When I Work shifts where a block would fit, for managers to act on.

    With HiBob, When I Work, Slack

Requirements

  • A source of assigned training and due dates: BambooHR training, HiBob's Training table, or Deputy training records
  • A scheduling connector with the employee's upcoming shifts: 7shifts, When I Work, Deputy, or Dayforce
  • Slack or Microsoft Teams to tell the employee and the manager
  • Optional: a hire date source where training is due from hire, such as BambooHR or HiBob
Authentication
Training records and schedules are read, and blocks proposed, through the connectors you bind, each under its own access, with no credential held by the operator.

Limits

  • The catalog has no learning management connector today; training is read from HR and scheduling systems, and your training platform is linked on request
  • It proposes time, not training. The course is delivered by your training platform, and completion counts once a system the operator reads records it
  • A block needs a shift with room. Where the schedule is full, the operator reports the training as unplaced rather than extending a shift
  • Where the scheduling system carries no note or activity on a shift, the approved block goes to the scheduler as a message to enter

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 Training Due ↗

Questions and answers

What is the manager asked to approve?
A block of paid time: the employee, the shift, the start and length, and the training it is for. The manager approves it, moves it to another shift, or declines. Nothing is added to the schedule until then.
What stays on the record?
The training record read, the due date, the shift chosen and why, the approval with name and time, the schedule entry or message as sent, and the completion when it is later read.
Does it assign training or mark it complete?
No. Assignment and completion stay in the training or HR system. The operator reads them, proposes time, and reports what is still open. Whether the time is paid is a policy you set.
Ask about Training Due

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