# Approval Roster Change Impact

Explain how changed review membership can make an old approval summary unreliable.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Two dated level rosters, stable user IDs, post version, approval events and supplied transition policy.

## Workflow
1. Diff the rosters by level and user ID rather than display name.
2. Separate removed reviewers, added reviewers and moved reviewers.
3. Retain old approvals as historical evidence, not automatic approval under a new roster.
4. Ask the owner how changes apply to pending posts; no access or workflow change.

## Output contract
level | old_roster | new_roster | change | prior_event | current_policy_gap

## Fictional acceptance test
Fictional legal level changes from A to B after A approved. Record A historical approval and B current membership. With no transition rule, hold whether the old event satisfies the new level.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://help.planable.io/hc/en-us/articles/21715417710876-Multi-level-approvals

Checked October 10, 2026. Oct10 live AIS Search Console through Oct6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.