Planner: prepare assigned work before removing a member

For one existing Microsoft Planner plan and a current member, using the documented new experience. Exact plan type, permissions and visible controls remain unobserved. This is one-plan preparation, not organization-wide offboarding.

Separate membership, assignments and work

Microsoft's assignment guide, multiple assignees and removing a member says a removed plan member can still view and edit tasks assigned to them. To restrict that access, it says to unassign them from each assigned task.

Its current removal route is arrow beside Share → hover over the person → x. The page separately lists legacy and government-environment instructions; if those apply or controls differ, resolve the actual context before proceeding.

When any team member marks a shared task complete, it becomes complete for everyone. That is no per-person acknowledgement or proof of underlying work. Unassignment is not evidence that a successor accepted it, and plan removal is no global file, group or account-access revocation guarantee.

Prepare the handoff

Privately establish the exact plan and member, authority for the change, outstanding assigned tasks and intended access outcome. Titles or an old member list cannot establish the selected records. Agree who will take responsibility for unfinished work and what evidence establishes completion.

If assignment inventory, remaining responsibility or authority is uncertain, leave removal and unassignment pending. Return the selected plan, desired access change, remaining work and unresolved context; do not use a completion label to erase those questions. This guide supplies no premium-plan role matrix, account deletion, automatic reassignment or safe recovery procedure.

Evidence: The official page read through 2026-10-05T19:05:48.240783Z; no update date displayed. Sixteen synthetic author manual decisions checked; a distinct same-controller checker rechecked those sixteen decisions and six additional boundaries. Same-controller checking supplies no independent review. No plan, task, member, assignment, account or message action occurred. Recheck before use, after changed plan/interface/member/assignment facts and by 2026-11-05T19:05:48.240783Z. Follow the task standard [current article]. Feedback should identify the disputed public branch without task content, member addresses or private plan links.