What can you actually measure about a pre-arrival community? The numbers that are yours 

At Uni-Life we provide universities with a real-time dashboard on their engagement levels. When we review the dashboards together, the questions we get are rarely about features. It is always some version of: which of these numbers should I actually care about, and which one do I put in front of my Pro Vice Chancellor? 

It is the right question, and the honest answer is that two numbers decide almost everything, the gap between them tells you more than either one on its own, and several of the numbers you will be shown are not measurements at all. 

Here is the full list we would report, and why the denominator can sometimes matter more than the metric,  

The two numbers that decide everything 

What share of invited offer holders created a profile. Not registrations, not downloads. A profile, because in a community product, a profile is the thing that makes anyone findable. 

What share had a real interaction with another student. A message, a reply, a comment, a connection accepted. Not a login. 

Between them they answer the only two questions that matter early: did the students come, and did anything happen when they got there. 

The gap between the two is the story of the account. High profile creation with low interaction means the invitation worked and the room was empty. Students turned up, looked around, found nothing to do, and left. That is a content and programme problem, and if the vendor is running the engagement it is the vendor's problem, not yours. Ask for both numbers every month and watch the distance between them. It is the earliest reliable signal that something is going wrong, and it appears months before anything shows up in a satisfaction survey. 

Check the denominator before you check the number 

An adoption rate is a fraction, and almost all the argument is in the bottom half of it. 

Universities give a vendor an estimate of how many offer holders they expect to invite, usually early, usually before the cycle has settled. Actual offer volumes then move, sometimes a lot. If the rate is still being calculated against the original estimate, it is measuring the forecast as much as the community. 

We calculated ours that way for longer than we should have. It is an easy error to make, it flatters some accounts and unfairly punishes others, and it is worth one direct question at the start of every reporting conversation: what exactly is the denominator, and is it the real number. 

There is a related effect worth knowing about, because it changes what a good adoption rate means. Adoption tends to track the students who eventually enrol more closely than the students who were offered. That is the self-selection point from the other direction: the population that joins a pre-arrival community overlaps heavily with the population that was always going to turn up. It does not make the number useless. It does mean a 40% adoption rate against offer holders is not the same claim as 40% of your future first years, and nobody should let you believe otherwise. 

What else is worth reporting 

Beyond the two, four things earn their place: 

• Sentiment, and its direction. Not a score in isolation. Whether confidence is rising or falling as the intake approaches. 

• What students are actually asking and anxious about. This is qualitative, it does not fit in a dashboard tile, and it is the most undervalued output of a pre-arrival community. It tells your accommodation team what is coming, your visa team where the confusion is, and your marketing team which of their answers is not landing. 

• Time from signed to live. A capability measure that turns into a commercial one, for reasons in the next section. 

• How much of your staff's time it consumed. Ask for it in hours. If nobody is counting it, that is an answer too. 

Time to first meaningful data is itself a metric 

This is the one most evaluation processes miss, and it costs universities real money. 

Suppose you sign in June and launch in August for a September intake. The community works, students join, conversations happen. Then you reach your renewal conversation with a single intake of partial data gathered under time pressure, and you have to argue for a budget line on it. 

That is not a platform failing. It is a calendar failing, and it is entirely predictable at the point of signing. The fix is to treat the date your data becomes meaningful as a contractual question rather than an operational one. Ask when the community will be live, then ask separately how many complete intakes you will have measured before the renewal decision. If the answer is fewer than two, either move the start date or move the renewal date.  

Numbers that look like measurement and are not 

• Member count. A count of people who once clicked a link, including everyone who muted it in March. 

• Registrations or downloads. They measure your invitation email, not the community. 

• Total posts. Ten students posting forty times each is not a community, and it reports identically to forty students posting ten times each. 

• A single composite engagement score. Several platforms offer one. If you cannot see the inputs and the weightings, you cannot audit it, you cannot compare it across vendors, and you cannot defend it upward when someone asks what it means. Ask for the components. If the components are not available, treat the score as decoration. 

What we will not report 

We do not attribute enrolment to the community, and we will not put a conversion uplift in a report we write for you. Enrolment sits months downstream of a hundred other things, and no vendor in this category, us included, can isolate a causal contribution to it. We have written separately about why that is, and about the self-selection problem sitting under every outcome number in this market. 

That is a deliberate limit rather than missing data. Report the proximal numbers, which are genuinely yours and verifiable from your own dashboard, and draw your own conclusions about what they are worth. 

What this actually gets you 

None of this is enrolment, and it would be easy to read the list above as a smaller offer than the one on a competitor's slide. It is not, because it is the half you can act on. 

The questions students are asking in July tell your arrival team what August looks like before August happens. The gap between profile creation and interaction tells you whether you are being served well, months before the renewal meeting where you would otherwise find out. And when someone senior asks whether the platform is working, you have an answer that came from your students rather than from a vendor's case study. 

The measurement you can defend is worth more than the measurement you would prefer to have. It is also the only kind that survives the second question. 

If it would help to see what a month of this looks like for a university of your size, including the numbers we would not show you, we are happy to walk through it.