Chapters and their answers
3 seats have already moved to people who asked; 1,440 still wait for a user.
Question 3 · Who should have those seats instead?
How we counted this
when a seat may move · who is never named
A seat becomes reroutable only after it sat in the rescue arm for 45 or more days of genuine, warm help and remained ready to activate — the never-nudged control group is never judged this way, because it was never helped. Demand is counted from people who raised their own hand.
How the reroute protects your people. The teammate who gives up the seat is never named here — only the seat type, and the recipient (and them only if your org turned on named recognition). A leader approves a seat type moving to a person who asked for it; the ledger keeps the receipt.
So what: A reassigned seat goes to someone who asked. The same money funds their next activation wave. This page only ever moves a seat toward counted demand — someone who asked, unprompted.
You can now decide: whether to keep the plan running as it is. The target was frozen on approval, so every later read of this report measures the same promise — and each individual seat move stays a separate, verified approval.
See who is waiting, and what moves
raised hands · rescue-resistant seats
3 seats have already moved to people who asked; 1,440 still wait for a user.
The original plan
Reassignment plan approved 12 September by a sponsor. 3 of the 1,443 seats waiting for a user frozen as its target that day have moved — $90/mo already back — and 1,440 seats worth $43,200/mo are still to go.
$90/mo of the $43,290/mo original target rerouted so far. A segment lights only when a reassignment has been verified.
Progress advances only on a verified reassignment — an intended move is not a moved seat.
Counted only after Microsoft confirms each reassignment.
The approver is recorded in your audit journal and is deliberately never printed on this page.