Email-driven grievances missed union deadlines; ServiceNow case management enforced milestones and role-based access

Overview

A unionized utility company managed employee grievances with paper files and email chains, so contractual timelines slipped and records were hard to trust. Evidence lived in shared folders, letters were drafted from old versions, and union representatives received updates inconsistently. Intelligex implemented a grievance management system with role?based access, milestone calculations per collective bargaining agreement (CBA), evidence collection, and structured collaboration with union reps under controlled access. Grievance steps were met more consistently, documentation became complete and searchable, and HR, Operations, Legal, and the unions worked from the same record—while the HRIS, identity provider, email, and calendaring tools stayed in place.

Client Profile

• Industry: Utilities (generation, transmission, and field services)
• Company size (range): Multi?site operations with several bargaining units
• Stage: Paper files and spreadsheets for grievances; email for union exchanges; inconsistent letter templates; ad hoc deadline tracking per manager
• Department owner: Human Resources & People Ops (Employee & Labor Relations)
• Other stakeholders: Union representatives and stewards, Operations leaders, Legal, Payroll, Safety, IT/Identity, Security & Privacy, Internal Audit, Risk/Compliance

The Challenge

CBA timelines were strict, but tracking depended on memory and inboxes. Step meetings were scheduled by email, letters were cut from old documents, and extensions were negotiated informally. When staff changed or a manager went on leave, handoffs stalled. Missed filing or response deadlines invited disputes about timeliness that overshadowed the merits of a grievance.

Evidence was fragmented. Photos from field incidents, badge access logs, and witness notes lived in personal or shared folders with inconsistent naming. HR redacted sensitive information case by case, and union reps received attachments that sometimes included information beyond what policy allowed. Preparing for arbitration meant reconstructing history from paper files and mail threads.

Multiple CBAs compounded complexity. Each bargaining unit had different steps, triggers, and response windows. Holidays and site?specific schedules affected due dates. Without a system that encoded these differences and calculated milestones automatically, teams relied on spreadsheets and reminders that drifted with each case.

Why It Was Happening

There was no dedicated workflow for grievances. The HRIS tracked people, not CBA timelines or step gates. Paper files and email made it fast to act in the moment but impossible to enforce consistent templates, privacy boundaries, or approvals. Union collaboration required sending documents rather than granting controlled visibility.

Ownership and timing were unclear. Managers, stewards, HR, and Legal each had roles at different steps, but the process depended on “who remembered” instead of a system that assigned tasks with due dates. Extensions and settlements were handled as side conversations, so the official record lagged behind reality.

The Solution

Intelligex deployed a grievance management system that centralized cases, calculated deadlines from the relevant CBA, and enabled controlled collaboration with union representatives. Case intake captured the triggering event, bargaining unit, and timelines, then generated step tasks with due dates, letters from approved templates, and evidence requests. Role?based access limited who could see what, union reps received a secure view of their cases, and escalations to Legal required approvals. Evidence lived in a secure vault with redaction in outbound communications. The solution leveraged an existing case platform (for example, ServiceNow HR Service Delivery) and aligned collaboration with labor practices referenced by bodies such as the NLRB and mediation resources like the Federal Mediation & Conciliation Service.

• Integrations: HRIS for employee, supervisor, location, and bargaining unit; identity provider for single sign?on and role mapping; email and calendar for meeting invites; optional e?signature for settlements (for example, DocuSign); secure document storage for evidence and letters.
• Milestone engine: CBA?aware timeline calculations; site calendar and holiday adjustments; extension capture with new due dates and union acknowledgement.
• Templates and correspondence: Approved letters per step, bargaining unit, and jurisdiction; merge fields for dates, names, and case facts; version control and audit of what was sent when.
• Evidence management: Structured upload requests with accepted formats; chain?of?custody metadata; automatic redaction previews for sensitive fields before sharing; tagging for quick retrieval at arbitration.
• Union collaboration: Controlled access for designated reps and stewards to view case status, letters, and agreed evidence; comment threads logged with timestamps; optional read receipts for key communications.
• Approvals and escalations: Legal checkpoints for arbitration requests, withdrawals, or settlements; maker?checker for remedy offers; reason codes documented for deviations from standard process.
• Dashboards and reporting: Cases by step and unit; items at risk by due date; extension history; settlement terms and implementation tasks; exportable case packets for audit and arbitration.
• Security and retention: Role?based access; encryption in transit and at rest; case?type retention schedules; immutable logs of access, edits, and exports.

Implementation

