Workflow context
What this guide helps you accomplish
Close a UnionStack case deliberately by confirming progress, evidence, outcomes and follow-up responsibilities.
Closure confirms that required work is complete, records the approved outcome or award and leaves a coherent history for future users.
Closure is the point where the record should explain the result without depending on the memory of the people who handled it.
Before you begin
Prepare the following before changing shared configuration or records:
- A documented case procedure with intake criteria, participant responsibilities, progress stages and closure expectations.
- A fake member, organizational entity, agreement and supporting documents suitable for an end-to-end test.
- Users representing intake, assignment, investigation and closure responsibilities.
- A fake case at its final stage with approved outcome details and all material records connected.
Procedure
Complete the steps in order with fake or approved test information first. Record configuration decisions that will affect other teams.
Confirm the procedure is complete
Review required progress stages, submissions, meetings and approvals. Document any intentionally skipped step and the authority for that decision.
Record the outcome
Use the configured outcome or disposition that accurately reflects the result. Add concise explanatory context where the label is not sufficient.
Capture awards or obligations
Record applicable remedies, amounts, dates, conditions or follow-up commitments using approved fields and documents.
Review participants and evidence
Confirm the requestor, representatives, decision-makers, key communications and final documents are connected.
Assign remaining follow-up
Create or record any monitoring, payment, implementation or communication task that continues after the case itself closes.
Close and sample later
Apply the final status and include closed cases in periodic quality review to improve case-type configuration and practice.
Product view
Video demonstration
Related demonstration
Progress a case from intake to outcome
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 closed case still has unresolved assignments
Review open actions, participant communication and required documents. Complete or deliberately transfer the remaining work before closing the case.
The case cannot move to the expected stage
Check the selected case type, current progress state, required information and user access. Complete or correct the missing prerequisite before bypassing the designed path.
Participants are present but responsibility is unclear
Review each participant role and the assigned UnionStack users. Use roles to describe involvement and assignments to make operational ownership explicit.
Evidence is scattered across notes, files and email
Identify the authoritative source for each item, connect the conversation or document to the case, and use notes for analysis rather than duplicate copies of evidence.
Validation checklist
Do not treat the procedure as complete until an authorized second person can reproduce the intended result.
- The case has no unexplained open action and its outcome, award, evidence and communication support the closure decision.
- The requestor, participant roles and assigned users are unambiguous.
- Progress accurately reflects the work completed and the next required action.
- Material documents, conversations, meetings and governing articles are connected to the case.
- Closure records the approved outcome or award and leaves a usable operational history.
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
Grievance tracking software
See the feature evidence, connected workflows and buyer guidance behind this procedure.
Explore Grievance tracking software →Continue learning
Return to the UnionStack Learning Centre, or take the UnionStack product tour to see how these parts connect.