Independent research · Source-linked guidance
Home / Prepare / Member communication
Practical guide

Explain a community move without promising that everyone has seen the message

Last materially reviewed 2026-09-28

Quick answerPublish one authoritative set of transition instructions and treat delivery, reading and successful access as different stages.
What to know

Make one message authoritative

State what is changing, what is not, when action is needed and where to get help. Link to one maintained instruction page rather than distributing conflicting versions across channels. Use the vocabulary members already recognise. If dates or routes change, update the authoritative page and make the correction visible instead of silently relying on an older announcement.

What to know

Separate notice from completion

A posted notice, an email delivery and a member’s successful arrival do not establish the same thing. Notification preferences and device settings can affect what people receive. Avoid declaring everyone informed because an administrator clicked send. Plan a proportionate way to identify unresolved access without exposing a public list of non-responders or sending repeated unnecessary messages.

What to know

Give the message an owner

Assign responsibility for corrections and incoming questions. Explain the actual support window without inventing a guaranteed response time. Provide an alternative help route that a locked-out member can reach. Keep promotional language out of operational instructions: a person trying to find their existing group needs a clear route, not a sales pitch for the new platform.

What to know

A fictional update

A community moves its rehearsal by two days after finding an access issue. Its owner updates the central instructions, posts a short correction through the existing agreed channel and retains the prior date in the change record. The owner does not assume that the correction reached every member. Outstanding cases remain visible in a private operational queue until the relevant task is resolved.

What to know

Before you close this task

Give each instruction version a clear date and owner. When a helper answers a repeated question, improve the central explanation if appropriate rather than creating another competing set of steps. Keep the original member-facing problem visible so the edit can be checked against a real task.

Continue when useful

Next: First visit

Welcome an existing member back to their community before introducing every feature of the new platform.

Open First visit →
Keep exploring

Related guides

First visitWelcome an existing member back to their community before introducing every feature of the new platform.NotificationsExplain notification choices and a dependable way to find essential information; do not equate sending with reading.Member helpA locked-out member needs a reachable help route that does not require access to the locked space.

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Host notifications — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28
  2. Welcoming members — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28