Most alumni databases keep their graduates tagged as "student" for years after graduation because the transition is manual. The result: biased CGE surveys, impossible mentorship, badly targeted communications. Three complementary mechanisms (D+1 email, profile banner, D+30 safety net) let you automate the switch with no admin intervention.
The silent problem: the alumni database that lies
On most alumni platforms, the "student" / "alumni" status is a static field. At sign-up, the member is a student. At graduation... they stay a student. Why? Because nobody explicitly triggered the switch.
Concretely, here's what happens in a school that uses Excel or a classic platform like AlumnForce / Hivebrite:
- In July, the class of 2026 receives its diploma.
- At some point, the admin has to run a CSV export, edit the status column, and re-import.
- This task is rarely prioritized — it has no visible urgency, no attached KPI, no technical error if forgotten.
- Result: twelve months later, the class of 2026 is still labeled "student" in the database.
This problem is invisible. The platform works. The emails go out. The profiles are viewable. Except the data is wrong, and everything built on top of it ends up biased.
Why it's a real problem (beyond the database looking tidy)
A database with ghost students causes three cascading failures.
Biased CGE/CTI surveys
When the CGE 6-month placement survey comes around, you segment on member_type = alumni. Graduates labeled "student" never receive the survey. You measure the placement of a partial panel — and you report mechanically truncated figures to the CGE. For schools in an accreditation visit, the gap between the real class and the responding class becomes a thorn in the side of the file.
Mentorship that can't be activated
A past graduate still marked as "student" can't become a mentor — the role is usually gated by alumni status. An entire class is thereby excluded from your school's mentorship program, even though it represents exactly the profile current students want to reach out to (young graduates, still close to school life).
Badly targeted communications
Newsletters for "honored alumni", the "graduates' club", and "membership dues calls" exclude mislabeled graduates by design. And conversely, "internship", "back-to-school" and "enrollment" announcements reach them at 30 years old. The effect: the school's communication loses credibility with an entire generation.
Why classic tools don't do it
The alumni platforms on the market treat status as an admin field, not as an automatic mechanism. Three reasons:
- AlumnForce, Hivebrite, Graduway: the transition is exposed in the admin interface (export → edit → re-import OR bulk update). It's technically doable, but none of these tools triggers the switch without human intervention.
- Excel, Google Sheets: the mechanism simply doesn't exist. The spreadsheet is inert.
- LinkedIn Groups, WhatsApp, community Slack: there's no notion of formal status. Everyone is a "member".
The common bug: these tools treat the alumni network as a list, not a flow. Yet an alumni network is a flow: every year, a class shifts from inside to outside, and the platform should handle it on its own.
The Terrilink mechanism: 3 converging sources
Terrilink triggers the switch through three complementary mechanisms, each covering a case the others miss.
Source 1 — D+1 email (active engagement)
The day after the computed graduation date (end_year × the school's default graduation month), an automatic email is sent to the student with a signed JWT link valid for 60 days. One click = instant alumni switch + a warm welcome email.
Source 2 — Profile banner (case of the already-logged-in member)
If the student logs in on their own after their graduation date (before or after the email), a banner on their profile offers the 1-click switch. This covers the case where the D+1 email lands in spam or is ignored.
Source 3 — D+30 safety net (completeness guarantee)
If the student has neither clicked the email nor reacted to the banner within 30 days, the system automatically moves them to alumni. The transition is traced in the database (graduation_status = auto_transitioned) to distinguish switches performed by the user (sources 1 and 2) from those performed by the safety net.
The three sources converge on the same final state: member_type = alumni. The cron runs every day at 8am Europe/Paris.
Comparison: manual vs automatic
| Criterion | AlumnForce / Hivebrite | Excel / Google Sheets | Terrilink |
|---|---|---|---|
| Automatic transition | ❌ Manual (admin) | ❌ Nonexistent | ✅ Automatic |
| Alumni welcome email | ⚠️ To configure | ❌ No | ✅ Included |
| Safety net (D+30) | ❌ No | ❌ No | ✅ Included |
| Annual admin workload | 1-2 days / year | 1-2 days / year | 0 minutes |
| Risk of being forgotten | High | Very high | None |
Comparison based on public documentation available as of May 4, 2026 (vendor websites, product sheets, recorded demos). If you spot an equivalent feature at a competitor mentioned here, write to us at thibault@terrilink.io: we'll update the article.
The benefits nobody measures
Beyond a clean database, the automatic lifecycle unlocks second-order effects that are rarely documented.
A warm welcome email. The graduate receives a message celebrating their change of status. The profile completion rate (company + role) is mechanically higher in the days that follow — which then feeds mentorship matching and the accuracy of CGE surveys.
Always-up-to-date data for surveys. When the time comes to launch the CGE 6-month survey, your segmentation on alumni is exhaustive and reliable. See our full schedule for the 2026 CGE survey to line up the mechanism with the reminder windows.
Immediate mentorship activation. A graduate can, from the moment of the switch, be identified as a potential mentor. Programs that rely on young graduates (3-5 years out) gain in responsiveness.
Institutional credibility. For a B2B buyer (school GM, careers-and-placement lead), a platform that does this on its own signals a level of product maturity. It's exactly the kind of detail that sets a modern tool apart from a legacy one in a demo.
Frequently asked questions
What happens if the expected graduation date doesn't match reality (make-up board, repeated year)?
The graduation date is editable at the member level. The admin can update it at any time; the D+1 / D+30 cron takes the current value into account.
Does the system send emails to schools in demo mode?
No. The cron filters on Stripe live mode: no real email is sent to tenants in test or demo mode.
What happens if the welcome email fails to send (SMTP down, invalid address)?
The welcome email is non-blocking. If sending fails, the student → alumni transition is preserved in the database and the error is logged on the admin side. No automatic retry today: the member keeps their new alumni status but does not receive the welcome email until the incident is resolved.
See the mechanism on your own database
The automatic lifecycle is one of Terrilink's most demonstrable features: we import one of your school's classes, configure the graduation date, and you watch the D+1 email go out live. Book 15 minutes and we'll run through the full sequence on your case. To compare Terrilink with the other options on the market, see also the alternative to AlumnForce or our guide on how to choose your alumni software.