Cases & grievances

Union grievance management from intake to resolution.

Track union grievances with configurable case workflows. Keep assignments, evidence, deadlines and outcomes together, with controlled access for staff and members.

Case workspace

UnionStack shown with fictional demonstration records.

Operational outcomes

What this changes for the team.

See how this part of UnionStack helps your team organize the work and follow through.

A coherent case history

See the requestor, participants, activity, evidence, communication and outcome without rebuilding context from several systems.

Clear responsibility

Use assignments, urgency, progress and due dates to make ownership visible.

Analysis within access scope

Review intake, closures, backlog, issues, outcomes, aging and deadline performance without bypassing case permissions.

Deadlines with a policy source

Calculate staff deadlines from published agreement policies and business calendars, review source authority and escalate through approved delivery bindings.

Connected workflow

Follow the work through its record.

The exact configuration varies by tenant, but the accountable sequence remains visible.

01

Intake

Apply the right case type, number and initial participants.

02

Progress

Record activities, assignments, notes, deadlines and related meetings.

03

Evidence

Maintain documents, correspondence, expenses and awards with governed access.

04

Close and learn

Record the outcome, complete required work and review trends.

Try a complete workflow

Follow a grievance through a change of representative.

Demonstration scenario · Fictional records

Use a fictional grievance with an agreement reference, correspondence, evidence and a next action. The useful test is whether another authorized representative can take over without reconstructing the file from a private inbox.

  1. Establish the case context

    Select the applicable case type and workflow, relate the member and agreement, and identify the responsible staff. Verify the agreement version relevant to the issue rather than assuming the latest version applies.

  2. Make the next action explainable

    Review the next step, owner and evidence. Where published agreement-deadline policies and calendars are configured, inspect the calculation and its source. A configured reminder is not proof that a recipient acted.

  3. Reassign and close with context

    Use another authorized account to locate the correspondence and documents, continue the workflow and record the outcome. Check the member-facing view separately from the internal case record.

Evidence to review together

  • The replacement representative can identify the next action and its owner.
  • Deadline evidence and configured policy requirements can be explained.
  • Member access does not expose internal notes or unrelated cases.
Discuss this workflow

Boundaries

What evaluators should keep in view.

  • Staff deadline calculations and escalation use published agreement policies and business calendars. Automatic jurisdiction selection and general rules-driven correspondence remain future work.
  • Member summaries and documents remain governed by safe-publication rules.

Next step

Evaluate Cases & grievances with your own workflow.

Try a real workflow with the 30-day trial, or request a guided walkthrough with UnionStack.

Credit card required. Automatic billing after 30 days.