This is a guest blog from Student CRM, purpose-built platform for UK education recruitment.

Have we met before? The student remembers. Can your teams see the whole story?
You don’t need to be an ABBA fan to appreciate the value of knowing a little about the person you’re talking to. Especially when they’re picking up a conversation your colleague started at an open day, and the record of it is tucked away in a spreadsheet, an inbox, a notebook or another system.
With different teams involved in school visits, open days and enquiries, the information can be scattered across the university. For the student, though, it’s all part of the same story.
A prospective student speaks to someone at a school visit. A few weeks later, they attend an open day. They ask a question about a course, take away a prospectus and perhaps make an enquiry when they get home.
Each interaction tells us something. They may be interested in a particular subject but unsure about entry requirements. They may be weighing up two courses. A conversation with an outreach officer may have given them the confidence to visit campus in the first place.
Outreach knows what happened at the school visit. Events can see who attended the open day. Marketing knows which communications the student received. Admissions may later see an application (fingers crossed, as that is rather the point of all this!)
Everyone has done their part, yet it can still be difficult to see how those parts fit together.
Joining those interactions together can help teams recognise what might encourage a student to take their next step, from visiting campus to applying or accepting an offer. It also helps answer a question that is often surprisingly difficult: what difference did our recruitment work actually make?
Student recruitment teams are rarely short of activity. There are visits to organise, events to deliver, questions to answer and communications to send. Each one takes planning and care.
The difficulty comes when the information gathered along the way sits in separate places, or is recorded in a way that only one team can use. A useful conversation can become a note on a spreadsheet. An event attendance can become a number in a report. An enquiry can be resolved without the wider context being visible to the person who speaks to that student next.
Many universities already have several systems supporting recruitment. The challenge is whether the people involved can see enough of the same student journey to decide what should happen next. Can outreach see whether a school visit led to an open day booking? Can marketing recognise when an enquirer has become an applicant? And can admissions build on the conversations that came before?
When teams cannot see that progression, it becomes harder to recognise where a timely follow-up might help, which applicants would benefit from further contact and where recruitment effort is making a difference. Useful opportunities can slip between teams, even when each team is working hard.
All this context can make a difference straight away. If a student attends a school talk but has yet to visit campus, an invitation to your next open day could help them take that interest a step further.
If they are choosing between two subjects, an invitation to a relevant taster session may be more useful than another general email. And if they have expressed an interest in a particular course, you could put them in touch with a student ambassador studying it, giving them a chance to ask questions and hear about the experience first-hand.
Seeing what has already happened also helps colleagues coordinate their follow-up. They can build on a previous conversation, recognise the next useful opportunity and avoid sending an invitation to something the student has already attended.
Small details can help teams offer a more relevant next step while the interest is still fresh.
Imagine looking back at that student’s journey six months after the school visit. Which details would help you understand it?
The fact that a visit took place is useful. So is attendance at an open day. But the questions the student asked, the interests they expressed and whether anyone followed up may tell a more helpful story.
That does not mean recording everything. Recruitment teams already have enough administration, and nobody is hoping for another spreadsheet with a heroic number of tabs. The aim is to make better use of the information gathered through existing work.
Looking back, those connections can help teams explore whether students who engaged with particular activities went on to enquire, apply or accept an offer. They will not explain every decision or prove that one interaction caused an application. But they can provide a fuller picture of student progression and help teams decide where to focus their effort.
Most universities have committed people doing good work at every stage of recruitment. Helping those teams see and use the wider picture creates opportunities to build on that work.
That is one of the reasons Student CRM is built specifically around UK education recruitment. Courses, enquiries, school engagement, open days and applications are not separate activities to bolt together later; they are parts of the same recruitment journey.
At the HELOA National Conference in January, Andy Speed from Student CRM will explore this in an interactive workshop: “Everyone owns part of the journey. Who moves it forward?”
We will look at the places where useful information can become disconnected and work through how teams can turn what they learn into meaningful action. We would love to hear how colleagues across outreach, marketing, events and admissions experience this in their own institutions.
Until then, something to think about: your next conversation with a prospective student might be their fifth interaction with your university. How much of the first four will you know about?