Back to all posts Checklist

When Staff Leave: A Phone System Offboarding Checklist for Nonprofits

Staff turnover creates real phone system risks: orphaned extensions, unreturned voicemails, exposed donor data. Here is the offboarding checklist most nonprofits skip.

People silhouetted moving up illuminated stairs
Photo by Wu Zhongyi on Unsplash

Most nonprofits have a solid offboarding process for email and Google Drive. The phone system? Usually an afterthought. A departing development director keeps forwarding her extension to her cell for three months. A former volunteer coordinator's voicemail greeting still plays her name in October. A terminated employee's softphone stays logged in on a personal laptop, silently receiving calls from major donors.

These are not hypotheticals. They are the three most common gaps we see when nonprofits move to a new provider and audit their existing setup. Here is a practical offboarding checklist that closes them.

Why phone offboarding gets skipped

Phone systems sit in a weird ownership gap. IT usually manages accounts. HR runs offboarding. Operations owns the caller experience. When someone leaves, each team assumes another team handled the phone piece. Meanwhile, the departing staffer's extension is often tied to real relationships: a major donor who has that direct number saved, a program partner who has been calling it for four years, a reporter who has it in their contacts file.

Deleting the extension outright is bad. Leaving it untouched is worse. You need a defined sequence.

The 24-hour checklist (do these on the last day)

These are the security-sensitive items. They should happen on the departure date, not "sometime that week."

  • Disable the user account in your VoIP admin console (not just delete, disable first so you preserve settings)
  • Force-logout all active softphone and mobile app sessions
  • Revoke any API tokens or app integrations tied to the user (CRM connectors, calendar syncs, SMS apps)
  • Rotate any shared line PINs, conference bridge codes, or auto-attendant admin passwords the person knew
  • Remove them from any call queues, ring groups, and after-hours on-call rotations
  • Disable voicemail-to-email forwarding to their personal address
  • Download and archive their voicemail box (many providers auto-delete after 30 days)
  • Pull the last 90 days of their call history for handoff context
Watch for this: Softphone apps installed on personal phones are the biggest overlooked risk. A remote-logout from the admin console handles it, but only if you actually do it. Do not rely on the person to "delete the app."

The first-week tasks (protect the relationships)

Once the account is locked down, focus on the callers. The person who left had a direct line for a reason, and those callers deserve a graceful handoff.

  1. Update the voicemail greeting. Replace the personal greeting with a temporary one: "You've reached the development office. Sarah is no longer with our team. For immediate assistance, please press 0 or call our main line at..." Keep her name in the greeting for 60 to 90 days so callers know they reached the right place.
  2. Set up call forwarding to a successor or team inbox. Do not forward to a random staffer's cell. Route to the department's shared queue or to the interim owner of those relationships.
  3. Add a follow-up task to your CRM. Anyone who calls the old extension in the next 90 days should get flagged for personal outreach from the replacement staffer.
  4. Notify high-value callers proactively. Pull the top 25 callers to that extension from the last year. Have someone reach out personally with the new contact info. Do not make major donors discover the transition through a voicemail greeting.

The 90-day decisions

After three months, revisit the extension. You generally have three options:

  • Reassign the number to the successor if the role is filled. Update the greeting, transfer the voicemail box, and notify frequent callers.
  • Retire the extension internally but keep the DID pointing to a queue or general inbox for another 6 to 12 months. Especially important for grants officers, executive directors, and anyone who has been quoted in press.
  • Release the number only if it has genuinely low external exposure. Once a phone number is released back to the carrier pool, you cannot get it back.

Never release a number that appears on printed materials, grant applications, event signage, or vehicle wraps until you have confirmed those assets are updated or retired.

Special cases worth planning for

A few scenarios need their own micro-playbook:

  • Involuntary terminations. All 24-hour items happen before the termination meeting, not after. The person should not have working phone access when they leave the building.
  • Executive departures. The ED's direct line often has decades of relationship history. Board notification, donor outreach, and a public transition message usually take precedence over any technical reassignment.
  • Volunteer turnover. Volunteers with softphone access should be on a quarterly access review, not just offboarded ad hoc. Most nonprofits have "ghost accounts" for volunteers who stopped showing up two years ago.
  • Contractors and consultants. Time-box their access from day one with a scheduled disable date, so offboarding happens automatically.

Build the checklist into HR, not IT

The single best change most nonprofits can make: add the phone offboarding steps directly to your HR exit checklist, right next to the email and badge items. Assign each task to a named role. Review the list every time someone leaves, even if you think it does not apply.

If you are not sure what your current provider allows for remote logout, session control, or voicemail archiving, that is worth a 30-minute conversation. We help nonprofits audit their phone offboarding gaps as part of any migration review. Reach out if you would like a second set of eyes on yours.

#offboarding #security #operations #checklist #staff-transitions