Use operational differences
Identify members with different starting states: current access, lapsed access, event-only participation or administrative duties. Also consider device and accessibility needs when volunteered or appropriately known. These differences can change the instructions required. Do not infer competence, disability or willingness to participate from a person’s age, profession or frequency of posting.
Keep the record proportionate
A planning count often needs only the number of people following each route and a responsible helper. Do not copy private member details into our tools; they accept aggregate numbers only. If your own operational records require identities, use an authorised restricted system and follow the relevant obligations. A public transition dashboard should never expose a list of members who have not responded.
Avoid accidental double counting
A moderator can also be a paying member and an event participant. Decide whether groups are mutually exclusive for counting or overlapping for task coverage. State that choice beside the totals. A useful rehearsal may include one person performing several tasks; that does not mean several independent members have successfully transitioned.
A fictional cohort plan
A society identifies forty regular participants, twenty occasional readers and four moderators. Some moderators are already among the regular participants. The support estimate counts unique people, while the rehearsal checklist counts distinct journeys. The group writes this distinction on both sheets. Otherwise, a reassuring total could conceal a missing event-only route or inflate the number of people believed to have completed their transition.
Before you close this task
Record the denominator and the date beside each aggregate count. If the group changes while preparation is underway, reconcile that change before comparing progress. A difference between two reports may come from different scopes rather than a lost member or a failed invitation.
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.
- Member purchase and access — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Personal settings — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28