• Discovery: Cataloged CBAs, steps, and response windows; inventoried letter templates and settlement formats; mapped evidence sources and redaction needs; reviewed union collaboration patterns and privacy constraints; gathered audit expectations.
• Design: Authored the data model for grievances, steps, and extensions; defined the milestone engine with holiday and site calendar rules; curated letter templates per unit; designed union access roles; planned Legal checkpoints, dashboards, and evidence exports; set retention and redaction policies.
• Build: Configured case types and workflows; implemented the milestone engine and extension capture; loaded and versioned templates; enabled union?side views with controlled permissions; wired HRIS lookups, calendar invites, and secure document storage; instrumented audit logs.
• Testing/QA: Ran in shadow mode mirroring active cases; validated due?date calculations across units and sites; exercised extensions, settlements, and arbitration escalations; tested redaction previews and union access; tuned template language and notifications with HR and Legal.
• Rollout: Piloted with one bargaining unit and a few operating districts; migrated in?flight cases; expanded unit by unit after stable cycles; retained paper files as read?only archives during transition; tightened permissions and retired legacy templates as adoption grew.
• Training/hand?off: Delivered guides for HR, managers, and union reps on roles, timelines, and evidence handling; briefed Legal on checkpoints and exports; updated SOPs for extensions, settlements, and arbitration; transferred ownership of templates, calendars, and dashboards to Employee & Labor Relations under change control.
• Human?in?the?loop review: Established recurring reviews with HR, Operations, Legal, and union leadership to examine missed?deadline risks, template clarity, and remedy consistency; recorded decisions with rationale and effective dates; fed updates back into timelines, templates, and roles.

Results

Grievance steps were executed on schedule with fewer surprises. The system calculated deadlines per CBA, adjusted for site calendars, and prompted for extensions with acknowledgements. Letters used current, approved language, and evidence lived in one place with redaction controls. Union reps saw status without being emailed entire file sets, and meeting invites reflected the right step and participants.

Records became reliable. Each case carried intake, correspondence, evidence, approvals, and outcomes with timestamps, making audits and arbitration preparation straightforward. Settlements translated into tracked implementation tasks so remedies did not linger. The utility kept its HRIS, identity, email, and calendars; the change added an orchestration and governance layer that made a paper?heavy process predictable.

What Changed for the Team

• Before: Paper files and inboxes drove timelines. After: A milestone engine calculated due dates and sent step tasks with owners.
• Before: Letters were edited from old versions. After: Templates were versioned per bargaining unit with merge fields and an audit trail.
• Before: Evidence sat in personal folders. After: A secure vault stored documents with redaction and chain?of?custody metadata.
• Before: Union reps received ad hoc emails. After: Controlled access let reps view status and correspondence without oversharing.
• Before: Extensions and settlements were informal. After: Extensions, approvals, and settlement terms were captured with reason codes.
• Before: Arbitration prep rebuilt history. After: Exportable packets contained the complete record by step and outcome.

Key Takeaways

• Encode CBA timelines; let a system calculate due dates and owners rather than relying on memory.
• Centralize evidence; redaction and chain?of?custody are easier when files live in one secure vault.
• Standardize correspondence; approved templates reduce disputes about wording and intent.
• Collaborate without oversharing; provide controlled access for union reps instead of emailing whole files.
• Gate high?risk moves; use Legal checkpoints and reason codes for settlements and arbitration escalations.
• Integrate, don’t replace; keep HRIS, identity, email, and calendars—add case workflows, timelines, and governance.

FAQ

What tools did this integrate with? The grievance system ran on the company’s case platform (for example, ServiceNow HR Service Delivery) and pulled employee, supervisor, location, and bargaining unit from the HRIS. Identity and single sign?on governed access. Email and calendar integrations handled meeting invites, and a secure repository stored evidence and letters. Optional e?signature supported settlements.

How did you handle quality control and governance? CBA timelines, holiday calendars, and templates lived under change control with Employee & Labor Relations and Legal as owners. Maker?checker applied to remedy offers and arbitration escalations. Each communication and deadline change captured who approved it and why. Immutable logs recorded access, edits, and exports; dashboards surfaced items at risk and extension patterns for review.

How did you roll this out without disruption? The team mirrored active cases in shadow mode to validate timelines and templates. A pilot with one bargaining unit ran live while paper files remained the reference. After tuning, additional units onboarded in waves, and legacy templates were retired with clear communications and quick guides for managers and union reps.

How were different CBAs and site calendars handled? The milestone engine selected a ruleset by bargaining unit and location, then adjusted for site calendars and holidays. Extensions were recorded with new due dates and acknowledgement. Updates to CBAs or calendars followed change control with effective dates, and existing cases recalculated only when policy allowed.

How did you protect privacy while collaborating with unions? Union reps and stewards received role?based access limited to their cases. Outbound communications used redaction for sensitive fields, and evidence sharing followed need?to?know rules. All documents were encrypted in transit and at rest, and every view or download was logged.

How did settlements and remedies translate into action? Approved settlements created implementation tasks for Operations, Payroll, or Safety with due dates and owners. Completion was tracked in the same case record, so remedies did not linger off to the side in emails or spreadsheets.

What if a grievance proceeds to arbitration? The case exported a complete packet—intake, correspondence, evidence, timelines, extensions, and approvals—ready for counsel and the arbitrator. References to general arbitration resources, such as the FMCS arbitration program, informed template design and step sequencing without dictating strategy.