Managing a Unionized Workforce Is Different. Your Software Should Be Too.

A grievance lands in your inbox on a Thursday afternoon. A maintenance worker says he was passed over for an open position that, under the CBA, should have gone to the most senior eligible employee in his classification. HR has to pull the contract language, cross-reference the seniority list, figure out whether bumping rights apply, document the whole thing, and track it through a multi-step resolution process — all while the clock on the SLA is ticking.

This is the daily reality for HR teams and operations managers at unionized organizations. And it is a reality that most workforce software has never adequately addressed. The tools are built for non-union environments — clean, simple, no layered obligation structures — then sold to employers where every scheduling decision, every job posting, every overtime hour is governed by a contract. The gap shows.

Three releases this week address that gap directly.

When Overtime Isn't Just a Number

In a non-union shop, overtime is simple: hours worked beyond 40, paid at 1.5x. In many union environments, overtime is a currency. It accrues into a bank. Employees elect whether they want it paid out or held. Different classifications have different conversion multipliers. Banked hours expire on a rolling basis under FIFO rules. Payout requests go through an approval workflow. And all of it has to be documented for compliance audits.

Most time-and-attendance systems treat this as a notes field problem — you note the agreement, then manage the complexity manually in a spreadsheet. The Banked Time Management release takes a different approach: configurable conversion multipliers per agreement, employee-level pay-vs-bank elections, payout workflows with approval steps, FIFO rolling expiry enforcement, and compliance reports built in.

The reason this matters is not efficiency. It is liability. When an employee claims their bank was miscalculated — or that they elected payout but it never happened — the employer needs a clear record of every election, every conversion, every balance change. A spreadsheet does not provide that. A system that treats banked time as a first-class concept does.

The CBA Is Not a Document. It Is a Rule Engine.

When a job opens at a unionized facility, the CBA often dictates who gets first rights to it. Seniority-based bumping provisions mean that a senior employee in a related classification may have the right to claim the role before it's posted externally — or even before junior employees in the same classification. Getting this wrong is not a process failure. It is a grievable offense.

HR teams at unionized employers often carry the CBA mentally, applying its rules informally because there is no system that knows the contract exists. The CBA Planner changes that model. Admins can define CBA eligibility rules and classification structures, simulate seniority-based bumping scenarios before a decision is made, and automatically notify union members when internal postings go live — so the contractual notification obligation is met without a manual step.

The simulation piece is worth pausing on. Bumping rights are not always obvious. A senior employee in classification A may have the right to bump into classification B based on a cross-training agreement, but only if they have the required certifications and have been in their current role for a minimum period. Running through those conditions manually before every internal posting is time-consuming and error-prone. Having a system that can model the scenario first — showing you who has rights before you post — reduces both the administrative burden and the grievance risk.

Grievances Need a Home, Not a Shared Inbox

When a union member files a formal grievance, what happens next is usually one of two things: it lands in someone's email, or it gets a ticket in a general help desk system that was never designed for labor relations. Either way, there is no structure around it. Stages are tracked in a spreadsheet. SLA deadlines are managed by whoever remembered to set a calendar reminder. The audit trail is whatever email chain survives.

Grievance Tracking in Service Desk brings a dedicated workflow to this process: configurable stages, per-stage SLA deadlines, designated approvers at each stage, a stage-stepper UI that shows exactly where each case stands, and a full audit trail. The audit trail is not a nice-to-have — it is the record that matters if a grievance escalates to arbitration.

What makes this particularly useful is that it lives in the same system as the rest of workforce operations. A grievance that relates to an overtime bank discrepancy, a bumping-rights dispute, or a missed posting notification can be linked to the underlying records — because those records now exist in the system as well.

The Rest of the Week

Beyond the union workforce releases, two other areas saw meaningful updates.

Performance management picked up a pair of improvements. HR admins can now organize review campaigns into named Performance Cycles — grouping multiple review configurations under a single cycle and creating all employee reviews in one action rather than one at a time. And Post-Review Surveys can now be automatically triggered when a review is approved, sent to the employee, the reviewer, or both. These are process improvements that reduce the manual coordination load around review season without changing how the reviews themselves work.

On the AI side, Ask AI is now available directly in the MangoApps Chrome extension — with conversation history, suggestion chips, and awareness of the current page context. For employees who live primarily in a browser, this removes the need to navigate to a separate tool to ask a question.

What This Week Points To

Workforce software has historically been built for the median employer. That median employer has relatively uniform pay structures, simple overtime rules, no contract obligations governing internal job postings, and no formal grievance process. The tools reflect those assumptions.

But a significant portion of the workforce operates under collective bargaining agreements — in healthcare, manufacturing, logistics, utilities, education, and public services. For these employers, the gap between what workforce software does and what the CBA requires has been filled by spreadsheets, manual workarounds, and institutional knowledge held by a few people who know the contract well enough to apply it correctly.

Three releases in a single week targeting banked time, seniority-based bumping, and grievance tracking is a signal about where the product is heading. The goal is not to add union-specific features as an add-on. It is to build a platform where the obligations embedded in a labor agreement can be codified, enforced, and audited — the same way scheduling rules, leave policies, and compliance requirements already are.

For HR leaders and operations managers at unionized organizations, that is a meaningful shift.