Union Case Management: The Operational Complexity of Grievance Management

UNION SOFTWARE · Whitepaper Series | No. 5 of 12

A detailed operational analysis of the file types, deadline architecture, stage documentation requirements, pattern detection demands, arbitration preparation obligations, and remedy tracking failures that define grievance management in active union offices

Published by Union Software · unionsoftware.com · 2025

Fifth in the Union Software Whitepaper Series. Intended audience: Local presidents, chief stewards, servicing reps, business agents, national and provincial staff, and anyone responsible for grievance administration or oversight. Prior papers in the series provide broader infrastructure context.

Executive Summary

Grievance management is the most operationally complex function a union office performs. It involves more distinct file types, more legally binding deadlines, more information demands at each stage, more consequential decision points, and more downstream obligations than any other union office function. And it is the function where the consequences of inadequate infrastructure are most directly felt by the members the union exists to represent.

This paper maps that complexity in operational detail. It begins with the file type problem: individual grievances, group grievances, policy grievances, discipline files, harassment and human rights files, and health and safety cases are not the same kind of file, do not follow the same process, and do not carry the same information requirements. A case management system that treats them as variations of a single template will fail in characteristic and predictable ways.

The paper then traces the full lifecycle of a grievance file: the intake moment and what must be captured there; the deadline architecture and why missing even a single deadline can end a case regardless of its merits; the step meeting record and what it must contain to be useful at arbitration; the decision log and why withdrawal, settlement, and advancement decisions must be documented as formally as the grievances themselves; and the pattern detection problem — the capacity that most locals lack entirely, and that allows recurring employer violations to continue unaddressed.

Two sections address the back end of the process that most case management discussions underweight: arbitration preparation and remedy tracking. Arbitration preparation is where file quality translates directly into outcome quality — and where the compounding effect of incomplete documentation at every prior stage becomes fully visible. Remedy tracking is where most locals fail entirely: the settlement is signed, the file is closed, and no one confirms that what was agreed was actually done.

The paper concludes with a specification of what adequate case management infrastructure must provide — not as an abstract list of features, but as a direct response to the operational complexity documented throughout.

1. Grievance Management Is More Complex Than It Looks From the Outside

From the outside, grievance management looks like a simple linear process: a member has a problem, the union files a grievance, the parties meet, and the matter is either resolved or goes to arbitration. That picture is accurate in the same way that a street map is accurate — it shows the main roads without showing the traffic, the construction, the detours, or the fact that six different kinds of vehicles are trying to use the same roads simultaneously for different purposes.

The actual operational picture is considerably more complex. At any given time, an active union office is managing a caseload that includes files at every stage of the process simultaneously — new intakes arriving while step meetings are being scheduled, while arbitration prep is underway on older files, while settlements from six months ago are being monitored for remedy implementation. Each file is in a different stage, governed by a different set of timelines under a specific collective agreement, involving different members, stewards, and employer contacts, with different documentation histories and different next steps.

Managing this caseload — keeping every file current, every deadline tracked, every decision documented, every remedy followed through — is the central operational challenge of a union office. It is a challenge that scales with the size and complexity of the local, but that does not become simple even in smaller locals where the caseload is more manageable. A single missed deadline can end a case that was strong on the merits. A single undocumented step meeting can leave a rep unable to advance a file that should have been advanced. A single settlement with no remedy tracking is a settlement that may never be fully implemented.

Principle 1

Grievance management is not a pipeline — it is a portfolio of active files at different stages, each governed by specific timelines, each carrying specific documentation requirements, each connected to a member who is waiting for an outcome. The infrastructure required to manage this portfolio reliably is qualitatively different from what is required to manage a simple, linear workflow. Treating it as a pipeline is the first and most consequential design error in union case management systems.

2. The File Type Problem

The most common design failure in union case management systems — including the spreadsheet-and-email systems that most locals actually use — is treating all grievance files as variations of the same template. In practice, the files that move through a union office are meaningfully different in type, and those differences have direct implications for the process, the timeline, the information requirements, and the handling obligations that apply.

