

.png)
The short answer. To keep alumni engaged, stop treating graduation as an exit and start treating it as a handover. Carry the record built up over years of study into the alumni relationship rather than starting over with a mailing list. Read what a graduate actually visits and returns to on the website after they leave, and respond with the specific thing that behaviour points to: further study, a mentoring role, an employer connection, a reunion, a gift. Alumni disengage not because they stopped caring, but because the institution stopped recognising them.
A graduate who spent four years being known, timetables, well-being check-ins, a personal tutor who remembered their name, leaves the ceremony and becomes a row in a spreadsheet by the following term. The alumni office sends the same annual appeal to a first-year dropout and a graduate who has since become a senior partner at a firm the university would love to place students with. Neither message reflects what either person actually did after they left. The relationship the institution spent years building does not end at graduation. It just stops being read.
Because the systems that knew the student stop talking to the ones that are supposed to know the graduate. The record built across enrolment, coursework, and student support usually lives in a student information system that alumni relations cannot see. What replaces it is often a fresh database, populated from a graduation list, with none of the history attached. The graduate who was a keen mentee, who struggled financially in second year and was helped through it, or who published research that made the department proud, shows up in the new system as a name and a degree. Alumni relations start from zero on a relationship the institution spent years building.
Even alumni who valued their time at the institution describe the reconnection experience as fragmented: a generic newsletter, an unrelated donation ask, an invitation to an event for the wrong faculty. Each message tells the graduate the institution has not registered who they are or what they have done since leaving, and that is a familiar feeling. It is the same failure that shows up earlier in the relationship, at the enquiry stage, when a prospective student compares three programmes on her phone and still gets a generic prospectus that reflects none of them. The institution has the information to send something relevant. It just is not reading it.
A coherent alumni relationship rests on three moves:
Suppress the rest. A generic annual appeal sent to someone already reading mentoring pages buries the message that would have actually worked.
Treat graduation and beyond as a set of specific pathways, not one undifferentiated audience called "alumni":
None of these pathways require guessing. They require reading the record that already exists and letting it lead.
Alumni sit at the start of the next enrolment cycle and the end of the last one, not outside either. A well-timed conversation with a satisfied graduate produces a referral, a mentor for a current student, an employer connection, a donor, or a further-study enrolment, each of which is worth more than the cost of reaching them well. A poorly-timed one, the wrong ask at the wrong moment, is not neutral. It reads as the institution not knowing its own graduate, and that undermines the very relationship the alumni office exists to protect.
The lifetime relationship, from prospective student through graduate, is the actual unit of value here, not any single stage of it read in isolation. An institution that treats graduation as an ending gives up everything that relationship could still become.
Do you need a separate alumni database to do this well? No, and running one is usually the problem rather than the fix. A separate system means starting the alumni relationship from a graduation list with no history attached. Carrying the existing student record forward, rather than replacing it with a fresh one, is what makes the relationship feel continuous instead of restarted.
How soon after graduation should an institution reach out? Before the relationship goes quiet, not on a fixed date months later. A graduate still checking department news or event pages in the weeks after leaving is telling you the relationship is still live. Waiting for the next scheduled alumni campaign to respond to that is the gap where the feeling of being known is lost.
What is different about alumni compared to current students? The stakes shift, but the underlying discipline does not. A current student's signals point mostly toward support and retention. A graduate's signals point toward a pathway, further study, mentoring, employer connections, giving, advocacy, that only becomes visible once you are reading what they actually do rather than assuming which category they fall into based on graduation year.
Does reading alumni engagement this way raise data protection questions? Yes, and it is worth answering before the programme runs, not after. Using a graduate's website behaviour to decide who gets a mentoring invitation is a different processing activity from using it to decide who gets a fundraising ask, and a UK institution needs a clear lawful basis for each, typically legitimate interests for the former, consent for direct marketing and fundraising communications under PECR and the Fundraising Regulator's code for the latter. Which basis applies, and how it is recorded, is a determination for the institution's data protection officer, not something this kind of system decides on the institution's behalf.
This is not about adding systems. It is about carrying the record an institution already holds through to the relationship it is meant to serve for life. That is the idea behind LoupeED, and the wider pressure that makes it urgent is the subject of our session on higher education under pressure.
This completes the series. Start at the beginning: Part 1: how to get prospective students to engage with your website. Or read Part 2: how to keep current students engaged and spot the ones slipping away.
This article was origionally posted on our LinkedIn Here
Has this triggered any questions, and want to keep the conversation flowing? We'd love to talk.


