HR workflow around a departure (collective card)

On the HR process side, connect this workflow to a group farewell card you can share with teams.

This workflow outlines HR’s role around a departure: light guardrails, coordination with the manager, alignment with the HRIS, and deliverables (guestbook, PDF export) without policing private sentiment. It targets people teams balancing compliance, employee experience, and manager workload.

End-to-end flow

Copy the sequence below into your knowledge base; adjust timings to internal policy and local legal requirements.

[ HRIS: exit status & end date confirmed ]
           |
           v
[ HR + Manager: announcement calendar & channels ]
           |
           v
[ HR: tool access / data policy / archiving rules ]
           |
           v
[ Manager: launch guestbook + peer relays ]
           |
           v
[ HR: moderation touchpoint if flagged ]
           |
           v
[ Close contributions -> PDF export -> Controlled distribution ]
           |
           v
[ HRIS / records: retention window & link deactivation ]

HR step-by-step

1. Data alignment: confirm end date, communicable reason, and any restrictions on public mention inside the HRIS.
2. Light legal framing: restate language rules (non-discrimination, no sensitive data) without sanitizing sincere tributes.
3. Enablement: open or approve guestbook access; document the admin owner and support channel.
4. Check-in: mid-window pulse if volume is unusually low; use avoiding an empty team card for levers.
5. Closure: confirm export recipients and format, then archive per group policy.

Before the announcement

Confirm end date and communication channels with the manager. Keep a neutral announcement template if several exits happen in a row—consistency matters. If the HRIS publishes exit paperwork to the employee portal, sync internal comms timing to prevent parallel leaks.

Personal data and contributions

Remind internally that notes should stay professional: no sensitive data, no discriminatory lines. The manager is the first line; HR steps in on reports. If your records of processing require explicit consent for certain photos, bake that step in before the final PDF export.

Manager handoff and HRIS touchpoints

HR often opens the process (tool access, archiving policy), but the manager drives momentum: nudges, tone, closure. Write that split into your internal playbook. In the HRIS, log at minimum: board open date, close date, export owner, and public link retention.

Asset	Primary owner	Suggested HRIS / IT trace
Guestbook admin access	HR or approved IT delegate	Named account + revocation procedure
Contributor nudges	Manager	Message templates in the manager playbook
Keepsake PDF export	Manager or HR per policy	Dated filename + secured storage path
Public link deactivation	HR / tool admin	Scheduled date on the closure ticket

Archives and access

Clarify who receives the PDF export (leaving employee, manager, HR). If the guestbook is public, define how long the link stays live after the last day. For PDF layout and branding detail, see the company PDF export guide; for chat announcements, read announcing a departure on Slack or Teams.

Urgent exits and compressed timelines

When only a few days remain, continue with last-minute farewell card and launch a team card in five minutes. Managers should prioritize a handful of key contributors instead of a broad campaign that cannot land.

HRIS integration: fields and light evidence

A guestbook is not a contract artifact, but it is evidence of employee experience. In the HRIS, a short note may be enough: export delivered, to whom, and when. Avoid pasting full message bodies unless policy demands it—this lowers accidental oversharing risk. If your HRIS auto-spawns offboarding tasks on the exit date, align a “close guestbook” task with the same timeline as laptop return.

Sensitive cases

Disciplinary exits, settlements, or media-sensitive moments may not suit a public collective card. Document when the ritual is paused or confined to a private channel. When teams learn about a departure late, keep public messaging factual and collect notes by invitation only.

Continuous improvement

After each exit wave, a five-minute HR-manager debrief is enough: Was the window realistic? Did people understand the link? Did the export land on time? Those three questions feed a living internal guide without heavy process.

Cross-team alignment with internal comms

When an exit hits multiple channels, HR should sync the official post with guestbook opening. A few hours of drift can spark leaks or confusion about whether notes are public. A fifteen-minute huddle with HR, comms, and the manager often saves a day of cleanup.

One-page playbook summary

Goal: deliver a collective keepsake without breaching confidentiality or overloading managers. Principles: one canonical link, a published window, a named closer, a secured export, a scheduled link deactivation. Escalate to HR on discriminatory content or sensitive data leaks. This half-page brief aligns new HRBPs and people managers faster than a sixty-slide training deck.

Peak season staffing

When reorgs or seasonal contract ends cluster, guestbook volume spikes the same week HRIS tasks spike. Block a short weekly review for access approvals and IT escalations so managers do not wait on a bottleneck. The time cost is tiny compared to the goodwill preserved when several exits land at once.

Manager enablement assets

Package a three-item bundle in your HR portal: announcement template, guestbook brief, and nudge schedule. Managers should not hunt three different wikis at 5pm on a Thursday. Centralizing assets cuts rework for HRBPs and keeps tone consistent across teams that rarely share managers.

Union or works-council contexts

In some geographies, collective representation affects what can be said publicly about exits. HR should pre-check phrasing with labor relations before a broad guestbook opens—especially when timelines are negotiated rather than purely managerial.

Documentation handoff to IT offboarding

Make sure IT knows when to revoke guestbook admin rights in the same ticket as email and SSO shutdown. A dangling admin account is a small but real attack surface; closing it with other access removals keeps security and people ops aligned.

Related reads

Manager departure checklist, the colleague farewell card guide, and the digital guestbook at work pillar complement this workflow in the field.

Read next

1. Farewells

   Manager wrap for the last days without chaos

   To round out your farewell flow (lines, structure, timing).

2. Farewells

   Farewell card reference from tone to PDF

   To avoid last-minute awkwardness on the card.

3. Farewells

   Tight-window kit: invites, openers, PDF backup

   To move from collection to the team moment (party, PDF, announcement).

Frequently asked questions

When should the card step enter the HR workflow?

After the internal announcement is approved and before the last working day: too early without framing fails; too late yields empty cards. Treat it as a cultural step, not a contract channel.

What data should never be requested on the card?

Avoid performance scores, health details, customer secrets, or compensation cues. The card is not an HR file.

How do we attach the exported PDF to the HRIS?

Use the intended document repository (employee file or ECM) with minimal metadata (date, type “farewell tribute”, owner). Avoid orphan attachments in personal mailboxes.

Who owns the ritual on the business side?

The line manager, with HR sign‑off on sensitive cases. HR supplies guardrails; the manager runs facilitation.

Can we automate nudges from the HRIS?

Sometimes via standard notifications, but keep the tone human—a single link plus calendar reminders often beats long robotic emails.