Each row in this table represents a different kind of operational problem. A discipline file that is handled with individual grievance timelines will miss the shorter response windows that most agreements impose on discipline. A harassment file that is not immediately restricted to authorised personnel violates the complainant's right to confidentiality and exposes the union to serious liability. A policy grievance filed without the right filing structure — with a named grievor instead of the union as grievor — may be technically defective.

The file type problem is not solved by telling experienced reps to remember which file type requires which treatment. It is solved by building file-type-specific intake forms, timeline logic, and handling requirements into the case management system so that the right process is triggered automatically from the moment a file is opened.

Principle 2

Not all grievance files are the same kind of file, and case management infrastructure that treats them as variations on a single template will fail in predictable ways — too-slow response to discipline, confidentiality failures in harassment files, technical defects in policy grievances. Purpose-built case management must distinguish file types at intake and apply the appropriate process, timeline logic, and access controls automatically from that point forward.

3. The Intake Moment

The intake moment — the first interaction between the union and a member's workplace problem — is the most consequential single point in the grievance lifecycle. Everything that happens afterward depends on what is captured here. And it is also the moment in the process when the union is under the most time pressure, the least well-positioned to be thorough, and the most reliant on a steward who may have never handled this type of file before.

A steward who takes an intake on the shop floor, between their own work tasks, in the middle of a shift, has minutes — not hours — to gather the information that will govern the entire subsequent process. What collective agreement articles might apply? What is the exact date of the incident, and does the clock start from the incident date or the date of knowledge? Is this individual or group? Does it require immediate escalation because it involves termination, harassment, or a health and safety refusal? Is there physical evidence that needs to be preserved right now, before the shift ends?

What a complete intake must capture

Grievor identity and employment details. Full name, worksite, bargaining unit, classification, shift, and employment status. These are not optional — without them, the file cannot be properly attributed, the applicable collective agreement cannot be identified, and the steward assignment cannot be confirmed.

Incident facts and timeline. What happened, when it happened, where it happened, who was involved, and who witnessed it. The date of the incident — or the date of knowledge if they differ — is critical, because the filing deadline runs from that date. Getting it wrong by one day can mean the difference between a grievable file and one that is out of time.

Relevant collective agreement language. Which articles are potentially engaged? This requires the steward to have quick access to the agreement. An intake system that surfaces the relevant agreement for the member's unit — and allows the steward to tag the articles they believe apply — makes this step faster and reduces the risk that a relevant article is overlooked.

Evidence identified and preservation flagged. What documentary evidence exists — scheduling records, posting notices, pay stubs, discipline letters, email chains, incident reports — and where is it? Evidence that is not identified at intake is evidence that may be lost before anyone comes back for it. The intake form should prompt for evidence identification as a required step.

Remedy sought. What does the grievor want? Money back? Discipline removed? Seniority corrected? The remedy sought at intake is not the final remedy — it can be refined as the file develops — but it is the starting point for the union's position. Failing to record it at intake means reconstructing it later, often from memory.

Urgency flag and escalation trigger. Is this a termination? A health and safety refusal? A harassment complaint? These file types require immediate escalation beyond the steward — to the chief steward, the servicing rep, or in some cases to national or provincial staff. The intake system must prompt the urgency assessment and generate the escalation automatically when triggered.

The intake moment is time-pressured by design — and infrastructure must compensate

The conditions under which most intakes happen — a steward on a worksite, mid-shift, often without access to the collective agreement or a computer — are not conditions that support thorough documentation. The intake form must be simple enough to complete quickly on a phone, structured enough to prompt for what is required, and smart enough to flag urgency and calculate the preliminary deadline automatically. A paper form or a shared spreadsheet cannot do this. The intake moment is where inadequate infrastructure has its first consequence.

Principle 3

The intake moment is the most consequential and most time-pressured point in the grievance lifecycle. Purpose-built case management must support intake in the conditions where it actually happens — mobile-accessible, structured to prompt all required fields, capable of surfacing the relevant collective agreement, and able to calculate and flag the preliminary filing deadline automatically from the incident date. An incomplete intake is not a minor data quality problem — it is a file that starts at a disadvantage and stays there.

