Hand over moderation as a set of responsibilities, not a password
Read the guide →Guide preview
Transfer the work, permissions and unresolved cases through authorised role changes and a clear acceptance check.
Maintain references, hand over responsibilities and review real outcomes.
Maintain references, hand over responsibilities and review real outcomes.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Transfer the work, permissions and unresolved cases through authorised role changes and a clear acceptance check.
Record who is responsible and how authorised recovery works; never turn an ownership sheet into a password collection.
A named backup needs the right task instructions and permissions before the main host is unavailable.
Separate routine community housekeeping from decisions requiring an owner, provider or appropriate specialist.
Assign an owner and review trigger to the few references members depend on most.
Know what you can retrieve, what you may retain and what requires provider help before you need to leave.
Evaluate member tasks, unresolved cases and ongoing workload separately from the platform’s activity counters.
Use explicit assumptions to explore support capacity; the result is arithmetic, not a forecast of member behaviour.
Track mutually exclusive observed stages and unresolved work; matching totals do not prove successful participation.