Member Transitions and Departure
Details
- Author: Fabian Pfortmüller, Nico Luchsinger, Sascha Mombartz (Community Canvas, 2017)
- Category: Frameworks
- Published: 2017
- Source: The Community Canvas
- Source URL: https://community-canvas.org/
- Access: public
Description
The practices through which community members navigate change: seasonal cycles, role shifts, planned departure, and invited exit. Documented from the ToGather archive.
Annotation
Member transitions cover everything that happens when a person's relationship with a community changes: seasonal cycles, role shifts, planned departures, and invited exits. Most communities struggle not with transitions in general but with one specific type they have designed least, typically role transitions or invited departures. This entry draws on interviews from Kibbutz Samar, Ananda Kalyani, and Feytopia to map the four modes and the practices that make each manageable.
Full text
**Every arrival implies a departure.** The practices a community uses to handle member transitions determine whether exits leave it stronger or fractured.
### 1. What it is
Member transitions are changes in the relationship between a person and a community. The Community Canvas identifies them as a distinct design theme, separate from membership selection and onboarding, because the failure modes are different. Communities that design careful entry processes frequently fail to design departure processes at all. The result is that exits, which are inevitable, arrive without language, without ritual, and without a shared frame for what has happened.
The Canvas framework identifies four types of transition that communities encounter at different stages of their life: seasonal cycles (where the community's rhythm creates natural points of entry and exit), role shifts (where a member's function or contribution changes substantially), planned departures (where a member leaves voluntarily, with time for preparation), and invited exits (where the community asks a member to leave, either temporarily or permanently). Communities usually have implicit practices for the first two and almost no design for the third and fourth.
<figure style="margin:28px auto;text-align:center;">
<svg viewBox="0 0 700 460" xmlns="http://www.w3.org/2000/svg" style="max-width:700px;width:100%;height:auto;display:block;margin:0 auto;background:#fcfaf5;" font-family="Georgia, serif" role="img">
<title>Four types of member transition, mapped by how communities design for them</title>
<desc>Seasonal cycles and role shifts usually have implicit practices; planned departures and invited exits usually have no design.</desc>
<text x="350" y="28" text-anchor="middle" font-size="11" font-family="Inter, system-ui, sans-serif" fill="#857e72" letter-spacing="3">FROM THE COMMUNITY CANVAS</text>
<text x="350" y="56" text-anchor="middle" font-size="16" font-style="italic" fill="#5b554c">Four kinds of departure. Two are usually held. Two are usually undesigned.</text>
<text x="40" y="100" font-size="11" font-weight="600" fill="#857e72" letter-spacing="1.5">USUALLY HELD IMPLICITLY</text>
<rect x="40" y="110" width="305" height="140" rx="8" fill="#f3ede1" stroke="#b59770" stroke-width="1"/>
<text x="60" y="138" font-size="11" font-weight="600" fill="#c97e4f" letter-spacing="1.2">SEASONAL CYCLES</text>
<text x="60" y="166" font-size="15" font-weight="700" fill="#5d4f3a">The rhythm of the year</text>
<text x="60" y="190" font-size="12" fill="#5b554c">Members come and go with the natural</text>
<text x="60" y="208" font-size="12" fill="#5b554c">cadence of a seasonal community.</text>
<text x="60" y="232" font-size="11" font-style="italic" fill="#857e72">Feytopia, four-to-five months a year.</text>
<rect x="355" y="110" width="305" height="140" rx="8" fill="#f3ede1" stroke="#b59770" stroke-width="1"/>
<text x="375" y="138" font-size="11" font-weight="600" fill="#c97e4f" letter-spacing="1.2">ROLE SHIFTS</text>
<text x="375" y="166" font-size="15" font-weight="700" fill="#5d4f3a">A member's function changes</text>
<text x="375" y="190" font-size="12" fill="#5b554c">A founder stepping back. A parent</text>
<text x="375" y="208" font-size="12" fill="#5b554c">reducing involvement. A new generation.</text>
<text x="375" y="232" font-size="11" font-style="italic" fill="#857e72">Tamera, across forty-eight years.</text>
<text x="40" y="290" font-size="11" font-weight="600" fill="#c97e4f" letter-spacing="1.5">USUALLY UNDESIGNED</text>
<rect x="40" y="300" width="305" height="140" rx="8" fill="#fcfaf5" stroke="#c97e4f" stroke-width="1.5" stroke-dasharray="6,4"/>
<text x="60" y="328" font-size="11" font-weight="600" fill="#c97e4f" letter-spacing="1.2">PLANNED DEPARTURES</text>
<text x="60" y="356" font-size="15" font-weight="700" fill="#5d4f3a">A member chooses to leave</text>
<text x="60" y="380" font-size="12" fill="#5b554c">Voluntary, with time to prepare. The</text>
<text x="60" y="398" font-size="12" fill="#5b554c">community decides how to mark it.</text>
<text x="60" y="422" font-size="11" font-style="italic" fill="#857e72">Most communities improvise this.</text>
<rect x="355" y="300" width="305" height="140" rx="8" fill="#fcfaf5" stroke="#c97e4f" stroke-width="1.5" stroke-dasharray="6,4"/>
<text x="375" y="328" font-size="11" font-weight="600" fill="#c97e4f" letter-spacing="1.2">INVITED EXITS</text>
<text x="375" y="356" font-size="15" font-weight="700" fill="#5d4f3a">The community asks someone to leave</text>
<text x="375" y="380" font-size="12" fill="#5b554c">Temporary suspension or permanent</text>
<text x="375" y="398" font-size="12" fill="#5b554c">removal. The hardest design decision.</text>
<text x="375" y="422" font-size="11" font-style="italic" fill="#857e72">Almost no community has designed this.</text>
</svg>
<figcaption style="text-align:center;font-style:italic;color:#857e72;font-size:13px;margin-top:10px;font-family:Georgia,serif;">Communities design carefully for entry and then find that exit, which is inevitable, arrives without language or ritual.</figcaption>
</figure>
*FROM THE FIELD: Three communities in the ToGather archive encounter transitions differently based on their structure. Feytopia at Château de Fey in Burgundy, France, has built its entire social logic around seasonal cycles: the community assembles each spring, disperses each autumn, and treats ending as a design feature rather than a loss. Kibbutz Samar in the Negev, Israel-Palestine, has almost no seasonal rhythm but a fifty-year accumulation of role shifts, planned departures, and returned members that Yaniv describes as orbital: nothing leaves the system, it just changes form and keeps circling. Ananda Kalyani in central northern Portugal runs continuous rotation of volunteers and contributors through a structured team system, with "invited to leave" as the explicit language for departures that the community initiates. Each structure produces different strengths and different costs.*
### 2. Where it came from
The Community Canvas (Pfortmüller, Luchsinger, and Mombartz, 2017) introduced member transitions as a named design theme in response to a gap in existing community-building literature. Most frameworks for intentional communities focused on arrival: recruitment, assessment, integration. Departure was treated as an edge case or a failure. The Canvas argued that this was backward. How a community handles the end of a membership relationship is as diagnostic of its health as how it handles the beginning.
The underlying observation is not new. Religious orders have managed novitiate entry and formal departure for centuries, often with elaborate ritual on both sides. Indigenous communities have transition ceremonies for role changes, seasonal movement, and death. The monastic tradition in particular developed sophisticated language for the person who leaves voluntarily (the one who discerns a different vocation) and the person who is asked to leave (exclaustration), avoiding the conflation of the two that secular communities often fall into.
Sociologically, the question of how groups handle exit was formalized by Albert O. Hirschman's 1970 framework distinguishing "exit" (leaving), "voice" (staying and advocating for change), and "loyalty" (staying and accepting). Intentional community research, including the work of Rosabeth Moss Kanter on commune survival and Richard Sennett on community and commitment, extended this to show that communities with no legitimate exit pathway tend to produce either forced loyalty or covert departure, both more damaging than designed exit would be.
### 3. How it actually runs
The four transition types require different design responses.
**Seasonal cycles.** A community organized around seasonal rhythms has a built-in transition structure. The arrival of a new season is a transition event. The end of a season is a departure event. Seasonal communities can use these points deliberately: end-of-season reflection practices, explicit acknowledgment of who contributed and how, documentation of what was learned, and a named close that allows the community to grieve the ending before anticipating the return. Communities that treat season-end as merely logistical, emptying the space and locking up, miss the ritual function that seasonal closure can serve.
**Role shifts.** Members change roles throughout their community tenure. Someone who coordinated the kitchen becomes a co-founder of a new project. Someone who led governance decisions moves into a maintenance role. Role transitions are often handled as bureaucratic handoffs, which misses the social and identity dimension: the person who held a role for years has built relationships, reputation, and self-understanding around that role. A role shift is a partial departure and a partial arrival, and it benefits from the same design attention as either.
**Planned departures.** The community member who leaves voluntarily, with time to prepare, is the transition type that communities most often neglect in favor of improvising warmly in the moment. Planned departure design includes the departure conversation (who has it, when, and what it covers), the handoff of responsibilities, the social acknowledgment within the community, and the continued relationship with former members. Communities that handle planned departures well tend to develop a culture of return: the person who left with honor comes back to visit, brings new perspectives, and sometimes rejoins. Communities that handle them badly tend to treat departure as betrayal, which makes the remaining members less likely to ever leave cleanly.
**Invited exits.** The hardest transition to design, and the one most likely to be improvised under pressure. An invited exit is when the community initiates the departure, either because the member has violated agreements or because the fit has genuinely broken down and repair is not possible. Invited exits require: clarity on who decides, a process for that decision that more than one person must complete, a conversation with the departing member that names what happened, and some account of whether and how return might be possible. Communities that design this in advance handle the moment more steadily than communities that discover they need it in real time.
### 4. What this practice is and what it is not
Transition design is sometimes confused with community membership rules, as if designing departures is the same as tightening entry requirements. The two practices operate on different problems. Entry design filters who joins. Transition design manages what happens when the relationship changes, for any of the four reasons described above. A community can have rigorous entry and terrible transition design. The two gaps are independent.
Transition design is also not a euphemism for making exit easy or normalizing departure as desirable. Designing departure practices does not signal indifference to whether members stay. It signals that the community takes the full arc of membership seriously enough to acknowledge that it ends, and that the ending matters.
Transition pairs with the membership and selection practices documented in the companion entry [Membership and Selection](/library/community-membership-selection). The invited exit is the departure-side mirror of the membership criteria: the community's theory of who belongs always implies a theory of what happens when someone stops belonging. Communities that have thought carefully about selection will find the invited exit conversation easier, because they already have the language for fit and for the failure of fit.
### 5. Communities
**Feytopia, Château de Fey, Burgundy, France.** Feytopia is the clearest example in the ToGather archive of seasonal cycle as deliberate design. The community assembles each spring and disperses each autumn. No one lives at the Château de Fey year-round except the owner, Jess. This is not a structural accident. Shelby McAuliffe, who has run admissions for two seasons, named it as one of the three things that would dissolve the community if removed.
"The third thing, that I think is quintessential, is that it ends," Shelby said. "That's why festivals are what they are. That's why so many things about this community hold such a rich and potent part... one of the main elements that keeps this community what it is, and not fall apart, and is around for seven seasons, is that it is seasonal. It has its temporal, has a beginning. It ends."
The ending is where Feytopia holds its richest social function. Because people know they will leave, the intensity of encounter is calibrated differently than in permanent communities. The departure is anticipated from the moment of arrival. This produces a particular kind of presence: less hedged, more willing to go deep quickly, less concerned with managing a long-term reputation that has to survive daily contact for years.
Feytopia's departure practice for the invited exit is less formally designed. Non-return requests happened when consent was breached and the person was not receptive to repair. "People that didn't really show remorse, or felt that they had done anything wrong, and weren't really receptive to collaboratively resolving the issue," Shelby said. "In that case, we've requested they don't return." The decision required multiple people to agree. It was not reversed once made. The community treated it as a correction to the selection process, not as punishment.
*FROM THE FIELD: Yaniv has lived in Kibbutz Samar in the Negev, Israel-Palestine, for more than 30 years. His account of what long-term community membership does to departure is the most direct description of the orbital logic that permanent communities develop over time. "You know, a spouse you can divorce and start over. But here there is none of that. It's like in space, no matter what comes out of you, it starts to orbit. You orbit around other people. It's endless, this shit." He has multiple former partners living on the same kibbutz. He knows their stories and they know his. He documents the place. He cannot leave the archive of his own life here behind, because the archive lives among the people, and the people are still there. "We are in a very remote area... Everyone who comes here didn't come because of a mistake at the traffic light. We are all refugees of something. We were running away from something."*
**Kibbutz Samar, the Negev, Israel-Palestine.** Samar does not have seasonal cycles or formal departure rituals. What it has is fifty years of accumulated transition history, documented in part by Yaniv and carried in the memory of the community at large. Departures from Samar are permanent in one sense (people leave the physical location) and not permanent in another (the relationships do not end; they change state and continue orbiting).
The cultural artifact that captures this most clearly is the junkyard. Samar's junkyard became a reclamation space over decades: old vehicles, scrap metal, furniture, all the material that a community produces when it cannot easily dispose of things because it is remote and because disposal feels wrong. Yaniv built a sorting system into the junkyard. He named the logic explicitly: "And here, on the kibbutz, even in relationships, you have to recycle. Because you live here together. You can't say goodbye to anything."
The junkyard is a metaphor Samar did not intend and lives with anyway. When you cannot easily leave and cannot easily throw things away, you learn to transform them. Former partners become neighbors. Former colleagues become members of the same economic crisis. Former adversaries in the founding factions become, as Yaniv's generation grew up and the factions dissolved, simply people who have known each other for thirty years.
Samar arrived at this without designing it. The transitions happen through time and proximity, through the slow work of people who chose to stay.
**Ananda Kalyani, central northern Portugal.** Ananda Kalyani has a higher rate of turnover than either Feytopia or Samar. "There is a lot of movement, a lot of rotation in people, people come and go all the time, different people," Anandeshvarii said. The community runs continuous cycles of volunteers and contributors arriving through the Human Flow team, staying for varying durations, and leaving when their contribution cycle ends or when they choose a different path.
This continuous movement could be destabilizing. What makes it manageable is the structured role allocation: everyone arriving knows their team assignment before they arrive, and the team structure persists across individual turnover. The community's continuity is not located in individuals staying; it is located in the Ananda Marga philosophical tradition and the team system that carries it. People rotate through; the structure holds.
The invited departure at Ananda Kalyani is explicit and named. Anandeshvarii described it without hesitation: someone who was not adding to the collective, more weight than contribution, was invited to leave. The person objected. Said they would call the police. Left the next day without further intervention. "Things get to dissolve," Anandeshvarii observed. The clarity of the invitation, and the shared understanding that the invitation was legitimate, was enough for the dissolution to happen.
Anandeshvarii also described the personal cost of the rotation culture: "The loneliness. And that comes from a frustrated expectation, from the desire of having a lifelong partner and not being able to find that. So counting on that to fill the loneliness in such a setup where there are a lot of young people." When the people coming and going are mostly younger, and when you have been there long enough to see multiple full cohorts rotate through, the movement that sustains the community's work creates a particular kind of grief. This is the underside of designed transition in high-rotation communities: the people who stay accumulate loss alongside continuity.
### 6. Steps to begin
**Name which transition type is hardest for your community right now.** Most communities have a different answer. Some struggle with role transitions, where long-tenured members resist change. Some struggle with planned departures, which are handled as quiet exits with no shared acknowledgment. Some have never had to initiate a departure and do not know what that conversation would look like. Start with the type you have least capacity for, not the type that is most comfortable to think about.
**Design an end-of-season practice, even if your community is not seasonal.** Annual or quarterly closing practices serve the same function as seasonal departure: they create a named moment for acknowledging what happened, who contributed, and what is changing. A closing circle, a written reflection document, a shared meal with explicit gratitude and grief: any of these can hold the transition in a way that ongoing daily life cannot.
**Create a handoff protocol for role transitions.** Write down what the role requires, who depends on it, what the outgoing person has learned that is not in any document, and who will hold the knowledge after they leave the role. A 30-minute recorded conversation between the outgoing and incoming person is worth more than a written handoff document in most community settings, because the knowledge that matters most is usually not written anywhere.
**Hold a departure conversation before a departure happens.** For planned departures, the community's default is often a combination of informal warmth (a farewell meal, kind words) and official indifference (no formal acknowledgment, no handoff structure). The departure conversation is different from a farewell: it addresses what the person contributed, what they are leaving behind, what they are taking with them, and what kind of relationship with the community they want after they leave. Many communities find this conversation awkward to initiate. Starting to hold it routinely, even imperfectly, builds the muscle before it is needed under pressure.
**Document the invited exit process before you need it.** Three questions to answer in advance: who decides, how many people must agree, and what happens after the person has been asked to leave. A community that has answered these three questions before the situation arises will handle the conversation more steadily than one that discovers it has no process while managing the confrontation in real time.
**Maintain the relationship with former members.** Alumni relationships are a resource few communities develop deliberately. Former members carry the community's history, can provide outside perspective, and are often the most effective advocates with potential new members or partners. A once-a-year newsletter, an open invitation to seasonal events, or a simple message acknowledging the anniversary of someone's departure costs almost nothing and produces disproportionate goodwill.
### 7. Living examples and entry points for community builders
The Community Canvas worksheet on member transitions is available at [community-canvas.org](https://community-canvas.org). It walks through the four transition types with reflection prompts for each. The most useful prompts are in the section on invited exits, which asks communities to name the conditions under which they would ask a member to leave, before the situation arises.
Starhawk's community facilitation materials, compiled in *The Earth Path* and in the Reclaiming tradition's facilitation handbooks, include closing ritual structures designed for both seasonal and membership transitions. These are particularly useful for communities that want transition design with spiritual dimension rather than purely procedural structure.
The work of Arnold van Gennep and Victor Turner on rites of passage (van Gennep's *The Rites of Passage*, 1909; Turner's *The Ritual Process*, 1969) provides the theoretical foundation for understanding why transitions need ritual at all. The argument is that liminal states, states of being neither fully in nor fully out, are inherently unstable unless bounded by ritual. Communities that skip transition ritual produce members who remain liminal, caught between roles or between inside and outside, without a clear moment of passage.
The Transition Towns network has developed community-facing materials on managing the departure of founding members from social movements, which addresses a transition type not covered by intentional community literature: what happens when the people who started something step back. Documentation is at [transitionnetwork.org](https://transitionnetwork.org).
For the selection side of the same arc, the companion entry [Membership and Selection](/library/community-membership-selection) covers the criteria, assessment, trial, and integration stages that precede transitions.
For the purpose-setting context that gives transitions their meaning, the companion entry [Community Purpose-Setting](/library/community-purpose-setting) addresses what it means when a community's founding purpose no longer fits, which is one of the most common triggers for both planned and invited departures.
### 8. Where it gets hard
**Departure is often experienced as betrayal.** In communities with strong belonging cultures, leaving is read by remaining members as a rejection of the community itself, regardless of the leaver's reasons. This interpretation makes departures harder to talk about openly, which means they tend to happen with less preparation and more damage than they need to. A community that can distinguish between "this person is leaving" and "this person is rejecting us" has to practice that distinction before it comes up, because the emotional pull toward the second reading is strong.
**Role transitions in long-tenured communities are rarely clean.** The person who has held a role for ten years is not only the person who does the tasks of that role. They are the person others come to for institutional memory, for informal advice, for the particular kind of trust that comes from time. When they shift roles, those functions migrate unpredictably, and the new person in the role finds that they have inherited the title but not the informal authority. Communities that handle this well invest deliberately in the transfer of informal authority, which cannot be mandated but can be modeled.
**Invited exits produce contested narratives.** The person who was asked to leave will tell a different story than the community that asked them to leave. Both stories will spread. Communities that have not agreed in advance on how to communicate about an invited exit find themselves managing two competing accounts in real time, often with people choosing sides. A simple, factually accurate statement, agreed upon before any communication happens, is worth almost any amount of preparation time.
**The rotating community produces cumulative loss.** Feytopia's seasonal structure works because the temporality is explicit: everyone knows it ends. In communities with high rotation that are not explicitly seasonal, the departure of members produces a different kind of grief, because the loss is not built into the frame. The people who stay across multiple waves of rotation accumulate losses that have no designated container. Anandeshvarii named this plainly: the loneliness of watching people arrive and leave when you remain. Communities with high rotation and low seasonal structure need explicit grief practices for the people who stay.
**The orbital logic of permanent communities has no designed exit.** Samar's situation, where everyone who arrived is still in some sense in relationship with everyone else, is honest about what long-term community membership actually means. There is no clean departure from a community where you have lived for thirty years. The relationships become part of the landscape. Former partners, former adversaries, former collaborators on failed projects: all of them remain in orbit. The accumulation is the consequence of genuine commitment over time. What communities in this situation need are practices for living with it, not for dissolving it.
### 9. More resources
**Primary source**
Pfortmüller, Fabian, Nico Luchsinger, and Sascha Mombartz. *Community Canvas Guidebook.* Together Institute, 2017. Available free at [community-canvas.org](https://community-canvas.org). The Transitions and Rituals themes are in the Experience section.
**Archive interviews referenced**
Anandeshvarii, Ananda Kalyani, central northern Portugal (continuous rotation culture, structured team allocation, invited departure, cumulative loneliness in high-rotation settings).
Shelby McAuliffe, Feytopia, Château de Fey, Burgundy, France (seasonal ending as design feature, the temporality of festival community, non-return process after consent breach).
Yaniv, Kibbutz Samar, Negev, Israel-Palestine (orbital relationship logic, junkyard as recycling metaphor, departure as state change rather than ending, long-term consequences of a no-exit community).
**Companion Library entries**
[Membership and Selection](/library/community-membership-selection): The selection practices that precede transitions. The invited exit is the departure-side complement of the invitation-to-join.
[Community Purpose-Setting](/library/community-purpose-setting): Purpose erosion is one of the most common triggers for planned departure waves. When the founding purpose no longer holds, members who joined for that purpose tend to leave at the same time.
**Extended reading**
van Gennep, Arnold. *The Rites of Passage.* 1909. University of Chicago Press edition, 1960. The foundational account of why liminal states require ritual to close.
Turner, Victor. *The Ritual Process: Structure and Anti-Structure.* Aldine, 1969. Extends van Gennep to communities: liminality is generative when bounded and damaging when unbounded.
Hirschman, Albert O. *Exit, Voice, and Loyalty.* Harvard University Press, 1970. The political-economic framework for understanding when people leave, when they stay and advocate, and when they stay and accept.
Kanter, Rosabeth Moss. *Commitment and Community: Communes and Utopias in Sociological Perspective.* Harvard University Press, 1972. On the practices that produce long-term commitment, and what happens to communities that lack them.
Starhawk. *The Earth Path.* HarperOne, 2004. Closing ritual structures and community grief practices drawn from the Reclaiming tradition.