4. The Deadline Architecture

Grievance timelines are not guidelines. They are legally binding provisions of the collective agreement, and a grievance that is not advanced within the prescribed timeline is, in most cases, a grievance that cannot be advanced at all — regardless of how strong it is on the merits. The arbitrator does not have discretion to hear a grievance that is time-barred; the deadline is jurisdictional.

This means that deadline management in a union office is not a matter of staying organised — it is a matter of preserving members' right to have their grievances heard. A missed deadline is not an administrative error that can be corrected. It is a permanent loss of the member's recourse, and it is entirely within the union's control to prevent.

The layered deadline structure

What makes grievance deadline management hard is not that there is one deadline per file — it is that there are multiple deadlines at different stages, governed by different provisions of the collective agreement, with different consequences for missing each one. A typical collective agreement creates at least the following deadline obligations on the union's side:

• Filing deadline: the number of calendar or working days from the incident (or knowledge of the incident) within which the grievance must be filed in writing. This is typically the shortest and most unforgiving deadline in the process — often five to fifteen days.
• Step advancement deadlines: after each step meeting, the agreement typically prescribes the number of days within which the union must advance the grievance to the next step or it is deemed withdrawn. These deadlines run from the employer's response, which may itself be late — creating a chain of deadline calculations from documents that may not arrive on time.
• Arbitration referral deadline: the deadline within which the union must refer a grievance to arbitration after the final step denial. This is typically a longer window than the filing or advancement deadlines, but it is no less fatal if missed.
• Extension requests: some agreements allow deadlines to be extended by mutual agreement. Tracking whether an extension has been requested, whether it has been granted, and what the new deadline is requires a separate documentation discipline on top of the original deadline tracking.
• Employer response deadlines: agreements typically prescribe timelines within which the employer must respond at each step. When the employer is late, the union must decide whether to wait or to advance on the original timeline — and that decision must be documented.

Why spreadsheets cannot manage a deadline portfolio

A spreadsheet can track a list of deadlines. What it cannot do is manage the dynamic, cascading nature of a grievance deadline portfolio. When the employer responds to a Step 1 meeting on day seven of a ten-day response window, the Step 2 filing deadline is calculated from that response date — not from the Step 1 meeting date, not from the original filing date. When a grievor is on leave and the timeline is suspended, the spreadsheet does not know that. When three related grievances are merged into a group file, the individual deadlines do not automatically consolidate.

These are not edge cases. They are the routine complexity of grievance administration in any active local. Each one requires a manual calculation and a manual update to the tracking spreadsheet — and each manual step is a point of failure that does not exist in purpose-built case management infrastructure that calculates deadlines dynamically from the underlying process data.

A missed grievance deadline is not an administrative error that can be corrected. It is a permanent loss of the member's right to have their case heard — caused entirely by a failure of infrastructure that the union was in a position to prevent. Purpose-built case management does not miss deadlines. Manual systems do.

Principle 4

Deadline management in grievance administration is a multi-layered, cascading obligation that cannot be reliably managed through manual spreadsheet tracking in an active caseload. Purpose-built case management must calculate deadlines dynamically from process events — filing dates, employer response dates, advancement decisions, extension agreements — surface them before they become critical, and flag them as urgent when they are imminent. This is not an optional convenience feature. It is the core operational requirement of any system that claims to support union grievance administration.

5. The Stage Documentation Requirements

Every stage in the grievance process generates documentation obligations that are distinct from the obligations of every other stage. What must be recorded at intake is not the same as what must be recorded at a Step 1 meeting, which is not the same as what must be recorded at arbitration prep. A case management system that provides a single notes field for the entire file lifecycle is not supporting stage documentation — it is providing a place to put things, which is different.

The documentation obligations in this table are not aspirational standards — they are the minimum required to support a file through its full lifecycle, including arbitration. Each gap in the stage record is a gap in the union's ability to advance the file, respond to employer challenges, and demonstrate to an arbitrator that the process was followed correctly.

The practical implication for infrastructure design is that stage-specific documentation forms — not a single notes field, not a shared document, not an email thread — are a structural requirement for adequate case management. When a steward opens a Step 1 meeting record, they should see the fields that a Step 1 meeting requires: attendees, position presented, employer response, next steps. Not a blank page.

