1. Model test
Can the vendor represent your structure and terminology without flattening important relationships or requiring a custom project for every label?
Union management software buyer’s guide
Choose the best union management software for your actual work.
A criteria-led evaluation framework for membership, grievances, communication, reporting, sites, integrations, security, migration and total operating fit.
Editorial disclosure
Criteria first. Vendor identity second.
This guide is published by UnionStack and therefore is not an independent third-party ranking. It does not declare UnionStack—or any competitor—the universal “best.”
The evaluation method is intentionally product-neutral: define requirements, give shortlisted vendors the same data and scenarios, score observable evidence, record gaps and compare total implementation responsibility. UnionStack-specific links are clearly identified so buyers can test our claims directly.
Reviewed August 16, 2026 by the UnionStack Support Team. Product capabilities and commercial terms should always be confirmed with each vendor.
Weighted scorecard
Adapt the weights before vendor demonstrations begin.
| Criterion | Example weight | Evidence required |
|---|---|---|
| Membership and structure | 20% | Model representative people, positions, locals, employers, bargaining units and historical changes. |
| Grievance and case work | 20% | Complete one real procedure from intake through roles, evidence, communication, outcome and closure. |
| Communication and meetings | 10% | Connect an approved mailbox, relate a thread and demonstrate a meeting with participants and documents. |
| Member and public experience | 10% | Test registration, protected access, public publishing and content ownership with representative accounts. |
| Reporting and integrations | 10% | Produce an operational report and complete an authorized API or required integration scenario. |
| Security and governance | 10% | Review data location, access controls, encryption, credentials, logging, subprocessors and shared responsibilities. |
| Migration and implementation | 10% | Map a data sample, reconcile results, identify exceptions and document training and cutover ownership. |
| Commercial and support fit | 10% | Compare subscription, modules, services, increases, support, exit and the internal effort required to operate the system. |
Eight buying tests
Turn feature claims into observable evidence.
2. Change test
When a member, position, leader or bargaining relationship changes, can staff update the current state without destroying useful history?
3. Case test
Can another representative reconstruct a grievance from the requestor, roles, evidence, emails, meetings, stages and result?
4. Access test
Can the buying team demonstrate least-privilege access with representative users instead of relying on a slide about security?
5. Portal test
Can a fake member register, sign in, find the intended information and recover from an identity or access problem?
6. Reporting test
Can operational users produce the views they need from maintained data without recoding records in spreadsheets?
7. Integration test
Can a technical evaluator authorize a client, retrieve connected data and understand permissions, limits and credential lifecycle?
8. Exit test
Can the vendor explain export format, attachments, relationships, retention and the responsibilities involved when the contract ends?
Requirements workshop
Build the shortlist from workflows, not category labels.
- 01
Name the outcomes
Identify measurable problems such as duplicate member records, unclear grievance ownership, inaccessible case email or repeated website publishing.
- 02
Select representative scenarios
Choose routine and exceptional examples. Redact sensitive data, preserve realistic relationships and give the same scenarios to every vendor.
- 03
Assign weights and owners
Have membership, representation, communications, finance, IT, privacy and leadership participants agree on weights before seeing polished demos.
- 04
Score observed evidence
Record what was completed, what required configuration, what depended on a future commitment and what could not be demonstrated.
- 05
Calculate total responsibility
Include data cleanup, configuration, integration, internal administration, support, training, renewal and exit—not only subscription price.
- 06
Run a controlled pilot
Let real users complete the priority workflows with test data, document friction and verify the vendor’s remediation path before commitment.
Warning signs
Pause when the evidence does not match the claim.
- A generic contact database is presented as union-specific without a demonstrated structure, position or grievance model.
- Every request is answered “yes” but the vendor cannot complete the scenario in a working environment.
- Migration is described as copying tables without source ownership, mapping, reconciliation or exception handling.
- Member portals are demonstrated only as an administrator, not with registration and a representative member identity.
- Security answers focus on a hosting provider while omitting roles, credentials, integrations and customer responsibilities.
- Pricing omits required modules, implementation services, minimums, support tiers or expected renewal treatment.
- Reporting depends on manual exports for every recurring operational question.
- API availability is claimed without accessible authorization documentation or a test workflow.
Apply the framework to UnionStack
Our claims should survive the same tests.
UnionStack offers a 30-day free trial. User subscriptions start at $99.99 CAD per user per month, or save 16% with an annual subscription. Use the trial to model structure, create people and positions, progress a grievance, connect a controlled mailbox, inspect sites and test a documented API path.
Record any required configuration, integration or procedural boundary. If UnionStack cannot demonstrate a requirement that matters to your union, treat that as a gap in the same scorecard used for every other vendor.
From the UnionStack blog
Continue with evidence-led analysis
Union management software buyer’s guide and evaluation scorecard
Build a defensible union software shortlist with disclosed criteria, weighted requirements and repeatable product demonstrations.
Read the article →The definitive guide to union management software
Understand what union management software should model, which workflows to test and how to evaluate implementation, governance and long-term fit.
Read the article →Related implementation guides
Use practical guides during vendor evaluation
Use these maintained UnionStack 2.0 guides to evaluate the workflow in detail.
Foundation
Get started with UnionStack
Orient your team, confirm terminology and prepare a safe first configuration.
Support Team · UnionStack 2.08 min read → DataPrepare data for UnionStack onboarding
Clean, map and stage source information before creating production records.
Support Team · UnionStack 2.012 min read → AccessPlan roles, users and access
Give each person the access required for their responsibilities without widening it unnecessarily.
Support Team · UnionStack 2.09 min read → CasesCreate and progress a case
Move from intake through participants, progress, evidence and outcome.
Support Team · UnionStack 2.012 min read → Member accessTest member registration and sign-in
Verify registration, email continuation and supported identity-provider sign-in as a real member would experience them.
Support Team · UnionStack 2.010 min read → DevelopersPlan and authorize an API integration
Use OAuth 2.0 with PKCE and tenant-aware APIs to extend a defined UnionStack workflow.
Support Team · UnionStack 2.012 min read →Built for connected work
Evaluate UnionStack with the same scorecard.
Use the free trial to require evidence from our product, not just promises.