Union management software buyer’s guide and evaluation scorecard

Choosing union management software is an operational and governance decision, not simply a feature comparison. A defensible process begins with the union’s requirements, gives vendors the same scenarios and records the evidence observed during evaluation.

This article is published by UnionStack. It is not an independent product ranking, and it does not assume one product is best for every union. The scorecard is designed to be applied consistently to UnionStack and other shortlisted products.

Start with outcomes, not a long feature list

A list of hundreds of requirements can make every product look equivalent because vendors can answer many questions with a general “yes.” Outcomes create a stronger test. Examples include reducing duplicate member records, keeping grievance evidence discoverable, showing current representation relationships or eliminating repeated publication of the same meeting information.

For each outcome, identify the people affected, the authoritative records, the current failure points and the evidence that would show the new process works. This becomes the foundation for demonstrations and a controlled pilot.

A practical weighted scorecard

Adjust the weights before vendor demonstrations begin. A sample model is:

• Membership and organizational structure — 20%. People, positions, effective history, locals, employers, bargaining units, workplaces and related records.
• Grievance and case management — 20%. Intake, participant roles, assignments, progress, evidence, communication, outcomes and reporting.
• Communication and meetings — 10%. Operational email, attachments, meeting participants, documents and relationships.
• Public and member experiences — 10%. Public publishing, registration, authentication, identity matching and protected visibility.
• Reporting and integration — 10%. Reproducible operational reports, documented authorization and required external systems.
• Security and governance — 10%. Data location, permissions, credential handling, encryption, access reviews and shared responsibilities.
• Migration and implementation — 10%. Mapping, cleansing, reconciliation, cutover, training and stabilization.
• Commercial and support fit — 10%. Subscription, required modules, services, support, renewal, cancellation and exit.

Use the same demonstrations for every vendor

Member-change scenario

Update a member’s position, workplace or status with appropriate effective information. Confirm the current view, useful history, organizational context and downstream report.

Grievance scenario

Create a case from a representative concern. Add participants with roles, assign responsibility, relate an email and meeting, attach evidence, move through stages and record the result.

Member-portal scenario

Register and sign in using a dedicated test member. Confirm intended records are visible, unintended records are not and support staff can resolve an identity mismatch through an approved process.

Reporting scenario

Create a workload or membership report using the records entered during the demonstration. Ask how definitions are maintained and how users investigate a surprising result.

Integration scenario

Authorize a test client or complete the required integration. Verify identifiers, permission scope, failure handling, credential ownership and reconciliation.

Score evidence with a simple scale

• 0 — Not available: the requirement could not be demonstrated.
• 1 — Material gap: the outcome depends on an unsupported workaround or uncommitted future work.
• 2 — Available with significant implementation: the path is credible, but scope, cost and ownership must be approved.
• 3 — Configurable: the product supports the outcome after documented configuration that the buying team understands.
• 4 — Demonstrated: representative users completed the scenario with expected controls and results.

Add notes and evidence to every score. An unsupported “4” is less useful than a carefully documented “2.”

Commercial questions to document

Compare more than the monthly subscription. Record minimum commitments, seat definitions, required modules, implementation services, migration limits, training, support response commitments, payment processing, storage, integrations, renewal treatment and exit assistance.

UnionStack user subscriptions start at $99.99 CAD per user per month, or save 16% with an annual subscription. New users receive a 30-day trial. Buyers should still review checkout, taxes, intended seat quantity and any implementation work required for their scope on the pricing page.

Make the final decision reproducible

Keep the approved requirements, demonstration scripts, scores, assumptions, commercial responses, security review and migration plan together. Record why lower-scored areas were accepted and who owns each mitigation.

The best choice is the product that meets the union’s weighted requirements with evidence and an implementation model the organization can operate. Use the full buyer’s guide and scorecard to structure the review.