Principle 5

Each stage of the grievance process has distinct documentation requirements that cannot be served by a generic notes field or a shared document. Purpose-built case management must present stage-specific documentation forms that prompt for what is required at that stage, carry forward context from prior stages automatically, and produce a complete, navigable file history that can be used at arbitration without reconstruction. The documentation standard is not what is convenient to record — it is what is necessary to advance the file.

6. The Decision Log

Grievance files are not just records of what happened — they are records of decisions the union made, and those decisions can be questioned by members, by executive boards, and by arbitrators. The decision to withdraw a grievance without settlement, to settle for terms less than the full remedy sought, to advance a weak file to arbitration, or to decline to file at all — each of these is a consequential decision that was made by a person with authority to make it, and each must be documented with the same rigour as the factual history of the case.

The decisions that must be documented

The decision to file or not file. When a member brings a complaint to the union and the union decides not to file a grievance, that decision must be documented — the reasons for it, who made it, when it was made, and whether the member was informed. Undocumented non-filing decisions create serious exposure: if the member later challenges the union's duty of fair representation, the union must be able to demonstrate that the decision was made on a considered, non-arbitrary basis. "We reviewed it and decided it wasn't grievable" is a defensible position. "We have no record of receiving the complaint" is not.

The decision to withdraw. Withdrawing a grievance without settlement closes the file permanently in most cases. The decision to withdraw must be documented with the reasons — the legal assessment, the member's input, the discussion with the executive board if applicable, and the notification to the grievor. A withdrawal that cannot be documented is a decision that cannot be defended.

The decision to settle and on what terms. Settlement decisions are among the most consequential in the grievance file. The union is accepting terms that end the member's recourse on the matter, often in exchange for something less than the full remedy sought. The decision must be documented with the full terms accepted, the reasons the settlement was considered appropriate, whether the member was consulted, and who authorised the settlement on the union's behalf.

The decision to advance to arbitration. Arbitration is expensive and resource-intensive. The decision to advance a file to arbitration should be made consciously — with a review of the file strength, the resources available, the jurisprudential context, and the member's situation — and documented with the same care as the decision to settle or withdraw.

The duty of fair representation makes the decision log a legal document

In Canada and the United States, unions owe their members a duty of fair representation — an obligation to handle members' grievances without arbitrariness, discrimination, or bad faith. When a member files a duty of fair representation complaint, the union's defence depends entirely on its documented decision-making. A union that can produce a complete decision log — showing that each decision was made consciously, on a reasonable basis, with appropriate member communication — is in a defensible position. A union that cannot is not, regardless of how well-intentioned the decisions were at the time.

Principle 6

The decisions made in the life of a grievance file are as legally significant as the facts of the underlying dispute. The decision log — documenting every choice to file, not file, advance, settle, or withdraw — is the union's primary defence against duty of fair representation complaints and member challenges to how their case was handled. Purpose-built case management must treat decision documentation as a required field at each decision point, not an optional addendum to the factual record.

7. Pattern and Group Grievance Management

Individual grievances are the unit of most union case management systems. They are also, in many cases, the wrong unit of analysis for understanding and addressing what is actually happening in a workplace.

Pattern violations — an employer practice that affects multiple members, consistently, in the same way — are among the most important and most difficult categories of workplace problem to address. A supervisor who consistently bypasses the overtime distribution clause. A scheduler who routinely ignores seniority on shift assignments. A manager who issues discipline at a rate and consistency that suggests the discipline is designed to build a case for termination rather than correct performance. Each individual instance of these patterns produces a grievance file. But the pattern itself — the systemic violation that the individual files collectively evidence — is only visible when those files can be seen together.

Why pattern detection fails without infrastructure

In most union offices, pattern detection depends on individual memory. The experienced staff rep who has been working the same employer for ten years knows that this supervisor has a discipline problem, because they have handled three or four files involving that supervisor and remember each of them. The new rep, covering the same employer for the first time, sees only the current file. The pattern is invisible — not because it does not exist, but because it exists in the memory of someone who is not in the room.

