What to look for in a pre-arrival community platform: a checklist for admissions teams 

At Uni-Life we always know we'll at least get two questions: what features it has, and how much work it will be for my team. 

The feature list rarely predicts anything. And the workload question, which used to be the right one to ask, has largely stopped being useful. This category has converged on running the community for you. We do it, and so do some of the credible alternatives. If a vendor tells you their platform is low effort for your staff, they are almost certainly telling the truth, and they are also not telling you anything that separates them from anyone else. 

So, the interesting questions are elsewhere. Here is the list we would use, drawn from watching these projects work and fail. 

1. What share of offer holders actually use it? 

This is the question that replaced "who will run it," and it is now the whole ballgame. 

A managed community can still be a quiet one. The vendor posts, the campaigns go out, the dashboard fills in, and the students do not come. That is the real failure mode in this category, and it is much more common than an overworked admissions team. 

So, ask for an adoption rate, defined properly: what percentage of invited offer holders created a profile, and what percentage had a real interaction with another student rather than a single login. Ask for the range across their customers, not the flagship number. Ask what the weakest one looks like. 

Member count is not an answer. Neither are registrations. 

2. Is this the whole product, or a feature bolted onto something else? 

Several platforms in this market started somewhere else, in ambassador chat, in campus engagement, in the CRM, and added a community module later. 

That is not disqualifying. It does tell you where the product roadmap will go and whose problems get solved first. Ask when the community product launched and what share of their engineering goes into it now. 

3. Does it need your students to become ambassadors? 

Some models run on student ambassadors: you recruit them, train them, sometimes pay them, and the community depends on them showing up. 

That can work well, particularly where you already have a good ambassador programme. But it is a different operating model with a different failure mode, and it is worth knowing which one you are buying before the exam period arrives, and your ambassadors disappear. 

4. Show me what actually happens in February 

Communities are not uniformly busy. There is a spike when invites go out, and then there is a long middle. 

Since the vendor is running the engagement, ask to see it. The actual content calendar for a real university, for a quiet month. Not the launch plan. If what comes back is a list of features rather than a programme, you have learned something important. 

5. What is that number on the slide actually comparing? 

You will be shown a conversion figure. Three questions about it: 

• What is the control group? If the comparison is "students who joined versus students who did not," it measures who volunteered, not what the product did. Students keen enough to join in March were already more likely to enrol. 

• Which product earned it? Some of the most quoted numbers in this category came from a different product in the same vendor's range. For instance, a strong calling campaign earlier in the journey resulted in more students being excited to join a community further down the journey. 

• Has anyone outside the vendor checked it? 

6. Where does the data live, and can you get it out? 

Who is the controller and who is the processor? Where is it hosted? What the export actually looks like in practice rather than in theory? What happens to it if you leave? 

Ask for the DPA earlier than late. This is the most common reason a three-month process becomes a nine month one, and it is far easier to clear in month one than in month five when everyone has already decided. 

7. What are the moderation terms, not who does the moderating? 

Everyone will tell you they moderate. That is the low effort promise again, and it is probably true. 

The differences are in the terms. What hours are covered. How fast is the response. What is the escalation route when a student says something worrying at 23:00 on a Sunday, and who at your institution gets called. Where does liability actually sit. 

Get it in the contract rather than in the demo. This is the risk that keeps people awake and the one most likely to be met with a reassuring shrug. 

8. What do you measure, and what will you not claim? 

The good signals are proximal, because they are yours and you can verify them: profile creation, real interactions, sentiment, what students are anxious about, speed from signed to alive. 

A vendor who tells you where their claims stop is more trustworthy than one whose claims do not stop. If everything is attributed to the platform, nothing is. 

9. How long from signed to live? 

Ask for the range, not the best case. Then ask what they need from you during it and who at your end produces it, because that is the part that slips, and it is where the low effort promise gets tested first. 

10. Does it integrate with your CRM or student record system? 

And if not, who is moving the offer holder list, how often, and under what agreement. A weekly CSV is a real answer. It is just not the same answer as an integration, and it should not be priced like one. 

11. How does pricing move when your numbers move? 

Most pricing here keys off offer volume, ours included. Ask what happens if volume drops 20%, because in the current climate it might. Ask what happens if it grows. Ask what is inside the number and what becomes a professional services line later. 

12. Who can you talk to who looks like you? 

The most reliable signal in the process, by some distance. Not the flagship logo. A university of your size, your funding model, your region, ideally live for two intakes rather than two months. 

The research on how these decisions get made is clear that peer references outrank vendor evidence, and they should. Ask for a reference that is close to you rather than impressive and ask what they would do differently. 

The question underneath all twelve 

Effort used to be what separated these platforms. It is not anymore, and a lot of evaluation forms have not caught up. 

What is left, once every credible vendor is running the community for you, is simpler and more useful: do the students actually turn up, and can the vendor prove it. That is the one thing in this category that genuinely varies, and the good news is that you do not have to take anyone's word for it. Ours included. 

‍