Define the stages before counting
Use one current stage per person for the aggregate board: not yet invited, invited with no later observation, account claimed but access unconfirmed, intended access confirmed or help in progress. If your real process differs, keep the definitions alongside the counts. A person awaiting help should not also inflate the confirmed-access total.
Reconcile the scope
Compare the sum of current-stage counts with the number of unique people in the agreed transition scope. A difference may indicate missing observations, duplicate counting or a changed scope. A matching total establishes only arithmetic consistency. It does not verify identities, permission to contact members or the quality of their community experience.
Keep private cases elsewhere
Use an authorised restricted system for individual help cases when necessary. This public worksheet accepts aggregate numbers only and does not save them. Do not paste names, addresses or case narratives into a shared planning tool. Assign owners to unresolved categories without publishing a list of people who have not responded.
A fictional board review
A group expects fifty members and records ten not invited, fifteen invited, five accounts awaiting an access check, fifteen confirmed and five receiving help. The counts reconcile to fifty, while ten still need an access decision or assistance. The group does not report a hundred-percent successful transition. It uses the board to identify the next practical workload and preserves the uncertainty behind each aggregate category.
Before you close this task
When the scope changes, explain the added or removed members before comparing totals across dates. Do not move unknown outcomes into confirmed access to make a progress chart look complete. A board with an honest unresolved category is more useful than a visually balanced report that conceals the work the next helper needs to do.
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
- Mighty privacy policy — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Welcoming members — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28