Workflow recipe

Employee tiers

This recipe explains how to turn attendance and reliability signals into a tier system that affects shift access, approval, coaching, and incentives. The tier should not be a manual label only. It should be connected to shift history, rollups, access filters, and automation.

Operational question

How should performance history affect which workers see shifts and receive priority?

Reference walkthrough

Employee tiers

Use the video as a visual reference, then use the sections below to understand the actual implementation model: data, workspaces, rules, workflow steps, tests, and common failure modes.

6:49

Implementation model

Build the workflow in the same order the operation will depend on it.

A recipe is complete only when the business problem, data model, operator view, policy decision, automated follow-up, and testing path all line up.

Problem

Name the operating gap and the decision the team needs to make.

Data

Identify the records and fields Teambridge must trust.

Workspace

Create the queue where operators review and act.

Policy

Define what should be allowed, blocked, flagged, or ranked.

Workflow

Connect triggers, conditions, messages, updates, and approvals.

Test

Run realistic pass, fail, exception, and permission scenarios.

Data model

Employee Tiers collection with records such as Gold, Silver, and Bronze.
Users with a single-select Employee Tier link.
Shifts with multi-select accepted Employee Tiers.
Attendance fields on Shifts for late, no-show, cancellation, and facility cancellation.
Rollups on Users that count attendance signals from related shifts.

Product example

What schedulers see when open shifts, rules, and worker response come together.

This is useful context for the scheduling sections because it shows the operational surface operators use to move from open work to confirmed coverage.

Open scheduling product page

Teambridge scheduling product visual showing shift coverage workflow

Workspace design

Employee Tiers workspace for tier records and configuration.
Attendance Metrics workspace for late, no-show, cancellation, and trend review.
Workers by Tier workspace for coaching and operational decisions.
Shift Access workspace showing which tiers can claim each shift.
Tier Exceptions workspace for manual review and corrections.

Rules and policy logic

New workers can start in Gold by default or another configured tier.
Late, no-show, and cancellation thresholds can trigger demotion.
Positive attendance or manual review can trigger promotion.
New shifts can open to Gold first, then Silver, then Bronze after delays.
Gold-tier requests can be auto-approved if the business wants that reward.

Workflow sequence

How the process should run

Create tier records.

Link each user to one tier.

Link each shift to one or more accepted tiers.

Track attendance outcomes on shifts.

Roll up attendance counts to the user.

Run automations when rollup thresholds are reached.

Use access group filters or policies so workers see shifts matching their tier.

Review exceptions and coaching queues.

Testing checklist

Create test workers in each tier.
Confirm each worker sees only eligible shifts.
Create late/no-show/cancellation events and verify rollups.
Test tier demotion and promotion automations.
Test delayed shift release from Gold to Silver to Bronze.

Common failure modes

Tier is stored as text instead of a linked record.
Rollups are missing, so tier movement becomes manual.
Workers can still see shifts outside their tier.
Thresholds are not explained to managers or workers.
No exception path exists when a manager needs to override tier logic.