01Executive Summary
Union offices manage an extraordinary range of operational demands. On any given day, a local union office may be tracking active grievances through multiple steps, responding to employer discipline, maintaining contact with hundreds of members across different worksites and shifts, preparing for executive board and membership meetings, managing dues records, documenting steward assignments, and communicating on multiple fronts simultaneously.
The systems supporting this work have not kept pace. Across the labour movement in North America, union offices — regardless of size, sector, or affiliation — consistently rely on a patchwork of general-purpose tools: email clients, spreadsheets, shared drives, and paper files. These tools were not designed for union casework. They do not enforce timelines, connect related files, support role-based access control, or produce the structured reporting that executive boards and trustees require.
This whitepaper identifies and describes the infrastructure gap: the measurable distance between the operational complexity of a functioning union office and the administrative systems that most locals actually have. It examines the specific functions where that gap is most consequential — grievance and casework management, membership records, communications, and governance reporting — and considers why the gap has persisted despite the clear costs it imposes.
The argument is not that union offices are poorly managed. In most cases, they are managed by people doing demanding work under real constraints. The argument is that the tools available to those people are systematically mismatched with the work they are doing — and that this mismatch has direct consequences for members.
Closing the infrastructure gap does not require replacing experienced people or importing corporate management systems. It requires purpose-built infrastructure: systems designed around how union offices actually function, that respect union governance structures, that handle confidentiality appropriately, and that can be used sustainably by a small team that includes both staff and elected volunteers.
01The Scope of What Union Offices Manage
Labour unions exist to represent workers — in grievances, in bargaining, in health and safety disputes, and in the day-to-day negotiations of workplace life. What is less visible, even within the labour movement, is the volume and complexity of the administrative work that makes that representation possible.
A local union office is not an advocacy organisation that occasionally generates paperwork. It is a case management operation, a records system, a communications function, a governance body, and a financial entity — all at once, and usually with a small team of staff and volunteers who wear multiple roles simultaneously.
What the caseload actually looks like
Consider the file generated by a single member issue. A member calls a steward about a discipline letter. What follows may include: a steward intake note, a review of the member's employment history, an examination of collective agreement language across multiple articles, correspondence with the employer, a Step 1 grievance meeting with notes and an employer reply, a Step 2 escalation, more correspondence, a decision on whether to advance to arbitration, arbitration preparation including disclosure requests and witness preparation, and finally, when a settlement is reached, implementation tracking to confirm the remedy has been applied.
That is one file. A mid-size local with 500 members may have twenty or thirty such files active at different stages simultaneously. A large local with 3,000 members across multiple employers and worksites may have over a hundred. Each file has timelines. Each timeline has consequences if missed. The grievance that is not advanced because someone did not track the deadline does not return — it is lost, and so is the member's claim.
Governance, finance, and communications alongside casework
Casework is the most visible operational layer, but it runs alongside governance obligations that are equally demanding. Union locals are democratic institutions governed by constitutions and bylaws. Executive board meetings require prepared agendas, accurate financial reports, grievance status summaries, and minutes that meet governance standards. Membership meetings require proper notice, quorum verification, and recorded motions. Elections must follow constitutional procedures. All of this generates its own documentation trail, and that trail is not optional — it is the legal and democratic foundation of the organisation.
Financial management adds a third layer. Per capita payments, expense approvals, lost time reimbursements, dues reconciliation, trustee reports, and budget-to-actual comparisons are recurring obligations in every local, regardless of size. Finance work is, as one long-serving local president put it, "steady, detailed, and unforgiving" — errors have consequences both for the union's finances and for its credibility with members.
Communications cut across all of it. Meeting notices, bargaining updates, ratification information, strike vote logistics, mobilisation calls, and member-facing updates all require sending the right message to the right people at the right time. In a local with multiple units, worksites, and employers, that is not a single mailing list — it is a segmented communications operation that needs to be accurate, trackable, and tied to the member record.
Finding 1 A functioning union office manages, in parallel: active casework with legal timelines, governance obligations under constitution and bylaws, financial recordkeeping and reporting, segmented member communications, and steward network coordination. These are not separate functions — they interact constantly and share the same small team.
02The Tools Most Locals Actually Use
Against this backdrop of operational complexity, the tools most union offices use are general-purpose applications that were not designed for union work. The pattern is nearly universal across the labour movement: email clients, spreadsheets, shared drives, and paper — occasionally supplemented by generic task management applications or contact databases that require workarounds to function in a union context.
Email as case management
Email is the primary repository for active casework in most union offices. Grievance intake information arrives by email. Employer replies are stored in email. Step meeting notes are often drafted in email and sent to colleagues. When a steward or staff rep needs to review the history of a file, they search their inbox.
The consequences of this approach are predictable. Institutional knowledge is not shared — it lives in individual inboxes. When a staff rep leaves or a steward changes roles, the file history may leave with them, or require a time-consuming reconstruction from whoever remains. Files cannot be searched across cases to identify patterns. Timelines cannot be tracked systemically. When the executive board asks for a grievance status report, someone has to manually compile it from scattered sources.
Spreadsheets as the backbone of tracking
Where email falls short for tracking, spreadsheets fill the gap. Locals typically maintain spreadsheets for active grievances, member lists, steward assignments, expense tracking, and communications logs. These spreadsheets are created by individuals, named inconsistently, updated unevenly, and stored in locations that change as shared drives are reorganised. When officer transitions occur, spreadsheets may not be handed over, and the formats that do transfer often require rebuilding by the incoming officer before they can be used.
The deeper problem with spreadsheet-based tracking is not the format — it is that spreadsheets do not enforce process. A grievance tracker can list a deadline, but it cannot send a reminder, flag an overdue step, or prevent two people from overwriting each other's updates. The discipline required to maintain a complex spreadsheet system accurately over time is significant, and in offices where staff are already stretched, that discipline is one of the first things that slips.
Paper as a permanent fixture
Despite the proliferation of digital tools, paper remains a significant part of union office operations. Discipline letters, grievance forms, meeting sign-in sheets, collective agreement copies, and member contact forms frequently exist only as physical documents. When a file goes to arbitration, the assembly of the paper record is a substantial task in itself — collecting documents from different sources, establishing chronological order, and confirming completeness.
Paper is not inherently a problem. Some documentation is legitimately paper-based. The problem is when paper is the primary organisational system rather than a supplement to a structured digital record — which, in most locals, it is.
The tools available to union offices are systematically mismatched with the work those offices are doing. That mismatch is not a technology problem. It is an organisational risk that is absorbed, invisibly, by members.
Finding 2 Most union locals manage their operational functions — including casework with legal filing timelines — using email, spreadsheets, and paper. These tools share a common characteristic: they do not enforce process, do not track deadlines, and do not produce structured information that can be shared across the office or reported to governance bodies without manual compilation.
03The Infrastructure Gap — Mapped
The infrastructure gap is not a single failure point. It is a set of recurring gaps between what union office functions require and what the tools typically in use can provide. The following table maps the gap across the primary operational functions of a union local.
| Office function | How most locals manage it today | Primary failure mode | Consequence for members | Minimum infrastructure requirement |
|---|---|---|---|---|
| Grievance & casework tracking | Email threads, personal notes, shared spreadsheet (often individual-maintained) | No deadline enforcement; file history in individual inboxes; no pattern detection across cases | Missed filing windows; lost case history when personnel change; employer advantage at step meetings | Stage-based case tracking with deadline alerts, shared file history, and role-based access |
| Steward assignment & network management | Static spreadsheet or roster document, updated manually when roles change | Outdated assignments; coverage gaps not visible; steward-to-member mapping deteriorates over time | Members can't reach a steward; grievances missed at intake; new stewards lack context | Live assignment records linked to membership and worksite structure, with visible coverage gaps |
| Membership records | Employer-provided lists supplemented by local spreadsheet; dues system separate from contact records | Lists don't match reality; stale contact information; status inconsistencies surface at votes | Members excluded from communications or votes; wrong contact used in urgent situations | Unified membership records with worksite/unit/shift structure and documented change history |
| Communications | Email blast from personal or shared account; list maintained separately from member records | Outdated lists; no segmentation by worksite, unit, or shift; no delivery tracking | Time-sensitive communications don't reach all members; no record of what was sent or when | List management tied to member records; segmented send by worksite/unit/shift; delivery logging |
| Governance & meeting records | Minutes in Word documents; agendas in email; motions not systematically tracked | Minutes stored inconsistently; motions and decisions not searchable; officer transitions disrupt continuity | Executive board loses institutional memory; governance decisions hard to verify; trustees lack documentation | Meeting workspace with agenda, motions, minutes, and vote records integrated with member database |
| Finance & expense tracking | Spreadsheet maintained by Secretary-Treasurer; receipts in physical file; reporting compiled manually | Finance work is reactive; approvals not systematically tracked; budget-to-actual requires manual assembly | Trustee reports late or incomplete; budget overruns not caught early; expense policy compliance unclear | Expense workflow with approval chain, receipt attachment, and reporting tied to budget categories |
| Reporting to executive board | Staff prepare reports manually before each meeting; data assembled from multiple sources | Preparation is time-consuming; reports may be inconsistent across periods; real-time view unavailable | Board decisions made on incomplete information; staff time consumed in report assembly rather than work | Live reporting dashboard with grievance status, upcoming deadlines, finance summary, and steward coverage |
The pattern across every row is the same: the primary failure mode is not malfunction of the tools in use — it is structural inability to enforce process, maintain continuity, or produce structured information for governance purposes. These are not edge cases. They are the routine operational requirements of any functioning union office.
Finding 3 The infrastructure gap is widest in the functions that carry the highest member risk: grievance tracking, steward assignment, and membership records. In all three cases, the typical approach creates conditions under which member access to representation can fail silently — without any visible alert that a deadline has been missed, a steward assignment has lapsed, or a member has been removed from communications due to stale contact information.
04Why the Infrastructure Gap Has Persisted
The infrastructure gap is not new. Union offices have operated this way for decades. Understanding why the gap has persisted — despite its evident costs — is necessary for understanding what closing it actually requires.
The tools available have been wrong, not the people using them
The most common explanation offered within the labour movement for administrative shortcomings is individual capacity: there are not enough staff, officers are stretched, volunteers are unreliable. These observations are accurate, but they describe a symptom, not the root cause. Most of the people managing union offices are capable, experienced, and committed to doing the work well. They are working with tools that make accurate, structured, consistent record-keeping extremely difficult to maintain over time without constant individual effort.
A grievance tracking spreadsheet maintained by a diligent staff rep will work well — until that staff rep leaves. An email-based file system maintained with careful folder structure will work well — until a new person takes over and uses different conventions. The fragility is in the system, not the person. Purpose-built infrastructure is more robust precisely because it does not depend on individual discipline to enforce the same structure every time.
Software solutions have not been built for unions
The software market has not served the labour movement well. Generic case management platforms are designed for law firms, insurance companies, or government agencies — not for union casework with its specific stages, timelines, role structures, and confidentiality requirements. Generic membership databases are designed for associations or nonprofits — not for union locals with bargaining unit definitions, seniority systems, and worksite-based steward assignments.
When union offices have attempted to adapt generic software for their needs, the adaptations have typically required significant manual workarounds that undermine the software's utility and add to, rather than reduce, administrative burden. The result is often a system that is worse than the spreadsheets it was meant to replace — because it imposes a structure that does not match union operations while also requiring maintenance of the underlying data.
The costs of the gap are mostly invisible
A missed grievance deadline is visible — once. A member who never hears back about their complaint is not in the administrative record at all. A pattern of management violations that was never identified because no one could see across the case files is, by definition, not something anyone notices. The costs of the infrastructure gap are borne primarily by members, and primarily in ways that do not generate a visible failure event that the union office can track and learn from.
This invisibility makes the gap self-perpetuating. When operational failures do not register as discrete events, there is no feedback loop that generates pressure for improvement. Officers who have managed without purpose-built infrastructure often do not know what they are missing — because what they are missing is the failures they do not know happened.
The visibility problem is the governance problem
Executive boards and trustees can only oversee what is visible to them. When operational information is scattered across individual email inboxes, spreadsheets, and paper files, governance bodies are working from summaries that may be incomplete, inconsistent, or weeks out of date. Infrastructure that makes operational information systematically available is not just an operational improvement — it is a governance improvement.
05The Institutional Comparison
To understand the magnitude of the infrastructure gap, it is useful to compare the operational systems available to union offices against those used by comparable institutions — organisations of similar size, similar staffing constraints, and similar obligations around records, governance, and member-facing service.
| Operational dimension | Typical union local | Comparable institution (hospital, school board, NGO of similar size) |
|---|---|---|
| Case and file management | Email threads, personal notes, spreadsheets. No enforced workflow, no shared history, no deadline tracking. | Purpose-built case management system with stage tracking, automated reminders, shared file access, and reporting. |
| Member/client records | Employer-provided lists supplemented by local spreadsheet. Separate from dues system and communications. | Unified constituent database with documented change history, contact preferences, and service record. |
| Communications | Email blast from shared or personal account. List maintained separately from records. No segmentation. | Communications platform integrated with constituent database. Segmented by group, tracked by delivery. |
| Governance & decisions | Minutes in Word documents stored inconsistently. Motions not linked to decisions or subsequent action. | Board management system with integrated agenda, minutes, motions, and decision tracking. |
| Financial tracking | Secretary-Treasurer spreadsheet. Receipts in physical file. Manual budget-to-actual assembly. | Finance system with approval workflow, digital receipts, automated reporting, and audit trail. |
| Reporting to oversight bodies | Staff compile reports manually before each meeting from scattered data sources. | Dashboard reporting with live data, exportable summaries, and consistent presentation across periods. |
| Knowledge continuity on transition | Institutional knowledge concentrated in individuals. Significant loss common when officers or staff change. | System-of-record design ensures institutional knowledge persists regardless of personnel changes. |
The comparison is not meant to suggest that union offices should operate like corporations or that the administrative culture of the labour movement should mirror the private sector. Union offices exist in a different political and democratic context, with different governance structures and different member relationships. The point is narrower: organisations of similar size and operational complexity across many sectors have access to purpose-built infrastructure that supports their work. Union offices, largely, do not.
Organisations of comparable size and complexity across many sectors have access to purpose-built infrastructure that supports their work. Union offices, largely, do not. That disparity is not inevitable — it is a historical gap that can be closed.
Finding 4 Union locals managing 300–3,000 members face operational complexity comparable to mid-size service organisations — hospitals, school divisions, nonprofit associations — that have long had access to purpose-built administrative infrastructure. The gap is not a natural feature of union operations. It reflects the historical absence of software built specifically for the labour movement's operational context.
06What Closing the Infrastructure Gap Requires
Identifying the infrastructure gap is easier than closing it. Previous attempts to address the problem — typically by adapting generic software or building custom systems — have often failed to produce durable improvements because they did not start from the right premises about what union offices actually need.
It requires starting from how union offices actually work
The single most important design principle for union office infrastructure is that it must reflect the actual operational structure of a union: bargaining units, worksites, steward networks, grievance stages, collective agreement references, and role-based access controls that map to elected and appointed positions. Software that requires a union to model itself as a "company" with "customers" and "employees" will not be adopted, because it asks staff and officers to constantly translate between their actual work and the system's categories.
This is not primarily a user experience concern. It is a data integrity concern. When the categories in a system do not match the categories in the work, people fill in fields incorrectly, skip fields that do not map cleanly, or maintain parallel records outside the system to handle what the system cannot. The result is a database that reflects the software's categories rather than the union's reality — and a staff that has learned not to trust it.
It requires handling confidentiality as a structural feature, not an afterthought
Union casework involves some of the most sensitive information in a workplace: medical documentation, harassment complaints, discipline records, legal opinions, and internal conflict. In most union offices, confidentiality is managed through individual judgment — certain files are kept in a particular drawer, or sent only to particular people, or stored separately from the main file system. This approach depends on consistent individual practice rather than structural enforcement, and it creates liability when personnel change.
Purpose-built infrastructure for union offices must treat role-based access control as a core feature, not an add-on. The staff rep should be able to see all active files. The steward should see the files at their worksite. The trustee should have read-only access to financial reporting. The executive board should have visibility into operational summaries without access to confidential file details. These are not edge cases — they are the normal operating conditions of a union office with appropriate governance structures.
It requires supporting the volunteer layer
Union locals run on a combination of paid staff and elected volunteers. The ratio varies by local, but in most cases, a significant portion of the work — governance, steward representation, committee activity, communications — is carried by people who are doing this work in addition to their regular employment. Any infrastructure that requires extensive training, complex interfaces, or significant ongoing maintenance will not be adopted sustainably by this layer.
Simple, direct interfaces — accessible on a mobile device, requiring minimal training, and producing useful outputs without requiring a data administration background — are not a luxury feature for union offices. They are a prerequisite for sustainable adoption.
It requires that institutional knowledge survives personnel transitions
Officer and staff transitions are a recurring feature of democratic organisations. In most union locals, a significant portion of institutional knowledge — the history of a long-running file, the context behind a particular settlement, the reason a specific practice was adopted, the member contact who is most effective for a particular worksite — exists in individual memory rather than in any shared system. When that person leaves, the knowledge leaves with them.
Purpose-built infrastructure is the only reliable solution to this problem. When case history, meeting records, communications logs, and steward notes are maintained in a shared system, they survive personnel transitions intact. The incoming officer or staff rep can review the history of any file, understand the current state of any active case, and continue where their predecessor left off. This is not an administrative convenience — it is a structural protection for members whose files may span multiple officers over years.
Infrastructure as a democratic obligation
Union locals are democratic institutions with obligations to members that extend beyond individual terms of office. A member who files a grievance in the second year of one officer's term has a legitimate expectation that the file will be handled with the same care in the third year of the next officer's term. Meeting that expectation requires infrastructure that persists and functions regardless of who holds a given role — not systems that depend on individual memory and personal organisation habits.
07Implications for Union Leadership
The infrastructure gap is ultimately a leadership question. The decision to invest in purpose-built infrastructure — to move from email and spreadsheets to systems designed for union work — requires a clear-eyed assessment of the costs of the status quo and the conditions necessary for a successful transition.
The cost of the status quo is ongoing and largely invisible
The argument for maintaining the current approach is usually made on two grounds: it has worked so far, and the transition costs of change are high. Both observations have some validity, but neither withstands scrutiny when the full cost of the status quo is accounted for.
The infrastructure gap costs the labour movement in missed grievance deadlines, lost file histories, incomplete member records, missed communications, and governance bodies making decisions on incomplete information. These costs are not measured or reported because the systems that would allow them to be measured do not exist — which is itself part of the problem. The absence of a counter makes the status quo appear cheaper than it is.
The transition requires realistic expectations
Moving from a fragmented patchwork of tools to a structured, purpose-built system is not a simple upgrade. It requires data migration, staff orientation, and a period of parallel operation while confidence in the new system builds. Locals that have made this transition successfully have generally shared one characteristic: they started with the functions that cause the most operational pain — typically grievance tracking and membership records — and expanded from there, rather than attempting a comprehensive implementation from day one.
It also requires that the system chosen reflects the union's specific structure and operational culture. A system that works well for a public sector local with a single employer and a centralised office will not necessarily work well for a private sector local covering multiple employers across a wide geography. The infrastructure has to fit the local, not the other way around.
The question is not whether to close the gap — it is when
The operational demands on union offices are not decreasing. Employer sophistication in managing discipline and grievance processes has increased significantly over the past two decades. The legal complexity of collective agreement administration has grown. Member expectations of responsiveness and transparency have risen alongside expectations in every other service context. The infrastructure gap that was manageable in a simpler operational environment becomes progressively more costly as complexity increases.
Union leaders who invest in closing the infrastructure gap are not chasing technology for its own sake. They are making a practical decision about the organisation's capacity to fulfil its core obligation — effective representation of members — over the long term. The tools available for that investment have improved substantially in recent years. The cost of waiting is not zero.
The infrastructure gap costs the labour movement in missed grievance deadlines, lost file histories, and governance bodies making decisions on incomplete information. These costs are not measured because the systems that would allow them to be measured do not exist — which is itself part of the problem.
08Conclusion
Union offices manage operational complexity that is comparable to many professional service organisations — but with infrastructure that lags significantly behind what those organisations have had access to for years. The gap between the demands of the work and the tools available for that work is not a minor inconvenience. It is a structural condition that affects the quality and reliability of member representation.
Closing the infrastructure gap requires purpose-built systems: designed around how union offices actually operate, supporting the governance structures of democratic institutions, handling confidentiality as a structural feature, and functioning sustainably for a combination of paid staff and elected volunteers. Generic tools adapted for union use will not close the gap — they will add the cost of adaptation to the cost of the existing problem.
The labour movement has invested substantially, over many decades, in the analytical and legal capacity to represent workers effectively. That investment deserves administrative infrastructure that can support it. Members whose cases are tracked in inboxes and spreadsheets, whose steward assignments exist only in someone's memory, and whose contact information lives in files that do not survive officer transitions are not receiving the full benefit of that investment.
The infrastructure exists to close this gap. What remains is the organisational decision to use it.
10Notes and Sources
This whitepaper draws on qualitative operational analysis of union office functions across multiple sectors, locals, and jurisdictions in Canada and the United States, supplemented by direct engagement with union staff, elected officers, and administrative personnel. Individual locals are not identified to protect the confidentiality of operational discussions.
Operational data on grievance volumes, steward-to-member ratios, and caseload estimates reflects patterns common across mid-size locals (300–3,000 members) in the public and private sectors. Specific figures vary by local, sector, and collective agreement structure.
The institutional comparison in Section 5 draws on published operational practices in comparable-size healthcare, education, and non-profit organisations. The comparison is illustrative rather than systematic — individual organisations vary considerably in their infrastructure investment and maturity.
All union language and operational terminology reflects standard usage in Canadian and North American union contexts. Terminology may vary by affiliation, jurisdiction, and sector.
11About 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 · legal@unionsoftware.com