How to Build an Alumni Network at Your School

Start with a first cohort you can support

To build an alumni network, appoint an institutional owner, prepare a reachable graduate roster, invite a manageable first cohort and give members one useful activity. Creating the workspace and getting alumni to adopt it are separate jobs. A configured directory is not an active community: graduates still need to join, verify their membership and decide to participate, while your team welcomes people and keeps activities useful.

Use this kit for your first 100 verified members, or a smaller group you can support. This is a planning ceiling for the Free plan, not a promise to recruit 100 alumni by a fixed date. Staff and administrators count toward the capacity even without recent activity; imported records and pending invitations do not count. Check the current plans and limits before expanding.

Choose graduates with a reason to connect: a recent graduating class, an anniversary class or alumni interested in one professional topic. Mentoring here is between alumni, including recent graduates; it is not an activity for current students. Do not add people merely to fill the capacity.

A launch checklist with clear owners

Complete each step before moving on. Write an owner and review date next to it in your team's launch notes. Dates are your team's choices, not an automated Alumnia schedule.

1. Confirm authority and responsibility

Owner: institutional administrator. Confirm who is authorized to create and represent the institution, which graduate cohort is eligible and which contact source you are allowed to use. Assign a person to answer joining questions, review membership requests and handle community concerns. Assign a backup before sending invitations.

Record this decision:

Institution: [institution]. Eligible graduate cohort: [class years or program]. Institutional owner: [name]. Membership and support owner: [name]. First activity owner: [name]. Roster source and permitted use: [source]. Review date: [date].

Agree what members may post and how to contact the team. Do not give an alumni ambassador administrator access simply to help spread the invitation. Create the workspace, then check its member permissions and enabled features with the institutional owner.

2. Prepare a small, accurate roster

Owner: roster administrator. Use a CSV with one person per row. In Alumnia's importer, email is required. Start with that and the optional first_name, last_name and cohort_year fields; map and review the columns before importing. Check duplicates, missing emails and class years. Use a small sample to review the mapping before a larger import.

The supported optional fields are:

• Professional: current_role, current_company, industry, professional_status.
• Contact: linkedin_id, phone_number, contact_email.
• Education: institution_name, institution_country, degree_type, field_of_study, start_year, end_year.
• Invitation permissions: role can be member, admin or staff. Reserve elevated roles for authorized people; do not assign them to the whole cohort.
• Institution-specific fields: map the custom fields already configured in your institution, or skip columns you do not need.

You do not need to collect every optional field to launch. This ordinary CSV mapping does not include a city or street-address field; members can review location separately in their profiles. Do not put sensitive notes into a custom field merely because it is available. An imported institutional contact is not yet a joined, verified member. See how institutional records and the member directory differ.

3. Check the workspace before inviting alumni

Owner: institutional administrator, with the activity owner. Review the institution's name, joining and verification settings, contact/support instructions, directory visibility and which features are enabled. Test your own authorized account and the joining instructions without adding real people solely for a test. Confirm there is someone to review requests and respond when a person cannot join.

Members can enter profile information manually. LinkedIn-assisted information and later updates require the member's review and choice; signing in is not an automatic profile refresh. Optional enrichment of institutional contacts is a separate process and is not a promise that every member record stays current. Explain the directory and profile controls rather than requiring a LinkedIn account.

4. Send an invitation with one reason to join

Owner: outreach owner. Check the eligible recipient list, invitation destination, institutional identity and reply contact before sending. Replace every placeholder below. This is draft text for your team to adapt; reading this guide does not send an email or enroll anyone.

Subject: Join [institution]'s graduate community

Hello [first name], we are inviting graduates from [cohort/program] to [institution]'s alumni community. Our first activity is [specific activity and why it is useful].

Use your invitation or joining link: [joining link]. Follow the membership verification steps, review your profile and choose what you want to share. You can enter your information manually; LinkedIn is optional.

If the link does not work or your class year needs correcting, contact [support owner and contact]. We would be glad to see you there. [institutional sender]

Start with the group you can welcome and support. Review problems before expanding to another cohort. An invitation sent is not a verified member, and a verified member is not evidence of participation in an activity.

5. Welcome people into one useful activity

Owner: welcome and activity owners. Adapt this message for members who have joined. Verify the activity is available and someone is responsible for it before posting the welcome.

Welcome to [institution]'s alumni community, [first name]. Review your name, class year and the professional details you want to share, then find your classmates in the directory: [directory destination].

Our first activity is [activity]. You can take part by [one concrete action] at [activity destination]. [Activity owner] will answer questions at [contact]. Choose your notification preferences to suit you; participation is your choice.

Pick one first activity:

• Directory: ask members to review their class year and look for a familiar person. See the directory workflow.
• Mentoring: invite verified alumni to describe a specific professional question. Check mentoring is enabled and explain member choice and possible review or no match. Use the mentoring workflow and the request example in the existing guide.
• Jobs: ask willing alumni to share real openings with a working application contact and an owner who will maintain them. Company contacts depend on available profiles; an opening does not guarantee a referral or hire. See the jobs workflow.
• A reunion or conversation: choose a topic, host and date that the team can actually support. Confirm the location or meeting link before inviting people.

For more options, use the engagement ideas and measurement checklist. Your team still operates the activity; publishing a page or enabling a feature does not run a program by itself.

6. Review the first cohort before expanding

Owner: institutional owner, with outreach and activity owners. Set a review date after the first invitation wave and another after the activity. Separate records imported, invitations sent, people who joined and verified, and observed activity. Keep denominators and dates beside counts. A login does not establish a profile update; an application click does not establish a hire.

Record questions people asked, joining problems and what participants actually did. Use institutional reporting within your permissions and an activity owner's notes where needed; do not assume every proposed measure has a built-in dashboard. Do not share a member-level activity export with ambassadors just to produce a report.

Use this follow-up draft only for recipients and channels your team is authorized to contact:

Hello [first name], a short update from [institution]: [specific activity or useful item] is available at [destination]. If you want to take part, [one action]. If you had trouble joining or finding it, [support contact] can help. Our team will review the first cohort on [date] and would welcome your feedback.

If people have joined but the activity is quiet, ask whether the activity or instructions were useful before sending another broad reminder. Fix unanswered support requests, inaccurate contacts and expired job posts before inviting more people. Decide to repeat, change or pause the activity based on what you observed, without treating a small pilot as a guaranteed outcome for a larger network.

What is ready when this checklist is complete?

You have an accountable owner, an eligible roster, reviewed import mapping, a verified joining path, invitation and welcome drafts, one maintained activity and a review date. Community adoption still depends on member decisions and continued institutional work. Start the workspace free when those responsibilities are clear, and use the university and graduate-program overview if you need to align the plan with your institution. For graduates living across countries, the international-school overview can help frame responsibility for a network and activities across cities.