Total members is in every community report because it only ever goes up. That is precisely why it is useless: a number that cannot fall cannot tell you anything went wrong.
Of all replies in a period, how many came from members rather than staff. This is the single clearest signal of whether you have a community or a support queue, and it can be counted by hand.
Do this: Count one week of replies, split by team and member. Under half means the room depends on you.
Of people who post once, how many post again. It tests welcome, onboarding and whether the first experience was good. It is also the number most likely to be terrible when you first measure it.
Do this: Take everyone whose first post was three months ago and check how many posted since.
Tell us members, posters and who answers. We reply with the stage you are at and the one thing to change first.
The share of questions receiving any human reply within twenty four hours. Every unanswered question teaches the audience not to ask, and that damage is invisible in totals.
Do this: Set an alert for questions with zero replies after a day. Fixing this is usually the fastest improvement available.
What proportion posted or replied in the last month, and how many went quiet. Reporting churn alongside growth is what makes the two numbers honest, and it is why most reports omit it.
Do this: Put churn in your next report. Expect the meeting to be more interesting than usual.
This is teaching material and our own reading of standard practice, not advice for your specific community. Check anything important with your own specialist before you act on it.
How many members, how many post, who answers questions. We reply with the stage you are at and the one thing to change. No call, no pitch.