This is not a people problem. It is an infrastructure problem. A case management system that allows files to be tagged by employer, worksite, supervisor, article, and issue type — and that allows a user to view all files sharing a given tag — makes pattern detection a routine function rather than a feat of individual memory. The pattern that took a veteran rep three years to accumulate enough experience to recognise becomes visible to a new rep on day one, because the file history is structured and searchable.

Group grievance management as a distinct workflow

When a pattern is identified and the union decides to address it through a group grievance — a single filing on behalf of all affected members — the case management workflow changes in ways that a standard individual grievance system cannot support. The file must hold multiple grievors, each with their own employment details and individual impacts. The remedy must be calculated for each grievor separately while being managed as a unified file. Step meetings involve a larger and more complex factual record. Arbitration, if it proceeds, involves evidence from multiple worksites and multiple incidents.

A group grievance managed in a standard individual grievance template — with a single grievor field and a single remedy field — will be administratively cumbersome and substantively incomplete. Purpose-built infrastructure must support the group filing structure from intake: multiple grievors linked to a single file, individual impact tracking, consolidated timeline management, and reporting that shows both the aggregate file status and the individual grievor details.

Pattern enforcement is where investment in infrastructure pays the largest dividend

An individual grievance that is won delivers a remedy to one member. A pattern grievance that is won — or a group of individual grievances that establish a pattern and force an employer practice change — delivers a remedy to every member affected by that practice, including the ones who never filed. The capacity to identify patterns, link related files, and manage group grievances is where the investment in case management infrastructure has the most significant and durable impact on working conditions. It is also the capacity that is most completely absent from email-and-spreadsheet case management.

8. Arbitration Preparation

Arbitration is where the quality of a union's grievance administration is fully tested. The file that was handled carefully — with complete intake notes, thorough step meeting records, all evidence preserved, all employer responses documented, and every decision logged — is a file that can be prepared for arbitration efficiently and presented coherently. The file that was handled on email and memory is a file that must be reconstructed before it can be prepared.

Arbitration preparation is also where the compounding effect of documentation gaps at every prior stage becomes fully visible. A missed witness name at intake becomes a witness the union cannot call. An undocumented step meeting position becomes a position the employer can characterise however they choose. A settlement offer that was discussed but not documented becomes a piece of bargaining history that the employer may try to introduce. The arbitration record is built from what the file contains — and what the file contains is determined by what was documented at every stage before arbitration prep began.

What arbitration preparation requires from the file

A complete chronology. Arbitration hearings are built on timelines. The arbitrator needs to understand exactly what happened, when, and in what sequence. Building a coherent chronology from a file that has complete, date-stamped stage records is a matter of hours. Building it from an email thread, a set of handwritten notes, and the rep's memory is a matter of days — and the result is never as complete or reliable.

All employer correspondence attached and indexed. Every discipline letter, every step meeting denial, every correspondence from the employer during the grievance process must be in the file, attached, and indexed. At arbitration, the employer will be referring to its own records. The union needs to be referring to the same records, plus its own documentation of the process.

Witness identification and preparation notes. Who are the potential witnesses? What do they know, and from what direct experience? Have they been contacted about potential hearing attendance? Witness management in arbitration preparation is a workflow in itself — one that requires tracking contact status, availability, and the substance of what each witness can offer.

Grievance history and prior settlements as context. Has the union grieved a similar issue before? Is there a prior settlement that established a practice the employer is now violating? Is there arbitration jurisprudence from this employer that is relevant? The file that is connected to the union's broader grievance history — through the pattern tagging and file linking that purpose-built infrastructure supports — provides this context automatically. The file that exists in isolation does not.

Disclosure management. Arbitration typically involves pre-hearing disclosure of documents and, in many jurisdictions, particulars of the parties' positions. Managing what has been disclosed, what has been received, and what outstanding disclosure requests exist is a workflow that must be tracked separately from the underlying file but connected to it.

Principle 7

