Workflow context
What this guide helps you accomplish
Track UnionStack leadership assignments so current representation and historical terms remain clear.
Leadership records should answer who represents an entity now and how that responsibility changed, without erasing prior terms.
Leadership records should answer both who represents the organization now and how that responsibility changed over time.
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.
- An approved fake leadership appointment with role, entity and effective dates.
Procedure
Complete the steps in order with fake or approved test information first. Record configuration decisions that will affect other teams.
Choose the organizational context
Open the entity the leadership role belongs to, such as a local, committee or bargaining unit.
Identify the leader type
Use the configured leadership role that matches the organization’s terminology and reporting needs.
Connect the person or user
Select the correct record and verify that the person’s identity and related organization are unambiguous.
Record effective term information
Add start, end and status details according to the organization’s policy. Avoid overwriting a previous term when a new term begins.
Review current and expiring terms
Use a recurring process to confirm active leaders, approaching end dates and vacancies before publishing or reporting.
Product view
Video demonstration
Related demonstration
Build a connected union structure
This conceptual guide shares the demonstration used by the main hands-on procedure.
Watch the captioned demonstration →Troubleshooting
Use the symptoms below to diagnose the workflow before widening access, adding duplicate configuration or bypassing an intended control.
A former leader still appears current
Review term dates and status on the relationship, then confirm the public site or report is using current effective 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.
- Current, future and ended leadership terms appear in the correct context and public output reflects only intended records.
- 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.