A 12-month alumni rhythm that keeps founders connected

Alumni engagement works better as a light rhythm than a stream of announcements. This 12-month plan gives operators a repeatable cadence of useful prompts, peer exchange, updates, referrals and feedback, with enough flexibility for founders to opt in and contribute on their own terms.

### Use this when Use this after a cohort finishes, when alumni participation has become event-led and irregular, or when founders receive many updates but few useful connections. The rhythm is not a promise of constant activity. It is a way to make the next useful interaction predictable while respecting changing founder priorities. CMX’s published moderator-program example combines day-to-day conversation, weekly welcomes, monthly team meetings, quarterly event support, tracking, feedback and recognition. [1] Adapt the principle—not the exact cadence—to an alumni context: assign ownership, create repeatable rituals, listen to participants and adjust. ### The outcome Alumni know how to ask for help, offer help, find relevant peers and re-enter the programme’s network. Operators have a calendar, owners, a lightweight record of needs and offers, and a quarterly review. The community remains useful even when not everyone attends every activity. ### Before you start **Inputs:** alumni consent and contact preferences, cohort themes, current needs, programme calendar, communication channels, moderation rules and a list of recurring questions. Decide what is public, members-only or private. **People:** one community owner, rotating alumni contributors, an event or content owner, and a clear route for sensitive or safeguarding issues. Ask alumni what cadence is realistic before fixing it. **Time:** set the annual skeleton in one planning session, then run a monthly operating block and quarterly review. Keep rituals small enough to survive busy periods. ### Step by step 1. **Write the alumni promise.** State what alumni can reasonably expect: a place to ask, a way to offer, selected introductions, learning resources, or periodic peer sessions. Do not promise funding, customers or access you cannot control. 2. **Segment by useful context.** Use cohort, sector, stage, geography or current need only where it changes the invitation. Avoid over-segmentation that makes the community feel like a database. Let members choose how they are described. 3. **Build the year around four rituals.** Use a monthly prompt or office hour, a quarterly peer exchange, a six-month update, and an annual reflection or reunion. Add ad hoc support only when it serves a clear need. 4. **Create a monthly prompt that invites substance.** Ask for one challenge, one lesson or one offer. Moderate replies so the thread does not become a list of links. Summarise useful patterns and unresolved questions. 5. **Run quarterly peer exchanges.** Give each session a topic, a host, a short preparation question and a follow-up action. Rotate the time or format where the community spans regions. Record learning only with consent. 6. **Make help discoverable.** Keep a simple needs-and-offers register with owner, date and status. Remove stale items. Route sensitive requests privately and do not publish personal details by default. 7. **Invite alumni contribution without creating unpaid obligation.** Offer clear roles: host a 20-minute clinic, review a resource, welcome a new founder, or share a market lesson. State expected time and give recognition where appropriate. 8. **Use a re-entry path.** A founder who has been quiet should be able to return without explaining their absence. Send a short “what is useful now?” check-in and offer a current summary, not a guilt message. 9. **Review each quarter.** Look at useful signals: unanswered questions, repeated needs, participation across geographies, referrals completed, resource use and member feedback. Change a ritual that creates work without value. 10. **Close the year with learning.** Ask what alumni want to keep, stop and start. Publish a short internal note on changes for the next year. Thank contributors without making claims about outcomes you have not measured. ### Templates **12-month rhythm** | Month | Ritual | Prompt / purpose | Owner | |---:|---|---|---| | 1 | Re-entry check-in | What is useful now? | Community owner | | 2 | Needs and offers | What can you help with or need? | Rotating host | | 3 | Peer exchange | One practical market or sector question | Alumni host | | 4 | Resource clinic | Review a shared tool or guide | Content owner | | 5 | Founder question | One decision you are working through | Community owner | | 6 | Mid-year reflection | Keep, stop, start | Community owner | | 7 | Peer exchange | Cross-border learning | Alumni host | | 8 | Welcome and re-entry | Invite quiet members back | Moderator | | 9 | Needs and offers | Refresh open requests | Community owner | | 10 | Office hour | Specialist topic, clear boundaries | Guest host | | 11 | Peer exchange | Lessons from a recent experiment | Alumni host | | 12 | Annual reflection | What should the network do next year? | Programme lead | **Monthly prompt:** “What is one decision you are making this month where an alumni perspective would help? Reply with context, the kind of input you want, and whether a private follow-up is welcome.” ### Common mistakes Do not measure community health only by attendance. Do not make every update a programme announcement. Do not ask the same visible alumni to carry the network. Do not expose founder needs without permission. Do not keep stale offers open. Do not confuse a broadcast list with a community. Do not punish silence. ### How to tell it worked Alumni can find the next ritual and know how to contribute. Needs and offers receive a response or are closed with an explanation. Participation is not concentrated in one small group. Quiet members can re-enter. The quarterly review changes the rhythm based on evidence and feedback. ### Using LINKK for this Use LINKK’s Network feed for regular Insight, Question, Event and Resource posts, choosing Public or Members visibility deliberately. Alumni can post Needs and Offers by category, follow relevant organisations, and use accepted introduction requests when a private conversation is appropriate. The Operator playbooks library can hold the repeatable routines that new community owners need. ### Sources [1]: https://www.cmxhub.com/blog/how-to-build-a-moderator-program "CMX: How CMX Built Our First Moderator Programme" ---