People types and fields
Configure member, retiree, staff or other people types with the statuses and custom information your organization is authorized to maintain.
Union membership management software
Member records that explain more than a mailing list.
UnionStack connects each person to positions, terms, locations, organizational entities, agreements, cases, meetings, communication and reporting so staff can understand the member and the working context around them.
A connected membership record
Keep identity, representation and activity in context.
A useful union membership database needs to answer practical questions: who is this person, where do they work, what position do they hold, which part of the union represents them, and what current work is connected to their record?
UnionStack supports configurable people types, statuses and fields rather than assuming every union uses the same labels. Contact and location information can sit alongside notes, documents, tags and positions. Relationships to cases, meetings, leaders and organizational entities provide context without copying the same information into separate systems.
The result is not a single oversized profile. It is a connected record whose structured details can be maintained by the people responsible for them and reused in the workflows that need them.
Feature evidence
Follow the member through six operational views.
Positions and terms
Connect positions with status, effective terms, steps, pay rates and dues information where they apply to the union’s model.
Union structure
Relate people and positions to locals, employers, bargaining units, workplaces, committees or other configured entities.
Contact and locations
Maintain approved addresses, phone numbers, email addresses and locations using consistent types and ownership rules.
Representation activity
Open connected cases, meetings, leadership terms, notes, documents and email relationships without searching another database.
Reporting and integration
Use configured fields and relationships in operational reports or authorized API workflows instead of rebuilding member context downstream.
Real workflow
From a member update to dependable downstream data.
- 01
Find the existing person
Search by approved identifiers and verify name, contact or organizational context before creating a record. This reduces duplicate people and conflicting histories.
- 02
Review the active context
Confirm people type, status, location, connected entity and current position. Record a change with the appropriate effective information rather than erasing useful history.
- 03
Update structured information
Use configured fields and controlled values for information that teams need to filter, compare or report. Reserve notes for narrative context.
- 04
Check connected work
Review open cases, meetings, email and leadership relationships that may be affected. Avoid copying the update into every connected record.
- 05
Validate the result
Confirm an authorized second user can find the person, interpret the current position and understand the organizational relationship without consulting a private spreadsheet.
Buyer guidance
Evaluate membership software with representative records.
A polished contact screen is not enough. Ask each vendor to demonstrate how the membership record behaves when structure, status and representation change.
| Evaluation question | Evidence to request |
|---|---|
| Can the model reflect our union? | Configure one local, employer, bargaining unit, workplace, people type and position using your terminology. |
| Can we preserve useful history? | Change a member’s position or term and show how current and prior context remain understandable. |
| Can staff avoid duplicates? | Demonstrate search, identifiers, duplicate-prevention practice and a correction workflow. |
| Does membership connect to representation? | Open a person and move directly to a related grievance, meeting, email conversation and organizational entity. |
| Can we report without shadow spreadsheets? | Produce an operational view using the configured statuses, positions and relationships demonstrated earlier. |
| Can we control collection? | Identify which fields are necessary, who can maintain them and how access is reviewed. |
Know the boundary
Membership management is broader than dues processing.
UnionStack records positions, steps, pay rates and dues information as part of connected member context. Buyers with specialized employer-remittance reconciliation, payment collection, accounting or financial-system requirements should document those workflows explicitly and verify the required implementation and integrations during evaluation.
This distinction keeps the buying process factual: choose the platform for the procedures it can demonstrate, and identify where an accounting, payroll, payment or specialist system remains authoritative.
Understand CRM, AMS and UMS boundaries →From the UnionStack blog
Continue with evidence-led analysis
Union member database and relationship management
Design member records around positions, terms, workplaces, bargaining units, representation and dependable data governance.
Read the article →Related implementation guides
Build and maintain dependable membership records
Use these maintained UnionStack 2.0 guides to evaluate the workflow in detail.
People
Manage people and positions
Create dependable member records and connect positions, terms, pay and dues.
Support Team · UnionStack 2.09 min read → StructureBuild your union structure
Model entities and relationships around the way responsibility and representation actually work.
Support Team · UnionStack 2.010 min read → Contact dataMaintain contact details and locations
Keep authorized addresses, phone numbers, email details and locations current and usable.
Support Team · UnionStack 2.08 min read → PositionsConfigure positions, pay rates and dues
Represent position types, steps, compensation and dues information consistently.
Support Team · UnionStack 2.011 min read → LeadershipTrack leaders and leadership terms
Connect leaders to organizational entities while preserving useful term history.
Support Team · UnionStack 2.09 min read → AgreementsConnect agreements and articles
Keep governing language close to the entities, cases and decisions that rely on it.
Support Team · UnionStack 2.09 min read →Built for connected work
See membership relationships in one connected system.
Use the trial to model representative members, positions and organizational structure.