Skip to content
UnionStack logo UnionStack

Learning centre · People & structure

Connect agreements and articles

Organize agreements and articles in UnionStack so teams can connect governing language to the relevant work.

Workflow context

What this guide helps you accomplish

Organize agreements and articles in UnionStack so teams can connect governing language to the relevant work.

Agreement records provide scope and effective context; article relationships let representatives find governing language without copying it into every case.

Working principle
The authoritative agreement remains the source; UnionStack relationships make that source easier to find in context.

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 or public agreement excerpt with authoritative title, scope and effective period.

Procedure

Complete the steps in order with fake or approved test information first. Record configuration decisions that will affect other teams.

01

Identify the agreement owner and scope

Confirm which entity, bargaining unit, employer or workplace the agreement applies to and who maintains the authoritative copy.

02

Record clear agreement details

Use consistent titles, effective dates, expiry information and status so users can distinguish current and historical agreements.

03

Organize articles for discovery

Use article names or identifiers that match the source document and the terminology representatives use.

04

Connect cases and entities

Relate the agreement or article to relevant records rather than copying text into several case notes.

05

Review after renewal or amendment

Add the new effective information, preserve required history and check cases or site content that reference the previous agreement.

Product view

UnionStack agreement and article records connected to a union entity
UnionStack 2.0 test environment using fake data. Interface details may vary with your organization’s types, fields, permissions and terminology.

Video demonstration

Troubleshooting

Use the symptoms below to diagnose the workflow before widening access, adding duplicate configuration or bypassing an intended control.

Users cannot tell current and historical agreements apart

Use clear status and effective information, retain recognizable titles and connect each agreement to the entity or bargaining context it governs.

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.

  • A representative can move from the test case or entity to the correct effective agreement and article.
  • 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

UnionStack 2.0

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.

Continue learning

Return to the UnionStack Learning Centre, or take the UnionStack product tour to see how these parts connect.