Arbitration preparation is the final test of a union's case management practice. Files that were documented thoroughly at every prior stage can be prepared efficiently and presented coherently. Files that were managed on email and memory must be reconstructed before they can be prepared — a process that is time-consuming, incomplete, and places the union at a structural disadvantage before the hearing begins. The investment in case management infrastructure is, in significant part, an investment in arbitration readiness.

9. Remedy Tracking: The Step That Gets Dropped

Of all the stages in the grievance lifecycle, remedy tracking is the one that is most consistently neglected — and the one whose neglect is most invisible. When a grievance is settled and a remedy is agreed, the work feels done. The file is closed. The next intake is waiting. The member has been told the outcome. The follow-through — confirming that the money was actually paid, that the discipline was actually removed from the file, that the seniority was actually corrected, that the scheduling practice was actually changed — is administrative work that happens after the resolution, at a point when the case no longer feels like an open case.

The result is that remedy implementation failures are common and largely unreported. The member is told the grievance was settled. The file is closed. Months later, the member discovers that the discipline letter is still in their personnel file, or that the back pay calculation was wrong, or that the scheduling practice changed for two weeks and then reverted. They call the union. The rep who handled the case may no longer be in that role. The file may not contain the settlement terms in sufficient detail to identify the specific obligations that were not met. The member has lost time and recourse. The employer has benefited from a settlement it did not fully implement.

What remedy tracking requires

Documented remedy terms, not summaries. The settlement record must contain the full terms of the remedy — not "wages to be paid" but "wages at the grievor's straight-time rate for eight hours on [date], net of any earnings received, to be paid by [date]." Vague remedy documentation makes compliance disputes inevitable.

Compliance dates assigned at settlement. Each remedy obligation must have a compliance date — the date by which the employer is required to have fulfilled it. These dates must be tracked actively, not passively. The case management system must surface them before they arrive, not after they have passed.

Confirmation required to close. A file should not be closeable — in a well-designed case management system — until each remedy obligation has been confirmed as fulfilled. This does not mean confirmation is always possible immediately; some remedies unfold over time. But it does mean that the file stays open, with active tracking, until the remedy is confirmed or the union has made a documented decision that the matter is resolved.

Non-compliance as a new file trigger. When a remedy obligation is not met by the compliance date, that is not a reminder notice — it is a potential new grievance. Employer failure to implement a settlement remedy is itself a violation of the collective agreement, and in most cases it can be grieved. Purpose-built case management flags non-compliance and prompts the rep to assess whether a new filing is warranted.

A settlement with no remedy tracking is not a settlement — it is a promise

Members come to the union when the employer has done something wrong. When the union files and wins — or settles on terms that should make it right — the member's experience of the outcome is determined by whether the remedy is actually implemented, not by whether it was agreed. A settlement that is never fully implemented is, from the member's perspective, a case the union won on paper and lost in practice. Remedy tracking is not administrative housekeeping. It is the final act of representation.

Principle 8

Remedy tracking is the most consistently neglected stage of the grievance lifecycle, and its neglect is the most invisible — because closed files do not show up in active caseload reports. Purpose-built case management must keep remedy obligations as active tracked items after settlement, surface compliance deadlines before they pass, require confirmation of fulfilment before file closure, and trigger a non-compliance assessment when deadlines are missed. The representation is not complete when the settlement is signed. It is complete when the remedy is implemented.

10. What Adequate Case Management Infrastructure Must Provide

The analysis in this paper points to a specific set of requirements for case management infrastructure that is adequate to the operational complexity of grievance management in an active union office. These are not aspirational features — they are direct responses to the documented failure modes of inadequate infrastructure.

File-type-specific intake and process logic

Distinct intake forms for individual grievances, group grievances, policy grievances, discipline files, harassment and human rights files, and health and safety cases — each presenting the fields that type of file requires, triggering the escalation flags appropriate to that type, and applying the timeline logic that governs that process. Not one form with optional fields.

Dynamic, cascading deadline management

Deadline calculation from process events — incident date, filing date, employer response date, step meeting date — with automatic advancement to the next deadline in the chain. Surface active deadlines by urgency across the full caseload, not per-file. Flag extensions and suspension of timelines as trackable events. Alert before the deadline, not on it.

