How nonprofit leaders can respect a completed contribution and prepare the work for its next chapter
By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.
A volunteer says they need to step away. The coordinator looks at next month's schedule and sees an empty space. The volunteer looks at the same conversation and wonders whether everything they gave will now be overshadowed by their decision to leave.
Both concerns deserve attention. The work must continue, and the person must be allowed to finish. A thoughtful goodbye can protect both without turning a departure into a negotiation about loyalty.
This is about ordinary, voluntary departures: a project completed, a schedule changed, a new responsibility at home, or simply the decision that it is time. A misconduct allegation or safeguarding concern requires the organization's appropriate procedures, not an informal farewell in place of them.
For a routine departure, the central question is useful and humane: what would make this contribution feel complete, while leaving the next person able to begin?
Leaving is not a verdict on the mission
It is easy to interpret a departure personally, especially in a small organization where people know one another well. A coordinator may have invested considerable time in training someone. A founder may feel the pressure of keeping a service open. The departing volunteer may care deeply about both people and still be unable to continue.
NCVO's Time Well Spent 2023 research offers helpful perspective. Among lapsed volunteers, defined as people who had volunteered within the previous three years but not the previous 12 months, 31% cited having less time because their circumstances had changed. That was the most common reason reported. This is a finding from that survey, not a universal estimate of why volunteers leave every organization. It does remind us to avoid assuming that departure means dissatisfaction or indifference. NCVO volunteer retention findings.
A useful first response is simple: “Thank you for telling me. We appreciate what you have contributed. Let's work out what is realistic before your last day.”
That response does not pretend the scheduling problem has disappeared. It puts the problem where it belongs: in the organization's planning, rather than in an argument about whether the volunteer cares enough.
Define a finish that is actually possible
A departure can quietly become a new assignment. Someone offers to write a few notes and is then asked to rebuild a filing system, train a replacement, and remain available until the replacement feels confident.
That is not a clear ending. It is a continuation with an uncertain workload.
Agree on a small, realistic closing task if the volunteer is able and willing. Perhaps it is identifying the current version of a document, explaining one recurring decision, or marking which items remain unfinished. Let them say what they cannot complete. An honest list of unfinished work is more useful than a reassuring promise made under pressure.
The coordinator should then decide what to continue, simplify, postpone, or stop. Not every activity deserves an immediate replacement. A departure can reveal that a task has survived because one generous person kept doing it, rather than because anyone recently checked whether it was still needed.
Volunteering Australia's 2024 National Standards support defining and regularly reviewing roles with volunteers, including their interests and experience. These are best-practice standards, not a universal legal requirement. They offer a useful reminder that a role is something to design and revisit, not merely a vacancy to refill. National Standards for Volunteer Involvement.
A handover should explain the unresolved decision
Consider this illustrative scenario, not a report of an actual organization.
A volunteer has been arranging speakers for a small community learning series. She is leaving at the end of the month. The shared folder contains invitations, speaker biographies, and several versions of the schedule. At first glance, everything appears to be there.
But one speaker has agreed only if the session can finish early. Another has offered two possible dates without choosing one. A third sent presentation slides that have not yet been checked for accessibility. None of those distinctions is obvious from the filenames.
The most valuable closing work is not a polished essay about the series. It is a short explanation of the open decisions: which arrangements are confirmed, which are conditional, and who is waiting for an answer. The coordinator assigns each unresolved item to a named person. The next volunteer starts with that map rather than having to reconstruct the story from email fragments.
Now imagine the departing volunteer can offer only 20 minutes. The coordinator uses that time to ask about the two most time-sensitive uncertainties. Other housekeeping waits. A perfect archive is less important than avoiding a promise that nobody realizes is still pending.
This is a practical design choice, not a tested formula: prioritize information according to the consequence of losing it. A decorative slide template can usually be recreated. A promise made to a speaker needs to be found before someone accidentally contradicts it.
The useful test comes after the handover. Can the person taking over explain the next action without asking the departing volunteer to stay on call? If not, clarify the missing point while there is still an agreed opportunity to do so. Do not leave “ask the former volunteer” as the permanent operating procedure.
Make the administrative ending calm and predictable
NCVO's guidance on ending volunteering recommends arranging a handover, inviting feedback, recognizing the contribution, and checking whether the person wants future contact. Its safeguarding guidance also emphasizes ending role-based access and retrieving organizational property. These are sensible management references to adapt to the organization's own policies and circumstances. Ending volunteering well; ending the volunteering relationship.
Explain the process before the last day. Returning a key or removing an account should not arrive as a surprise that makes someone feel suddenly distrusted. Keep the tone ordinary: the role is ending, so its access is ending too.
Use the organization's approved process to transfer records and remove permissions. Do not ask people to share personal passwords. Records connected to complaints, incidents, or other retention requirements need the responsible person's direction rather than casual deletion. A friendly relationship can continue without retaining operational access.
Ask what the ending revealed
A farewell conversation is not the place to demand proof that the volunteer had a good experience. “You enjoyed it, didn't you?” invites reassurance. A more open question is: “What was harder to manage than you expected?”
Someone may explain that the advertised two-hour shift regularly required another hour of preparation. They may have enjoyed the activity but struggled with transport. They may say that messages sent late at night made them feel obliged to respond immediately. These are possibilities to listen for, not assumptions about why any particular person is leaving.
Keep feedback optional. Some people want a conversation; others prefer a short written response or no feedback at all. The ability to leave respectfully should not depend on completing a final questionnaire.
Then distinguish between listening and promising. A coordinator can acknowledge an issue without guaranteeing an immediate solution. “I understand the preparation time was not clear. I will review the role description before we recruit again” is a manageable commitment if the coordinator has authority to make it. A vague promise to transform the whole program is less useful.
If the discussion raises a safety concern, route it through the appropriate reporting process. Do not treat a farewell conversation as confidential in ways the organization cannot responsibly honor.
Measure completion as well as continuity
An organization that measures only how many volunteers remain may miss a valuable kind of success. Someone completed the project they agreed to do. Someone contributed during a season when they had time. Someone learned enough to move into another opportunity. Their departure does not erase the work.
For a small team, a modest record can help: the role's end date, what was completed, which work was reassigned, and whether the necessary closing actions occurred. Keep personal explanations out unless there is a legitimate reason to retain them under the organization's policies.
Over time, look for operational patterns rather than labeling people. Are roles repeatedly expanding beyond their description? Are departures exposing information that exists only in one person's inbox? Does the same activity require a hurried rescue every few months? Those questions point toward changes the organization can make.
They also protect future volunteers. Recruiting another enthusiastic person into an unchanged, unmanageable role is not a solution to the previous departure.
Let gratitude be the final message
A good goodbye does not need an elaborate ceremony. It needs a clear acknowledgment that the contribution mattered and that the person is not being punished for ending it.
Be specific without exaggeration. Name the work that was done, the care that was visible, or the difficulty the volunteer helped resolve. Ask before making a public announcement or sharing a photograph. If a reference is appropriate, describe only what can be honestly supported.
Most importantly, do not attach a fresh request to every expression of thanks. “We appreciate everything you did” should be allowed to stand on its own.
The organization still has responsibilities after someone leaves. It must make choices about capacity, prepare successors, and keep its promises. Handling those responsibilities well is one way of honoring the volunteer's contribution, because it prevents their generosity from becoming an indefinite obligation.
A completed season of service deserves to feel complete.
What would someone leaving your organization need to hear, and what would the next person need to know, for both to move forward with confidence?

