Bring one real workflow
Choose a common grievance, inquiry or organizing process and identify its people, roles, stages, documents and outcome.
Product tour
Follow a piece of union work from signal to resolution.
This guided tour shows how UnionStack keeps people, cases, email, meetings and reporting connected as work moves forward.
The scenario
A member raises a workplace concern. The team needs to act without losing context.
The representative confirms the member’s position, creates the right case, connects the email thread, schedules preparation and records the outcome. The tour below shows what happens at each step and what remains connected.
This is a representative workflow, not a fixed template. Case types, stages, roles and terminology can be configured around the union’s own procedures.
01
Start with the work that needs attention.
The representative opens the dashboard to review unassigned cases, their open and closed work, and upcoming events. A new concern can be triaged alongside the team’s current workload instead of disappearing into a personal task list.
What remains connected
Learn how dashboards support daily work →
Workload, ownership and scheduled activity remain visible from the starting view.
Unassigned casesCurrent view
08My open casesRelated information
1402
Open the member record and confirm the working context.
Before opening a case, the representative checks contact information, the active position and location, and any relevant notes or connected activity. That establishes who the work is for and where it belongs in the organization.
What remains connected
Learn how to maintain people and positions →
Positions, terms, locations, documents, notes, custom fields, cases and meetings can remain connected to the person.
Active positionCurrent view
North FacilityConnected casesRelated information
0203
Create the right case type and establish a clear path.
The representative selects the appropriate case type, identifies the requestor, adds participants with their roles and records intake details such as channel, source, impact or urgency. Responsibility is assigned and the case enters its configured progress path.
What remains connected
Follow the complete case-management workflow →
Requestor, participant roles, assignments, categories, stages, related entities and parent or child cases stay on the case record.
Document reviewCurrent view
In progressParticipantsRelated information
0404
Bring the conversation and its evidence into the case.
A Microsoft, Gmail or IMAP/SMTP account can be connected. The relevant conversation is related to the case so authorized users can find the messages and attachments beside the work they support.
What remains connected
See how to link email to UnionStack records →
The conversation retains its senders, recipients, messages and attachments while its relationship to the case supplies context.
Linked messagesCurrent view
06AttachmentsRelated information
0305
Prepare the people and the record for the next meeting.
The team schedules a case-preparation meeting, adds person and user participants, records the location and attaches the documents people need. The meeting is related back to the case and organizational entity.
What remains connected
Learn how to prepare meeting records →
Participants, documents, tags, location, case and entity relationships remain available from the meeting.
ParticipantsCurrent view
05DocumentsRelated information
0406
Record the result and make the work measurable.
As the matter progresses, users update its stage and supporting records. At closure, the team records the relevant outcome or award and retains the evidence behind it. Dashboards and operational reports can then reflect maintained work instead of a separate reporting spreadsheet.
What remains connected
Review a dependable case-closure procedure →
Progress, outcomes, awards, assignments and related activity supply an auditable operational history.
Ready to closeCurrent view
03Related recordsRelated information
1207
Extend the right experience beyond the staff workspace.
The union can publish selected meetings, documents, leadership and contact information through a public entity site. A separate authenticated site can give members access to protected experiences based on the configured people type.
What remains connected
Plan public sites and member portals →
Public and authenticated experiences stay distinct while drawing on the union structure and records maintained in UnionStack.
Public contentCurrent view
LiveMember accessRelated information
ProtectedBuyer guidance
Turn the product tour into a useful evaluation.
A convincing demonstration should show your real operating questions, not just a polished interface.
Test your structure
Confirm the system can represent your locals, regions, employers, bargaining units and workplaces without flattening them.
Trace access
Ask which staff roles can view or change each record and how public versus member information is separated.
Inspect the handoffs
Follow email, meetings, documents, reporting and site publishing to see whether context survives between teams.
What to explore next
Go deeper where your buying team needs evidence.
Review the feature architecture, examine security controls, compare public and authenticated sites, or use the Learning Centre to evaluate a specific procedure.
Built for connected work
Now see what UnionStack can do for your team.
Start a 30-day free trial or continue into the practical learning guides.