Stage-specific documentation forms

A structured form for each stage — intake, informal, filed, Step 1 through Step 3, arbitration referral, settlement, remedy tracking — that prompts for what is required at that stage, carries forward relevant context from prior stages automatically, and produces a navigable file history without requiring the user to assemble it manually.

Documented decision points

Required decision documentation at every decision point: file or not file, advance or withdraw, settle or continue, refer to arbitration. Each decision record must capture the reasons, the authority, the member communication, and the date. These records are the union's defence against duty of fair representation complaints.

Pattern detection and group file management

File tagging by employer, worksite, supervisor, article, and issue type, with views that surface all files sharing a given tag. Group grievance structure that links multiple grievors to a single file with individual impact tracking. Pattern visibility that does not depend on individual memory or experience.

Remedy tracking as an active workflow

Settlement terms documented in full, remedy obligations with compliance dates, active tracking of fulfilment status, confirmation required before closure, and non-compliance flag when deadlines pass. Remedy tracking is part of the case management workflow, not an afterthought.

The standard for adequate case management is representational, not administrative

The question for evaluating any case management system is not whether it is better than a spreadsheet. It is whether it is adequate to the obligation the union has undertaken — to represent each member fairly, consistently, and completely through the full lifecycle of their case. A system that tracks intake and filing but drops remedy tracking is not adequate. A system that manages individual grievances but cannot detect patterns is not adequate. A system that documents step meetings but does not enforce deadline management is not adequate. The standard is the full obligation, not the parts of it that are easy to automate.

11. Conclusion

Grievance management is not a simple process that has been made complicated by inadequate tools. It is a genuinely complex process — multiple file types, cascading deadlines, layered documentation obligations, consequential decision points, and a final obligation that extends past settlement to the implementation of the remedy — that has been under-supported by the tools most unions have used to manage it.

The members who bring their workplace problems to the union do not experience that complexity directly. They experience its consequences: the case that lost a deadline and could not be advanced. The settlement that was signed but never fully implemented. The pattern of violations that continued for years because each individual instance was handled in isolation. These outcomes are not inevitable. They are the predictable result of managing a complex, high-stakes process without infrastructure adequate to its demands.

The infrastructure described in this paper exists. It is not experimental or aspirational — it is the practical specification of what a purpose-built case management system for a union office must provide. The locals that invest in it do not simply administer grievances more efficiently. They represent their members more reliably, enforce the collective agreement more consistently, and build the institutional capacity — in documented file history, in pattern detection, in arbitration-ready records — that makes the union more effective over time, not just on the current caseload.

The standard for adequacy is not a comparison to email and spreadsheets. It is a comparison to the obligation the union has undertaken. That obligation runs to every member, on every file, through every stage, to the point where the remedy is confirmed as implemented. Anything short of infrastructure that supports that full obligation is, by definition, not enough.

Notes and Sources

This whitepaper is the fifth in a twelve-part series. It draws on qualitative operational analysis of grievance administration in active union offices across multiple sectors and jurisdictions in Canada and the United States, direct engagement with chief stewards, servicing reps, business agents, and local officers, and review of collective agreement provisions governing grievance timelines and processes.

Collective agreement provisions governing grievance timelines, step structures, and duty of fair representation obligations vary significantly by jurisdiction, sector, and affiliation. The analysis in this paper reflects the general structure of grievance administration under North American labour relations frameworks; specific locals should assess their obligations under their own agreements.

The file type table and stage documentation table are operational frameworks derived from grievance administration practice. They represent the general requirements of each file type and stage; specific collective agreements may impose additional or different requirements.

Companion papers: No. 1, The Infrastructure Gap Inside Modern Union Offices; No. 3, Building the Digital Operating System for Union Governance; No. 4, Data Infrastructure for Democratic Labour Institutions (Union Software, 2025).

About Union Software

Union Software builds purpose-built administrative infrastructure for labour unions. Our platform supports grievance and casework management, steward network administration, membership records, governance and meeting management, and communications — designed specifically for how union locals actually operate.

unionsoftware.com · contact@unionsoftware.com