Trust Doesn't Transfer Itself: A Protocol for Program-Level Succession

When a program director retires, boards convene search committees. When a program coordinator retires, organizations often post the job, interview for a week, and move on. The assumption is that coordinator-level roles are interchangeable — that anyone with the right résumé can pick up where the last person left off.

The communities ICC2 serves know better. In neighborhood-based work, the person who has attended the same church potlucks, sat on the same school advisory councils, and returned the same phone calls for fifteen years is not easily replaced by a qualified hire. Their departure, handled poorly, can set a program back years — not because of any skills gap, but because trust was never written down.

The Invisible Balance Sheet

Every long-tenured program manager carries two portfolios. The first is documented: budgets, curricula, grant reports, attendance logs. The second lives entirely in their head and their contacts list — which vendor actually shows up on time, which family needs a direct call rather than a mass email, which partner organization has an internal politics landmine nobody has mapped.

This second portfolio is the one that evaporates. And unlike a grant shortfall or a staffing gap, its loss is rarely visible until something breaks: a partner stops returning calls, a recurring event loses its venue, a funder mentions that the new coordinator seemed unfamiliar with the program's history.

Succession planning at the program level, then, is not a courtesy. It is risk management.

Building the Institutional Knowledge Inventory

The foundation of any credible handoff is a structured inventory of what the departing coordinator actually knows. This is not a two-hour exit interview the week before their last day. Done properly, it is a six-to-eight-week process that begins well before a departure is announced.

A practical inventory covers four domains:

• Operational knowledge: recurring obligations, seasonal rhythms, vendor arrangements, and the small workarounds that keep programs running — the permit that renews in March, the storage unit with the finicky lock.
• Relational knowledge: every external contact, organized by relationship depth, history, and sensitivity. A spreadsheet of names is not a relationship map; the map should record how the relationship was built and what it depends on.
• Historical knowledge: why past decisions were made, which approaches failed and why, and which community members hold influence that never appears on any org chart.
• Commitment knowledge: verbal promises made, informal understandings with partners, and obligations that exist outside any contract.

The last category is the one organizations most often overlook — and the one most likely to cause embarrassment when a new coordinator unknowingly contradicts a commitment they never knew existed.

The Relationship Map: More Than a Contact List

Institutions rarely lose contacts; they lose standing. A relationship map documents not just who the coordinator knows, but the nature of each connection: how it was formed, what it has weathered, and what it will take to maintain it under new stewardship.

For US-based community programs, this is especially critical with institutional partners — school districts, county health departments, housing authorities — where relationships are often personal even when the partnership is formal. A memo of understanding survives a coordinator's departure. The phone call that gets a returned email within an hour does not.

The map should identify which relationships require a warm, facilitated introduction — the departing coordinator present, the successor learning the rhythm of the conversation — and which can be transitioned through a simple written notice.

Shadowing: The Overlooked Middle Phase

Documentation alone cannot transfer trust. The most effective handoffs we have observed include a structured shadowing period of four to eight weeks, during which the successor observes the outgoing coordinator in live settings: partner meetings, community events, the difficult phone calls.

Shadowing works because it transfers the how behind the what. A successor can read that a particular community leader is a key partner. Watching their mentor navigate that relationship — when to defer, when to push, which joke lands and which does not — teaches what no document can.

Where budget or timing makes full shadowing impractical, a hybrid approach still adds value: joint site visits, co-facilitated community meetings, and a standing weekly debrief during the transition window.

Making the Protocol Standard, Not Situational

The deeper lesson for boards and executive directors is that handoff protocols should not be improvised when a resignation letter arrives. Organizations that treat succession as a standing governance practice — with knowledge inventories updated annually and relationship maps reviewed at each program review cycle — convert an emergency into a routine.

For ICC2's member organizations, we recommend three concrete steps: first, require every program-level role to maintain a current knowledge inventory as part of annual documentation; second, budget explicitly for transition periods in every program plan, including overlap hours; third, add handoff readiness to the board's oversight agenda alongside financial review.

Community trust takes years to build and one careless transition to squander. The organizations that endure are the ones that treat a coordinator's departure not as a staffing event, but as a stewardship obligation — one that honors both the person leaving and the community staying.