Workflow context
What this guide helps you accomplish
Create UnionStack people records that remain useful across contact, representation, case and reporting workflows.
The person record provides identity and context; positions explain the person’s relationship to work and the union over time.
Collect and retain only the personal information your organization needs and is authorized to manage.
Before you begin
Prepare the following before changing shared configuration or records:
- An approved naming standard and a clear source for identity, position, organizational and agreement information.
- A representative branch of the union structure, including the relationships that make the records meaningful.
- Fake people and position records that can be changed safely during testing.
- A fake person with a current position and a historical change to test effective information.
Procedure
Complete the steps in order with fake or approved test information first. Record configuration decisions that will affect other teams.
Choose the correct people type
Select the type that reflects the person’s relationship to the union and exposes the appropriate configured information.
Create the core identity record
Enter the name and authorized contact or location details using the organization’s naming and contact standards.
Add status, tags and custom information
Use structured values for information that must be filtered or reported and notes for narrative context.
Connect a position
Create or select the relevant position type, then record status, term, step, pay rate or dues information where applicable.
Review connected work
Verify related cases, meetings, email and leadership information from the person record rather than duplicating it.
Maintain changes over time
When a role or term changes, update the relationship and effective information without erasing useful history.
Product view
Video demonstration
Follow the principal workflow in this captioned demonstration. The recording uses fake records in the UnionStack test environment.
Troubleshooting
Use the symptoms below to diagnose the workflow before widening access, adding duplicate configuration or bypassing an intended control.
A new position overwrites useful history
Create or update the effective relationship according to policy instead of replacing the prior term. Verify reports can distinguish current from historical information.
A person or entity appears more than once
Stop before adding another record. Compare identifiers, contact details and connected positions, then use the organization’s correction process to preserve the authoritative record.
A relationship is technically valid but confusing
Open both connected records and confirm the relationship label answers a useful operational question. Rename or remove relationships that staff cannot interpret consistently.
A report does not match the expected structure
Inspect the underlying type, status, effective dates and entity relationships before changing the report. Correct the source record and rerun the same filter.
Validation checklist
Do not treat the procedure as complete until an authorized second person can reproduce the intended result.
- The person record shows the correct current position while preserving the historical relationship needed for interpretation.
- The record can be found using the identifiers and terminology staff actually use.
- Current and historical relationships are distinguishable without overwriting useful history.
- A user can move from the person to the relevant position, entity or agreement in context.
- A sample report produces the expected population after source records are reviewed.
Version applicability
This guide was verified for UnionStack 2.0 on August 16, 2026. Available fields, types, relationships, navigation and access can vary with tenant configuration and user permissions.
Corresponding product capability
Membership management software
See the feature evidence, connected workflows and buyer guidance behind this procedure.
Explore Membership management software →Continue learning
Return to the UnionStack Learning Centre, or take the UnionStack product tour to see how these parts connect.