Employee Alumni Network Programme Template
Two documents and three sheets that record rehire eligibility the day someone leaves, then check it against who actually comes back.
Free download · No account needed
This pack builds an Alumni Register that records rehire eligibility at the moment someone leaves, using the exit interview and the manager's input while both are still fresh. Every departure gets one of three flags: Eligible, Eligible with conditions, or Not eligible, each with a one-line note. A Referral and Rehire Tracker then cross-references that register against who has actually reapplied and who has referred a hire, so the flags get tested against reality.
A generic alumni programme guide cannot do this, because it has no access to your departure records. In the worked example, a fictional instruments manufacturer's register covered 52 departures over two years: 37 eligible, 9 eligible with conditions, 6 not eligible. Only 8 of the 52, 15.4 percent, reapplied in that window. Cross-referencing found something worth knowing: 6 of those 8 were flagged eligible at departure, exactly as expected, but one was flagged not eligible and applied anyway, the case a register catches and a folder of old emails does not.
Written for people ops teams past the point where a leaver's rehire status lives in one manager's memory, and complementary to the 30-60-90 onboarding pack that ramps whoever actually returns. SHRM's analysis of applicant-tracking data found referrals delivered more than 30 percent of all hires, which is why the tracker here treats an alumnus who only refers, and never returns, as a full success. A departing employee's other obligations belong on a knowledge transfer plan instead, and a manager inheriting this alumnus's old team should start a new manager plan.
What is in the pack
Alumni Register
One row per departure with tenure, reason for leaving, and a rehire eligibility flag set at the time, with a note that keeps it checkable years later.
Contact Log
Personal contact information collected at exit, since a work email stops working on the last day and a former employee otherwise disappears by design.
Referral and Rehire Tracker
Every reapplication and every alumni-sourced referral in one place, cross-referenced against the original eligibility flag.
Alumni Programme
Who gets contacted, how contact information stays current, and how the same referral path current employees get is offered to alumni.
Outreach Cadence
A contact schedule by segment that treats an eligible alumnus in an open role differently from one whose skills or the company's needs have moved on.
How it works
- 1
Send departure records
Name, role, department, last day, tenure, manager, and reason for leaving for the last one to two years, plus exit interview notes if you have them.
- 2
Get the eligibility flags
Every departure scored Eligible, Eligible with conditions, or Not eligible, with a one-line note pulled from the actual exit record rather than tenure alone.
- 3
Cross-check against reality
Reapplications and alumni referrals checked against the original flags, so you see whether eligible people actually come back and ineligible ones do not.
- 4
Run the outreach
The Outreach Cadence and Alumni Programme docs draft a realistic contact schedule from what the register and cross-check actually support.
Frequently asked questions
Why record eligibility at departure instead of when someone reapplies?
Because the person best positioned to judge it, the departing manager, is available at departure and often is not two years later. In the worked example, one of eight reapplicants had been flagged Not eligible; that flag was only trustworthy because it was set at the time, not reconstructed.
What if we do not have exit interview notes for past departures?
Start the register from the last day and reason for leaving alone, flag eligibility as best as current knowledge allows, and note that the flag is a reconstruction rather than a contemporaneous record. Going forward, capture the flag at every new departure so the register stops being a backlog problem.
Should a Not eligible alumnus be removed from the register?
No. Keep the row so the flag is not lost if the same question comes up again, but exclude that person from all outreach and referral crediting. The register's job is to remember the decision that was made, not just the outcomes that look good in hindsight.
Does this replace a formal boomerang hiring policy?
No, it feeds one. The register gives whoever writes that policy real eligibility data and real reapplication behavior to design the policy around, instead of a policy written from anecdote and gut feel before anyone had actually counted a single departure or reapplication.
What about alumni who refer people but never come back themselves?
They count as a full success in this pack's tracker. In the worked example, 22.5 percent of the last 40 external hires were alumni-referred, a larger channel by volume than direct rehires, so the programme is built to value both paths rather than treating referral as an afterthought to rehiring.
Who should own the outreach once the register exists?
Whoever owns recruiting sourcing, since alumni outreach is a sourcing channel with its own register rather than a separate relationship-management program. People ops owns the eligibility flag itself, since that judgment belongs with whoever ran the departure.
Find out which of your departures are actually welcome back
Send your departure records and exit interview notes. The first thing back is the eligibility flag for each one, checked against who has actually reapplied or referred a hire.
Build my alumni register