HR playbook · AI Employee: Harry

Manager Change Cascade

Reporting-line drift < 1 day system-wide

Install this playbookBack to marketplace
The problem

When someone changes managers, dozens of downstream systems need to know. PTO approvers, expense reviewers, GitHub reviewers, Jira watchers, quota-attainment rollups, 1:1 calendars, org-chart tools — every one of them has the old manager wired in somewhere. HR updates Workday and considers the job done. Two months later the old manager is still approving the ex-report's expenses.

At a glance
Trigger
HRIS event
Approvals
None (rule-based)
What it does
Writes to your systems
Systems
Workday · Okta · Slack · Lattice
How it feels in production

An hour-by-hour walkthrough.

Sarah moves from Priya's team to Kiran's team on 2026-10-01. HR updates Workday. Remy sees the change within an hour and starts the cascade. First, it inventories every system where Sarah's manager relationship is wired: Okta approval groups, Slack channels tagged to Priya's team, GitHub team memberships, Jira project roles, PagerDuty rotations, Concur approval chains, Salesforce forecast rollups, Google Calendar recurring 1:1s, and the internal org-chart tool. Then it plans the moves: - Approval chains (PTO, expenses, hardware): reassign to Kiran, effective 2026-10-01. - GitHub review teams: remove from Priya's team, add to Kiran's team, preserving repo access. - Slack channels: leave Priya's team channels after a 14-day grace, join Kiran's team channels immediately. - Recurring 1:1s: cancel with Priya on the effective date, propose new slots with Kiran. - Quota + forecast rollups: reassign in Salesforce, backdated to the effective date so mid-period reporting doesn't double-count. - Documentation: update org-chart tool, HR profile, email signature template. The plan gets reviewed by HR (usually rubber-stamped). On approval, Remy executes in dependency order (access before removals so nothing is dropped mid-transition), verifies each write, and files the cascade record with per-system status.
How it works

Step by step.

  1. 01

    Detect the manager change in HRIS

    Poll HRIS on 15-minute cadence for manager-relationship changes. Effective-dated changes queued for the effective date; retroactive changes triggered immediately with a cutover window.

    Workday · BambooHR · HiBob · UKG · ADP
  2. 02

    Inventory every system holding the relationship

    Enumerate every downstream system: approval chains, review teams, Slack channels, PagerDuty rotations, expense chains, forecast rollups, calendar recurrences, documentation. The list is stable per company; kept in the runbook.

    Runbook · System registry · Context Graph
  3. 03

    Plan the moves with dependency order

    Add-then-remove ordering: new access before old removal so nothing drops mid-transition. Grace periods where relationships have handoff obligations (Slack channels: 14 days; ongoing tickets: reassigned individually with the incumbent's blessing).

    Cascade planner · Dependency graph
  4. 04

    HR review + one-click approve

    Cascade plan surfaced to HR with per-system move preview and the moves that need judgement (does the person keep GitHub access to the old team's repos, do open tickets transfer). Approve as-is or edit.

    Web UI · Slack · Teams
  5. 05

    Execute + verify + file the record

    Execute in planned order. Each write is verified — read back the state to confirm it took. Failed writes retry once, then flag for manual. Full cascade record filed to the person's HR profile as an immutable audit event.

    Okta · Slack · GitHub · Salesforce · Concur · Calendar · Audit log
Systems and wiring

What you connect to make this run.

Workday · BambooHR · HiBob

read

HRIS is the source of truth for the manager relationship. Read the change event; never write back — HR owns those records directly through the HRIS UI.

Okta · Google Workspace · Microsoft Entra

read+write

Identity + group membership. Approval-group moves, dynamic-group re-evaluation. The identity plane is the fanout point for most downstream approvals.

Slack · GitHub · Jira · PagerDuty

read+write

Team-scoped rewires. Slack channel membership with grace period, GitHub review teams, Jira project roles, on-call rotations. Preserves individual repo / project access even after team moves.

Salesforce · Concur · Ramp · Google Calendar

read+write

Business-process rewires. Forecast rollups, expense approval chains, recurring 1:1 calendar entries. Effective-dated to prevent double-counting or missed approvals during transition.

What changes

Before and after, honestly.

Time from HRIS change to full cascade complete
Before
2-8 weeks (systems drift for months)
After
Under 30 minutes on the effective date
Systems out-of-sync 60 days post-change
Before
30-50%
After
Under 2%
Approvals routed to wrong (old) manager
Before
10-30% for 8+ weeks
After
Under 1% (immediate cutover)
HR hours per manager change
Before
2-4 hours (chasing every system)
After
5-10 minutes (review + approve)
Related

Playbooks that pair with this one.

HR

Role & Manager Changes

The employee-facing side; this playbook handles the system-facing side.

HR

Employee Offboarding

Extreme cascade: same mechanism, but every relationship terminates rather than moves.

RevOps

Territory & Account Reassignment

Same cascade pattern for sales-org changes; often triggered by the same reorgs.

Frequently asked

Answers about this playbook.

How does it handle reorgs that move whole teams at once?

Batches the cascades. A 12-person reorg becomes one review with 12 dependent moves. Dependencies enforced (managers moved before their reports so the report cascade lands on the correct new manager).

What about matrix reporting (dotted-line managers)?

HRIS captures dotted-line separately from primary. The cascade respects both — some approvals key to primary (PTO, expenses), others to dotted-line (project-level approvals, code review teams). Runbook defines the split per system.

Can we roll back a cascade if the change was a mistake?

Yes — every cascade is reversible from the audit log. HR triggers a reverse cascade to the prior state. Common on retroactive HRIS corrections.

What if the new manager doesn't want inherited access (e.g. Slack channels the old team owned)?

The new manager sees the inherited set on cascade completion and can trim. Grace periods make removal a no-op most of the time — nothing is silently kept, nothing is silently removed.

How does it handle contractors + non-employee reports?

Same cascade if the contractor is in HRIS with a manager relationship. Systems where contractors are represented separately (some GitHub Enterprise setups) are called out in the runbook and handled manually.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore HR playbooks