Current UnionStack interface shown with fictional demonstration records.
Product tour
Union management software product tour
Watch the 10-minute video to see member records, grievance work, dues remittances and reporting in one connected workspace. Then explore the screenshots below for a closer look at each workflow.
Watch UnionStack in action · 9 min 54 sec
See how the work connects.
Follow member records, grievance work, dues remittances and reporting through the application, using fictional demonstration records.
Play at your own pace, or use full screen for a closer look.
Open video directlyRead the video transcript
00:00 One connected workspace
Welcome to UnionStack, a connected workspace for the people who keep a union moving.
It brings member information, representation, finance, and daily coordination into a shared system, while preserving the permissions each kind of work requires.
This tour uses actual application screens with demonstration records.
00:23 Start with the next action
Start at the dashboard, where personal, team, and unassigned views help staff find the work that needs attention.
The workspace brings together priorities, upcoming activity, pinned records, and recent work.
From here, we will explore four capabilities that connect everyday tasks to a bigger operational picture.
00:47 A member, in context
First, open a member profile. The header establishes who you are working with, and the sections below organize the information around that person.
Contact details, credentials, positions, and linked records stay close together.
Staff can move through the member's context without rebuilding the story in separate spreadsheets.
01:10 Connect people to organizations
Positions connect a person to the organizations where they work and participate.
In this demonstration, the member has two current assignments, connecting worksite context with an employer payroll relationship.
Dated assignments give staff a structured way to understand those relationships and support the membership analysis we will visit later.
01:33 Keep supporting evidence close
The credentials section keeps qualifications connected to the member record, including the issuing organization and effective and expiry dates.
Linked email conversations provide another part of that history.
Together, these sections help an authorized staff member understand the person behind a request before deciding what should happen next.
01:54 Review the quality of the record
Shared records become more useful when teams can maintain their quality. People operations brings administrative review into a dedicated workspace.
Here, an address finding includes a source workflow and explicit resolution controls.
The issue remains visible for review, so a correction can be handled as a deliberate administrative action.
02:18 Make changes reviewable
Member change requests add a review step between a proposed correction and the shared record.
The screen shows the member, the current phone value, the proposed value, and separate approve and reject controls.
That makes the decision concrete for the reviewer and supports governed maintenance of membership information.
02:39 Build the case around the member
The second capability is connected casework. This grievance workspace brings a pay classification issue together with the member, assigned staff, and the case summary.
Caseworkers can keep the issue, supporting context, and requested resolution in one place.
The record becomes the shared reference point as representation progresses.
03:03 Link the agreement evidence
The Articles section connects the grievance to the relevant employer agreement and its cited provision.
Instead of relying on a detached reference in a note, staff can preserve an explicit relationship between the case and the agreement.
That connection helps reviewers understand which contractual language is relevant to the issue.
03:24 Keep the next step visible
Progress records give the case a visible sequence of work. Here, an initial review and a scheduled investigator assignment show how activity is organized around the grievance.
Staff can follow the recorded steps and understand what comes next.
Foundational deadlines and messaging support the workflow alongside this case history.
03:47 Compare agreement generations
Agreement comparison extends that context across successive agreements. The comparison identifies changed, added, and removed articles, as well as splits, merges, and replacements.
Those relationships matter when article numbering or structure changes.
Review status helps agreement managers distinguish a suggested mapping from a relationship that has been checked.
04:13 Read the wording side by side
Open the wording view to compare the actual text side by side.
In this demonstration, the overtime language moves from seniority allocation to rotation and monthly allocation records.
The interface makes the difference visible, giving staff a practical starting point for reviewing the agreement and discussing its implications for casework.
04:38 Bring submissions into a queue
The third capability is employer dues remittance. Finance staff begin with a queue of submissions, where employers, reporting periods, totals, statuses, and exception counts are visible together.
The queue helps identify which submission needs review.
Each remittance then opens into its own controlled workflow and employee detail.
05:03 Review before posting
A remittance is staged for review before dues are posted. This example has a blocking employee matching exception, with calculated, posted, and paid totals shown separately.
The workflow makes that distinction explicit.
Unresolved employees and blocking exceptions must be addressed before the submission can advance through approval and posting.
05:28 Resolve the employee match
At the employee level, staff can inspect reported lines, matching controls, and deduction components.
Matching uses employer scoped identifiers, and the workflow does not treat a name alone as sufficient evidence.
An employer file also does not silently change membership or employment status, keeping remittance processing separate from member administration.
05:54 Separate the financial stages
After review, the workflow supports approval, posting, and payment reconciliation, with activity history and reconciliation export.
The separate totals help finance staff understand the difference between what was calculated, what was posted, and what has been paid.
That creates a clearer path from an employer submission to an accountable financial record.
06:20 See the shape of casework
The fourth capability is operational insight. Case Trend Analysis brings opened, closed, and reopened cases together with backlog over time.
Managers can see the relationship between incoming work and completed work, then review the supporting aging and deadline panels.
The report stays within the user's authorized case scope.
06:45 Understand membership movement
Position Analysis looks at membership and assignment movement across a selected reporting period. The charts show growth, joins, exits, and position activity.
That helps staff explore how the represented population is changing.
The measures describe recorded people and assignments, giving the team a consistent starting point for further investigation.
07:12 Turn a pattern into a question
Useful reporting connects a visible pattern to a follow up question. If backlog is rising, inspect aging and deadline performance, then use the available scoped drill downs and exports.
Membership reporting also includes privacy suppression for sensitive small groups.
The aim is informed operational review, grounded in the underlying records.
07:39 Carry decisions into follow-up
Beyond those four capabilities, meetings connect coordination to recorded follow up. The workspace brings an agenda, participants, decisions, and dated actions into the same view.
A discussion can lead to a documented decision and an identifiable next step.
That keeps meeting outcomes close to the people and work they concern.
08:05 Coordinate member learning
Events provide another connected workflow for member engagement. This published workshop has a description, a visible workflow, and two scheduled sessions.
The events module supports registration, attendance, completions, and credentials.
Teams can organize learning activities while keeping the resulting participation connected to the broader member experience.
08:30 Reflect the union's structure
Organization structure provides context across these workflows. The hierarchy view brings organizations, configurable types, lifecycle status, and child relationships together.
Locals, employers, departments, and worksites can be represented in a shared structure.
People, agreements, and operational records can then connect to the organizations that give their work meaning.
08:57 Shared context. Defined boundaries.
Underneath the interface, modular dot net services share a tenant scoped PostgreSQL foundation. Open ID Connect handles identity, while permission checks protect each workflow.
Signal R notifies authorized screens after committed changes, and background jobs support durable processing.
These foundations help connected workflows retain their distinct access and reliability boundaries.
09:26 Follow one complete workflow
UnionStack brings member context, connected casework, controlled remittance processing, and operational insight into one working environment.
A practical next step is to follow a real workflow: understand the member, advance the work, and review the outcome.
That is the value of a shared workspace: better context for the next decision.
Current product
Start with the operating picture.
The workspace dashboard brings priority, active work, recent records and upcoming meetings together. Every screen below uses fictional records from the current UnionStack interface.
Current UnionStack interface shown with fictional demonstration records.
Current UnionStack interface shown with fictional demonstration records.
Current UnionStack interface shown with fictional demonstration records.
Current UnionStack interface shown with fictional demonstration records.
Current UnionStack interface shown with fictional demonstration records.
More of the union’s work
From agreement changes to campaign follow-up.
Compare wording, review a dues exception, plan workshop sessions and follow worker outreach. Each feature page explains its workflow and activation requirements.
Current UnionStack interface shown with fictional demonstration records.
Current UnionStack interface shown with fictional demonstration records.
Current UnionStack interface shown with fictional demonstration records.
Current UnionStack interface shown with fictional demonstration records.
Fictional campaign shown. Jurisdiction activation and an approved pilot are required.
Evaluation sequence
Test the connections that matter.
Use one controlled scenario to verify record relationships, responsibilities, permissions and follow-through across the platform.
Start with a person
Open a governed people record with contact details, status, classifications and relationships.
See the position
Follow dated assignments into the employer, workplace, local or other configured structure.
Open the agreement
Find terms, articles, documents, renewal context and case links.
Progress a case
Bring together participants, assignments, deadlines, evidence, communication, meetings and outcome.
Share with purpose
Publish approved information to a UnionStack Site or expose configured member experiences behind sign-in.
Review the operation
Use permission-filtered dashboards, domain reports, audit history and documented APIs.
Bring your scenario
Use a controlled case, member change or publishing workflow from your own evaluation plan.
Prepare a trial →Next step
See how your union’s work stays connected.
Try a real workflow with the 30-day trial, or request a guided walkthrough with UnionStack.
Credit card required. Automatic billing after 30 days.