Start with the responsibilities that must continue
List who handles donor requests, checks exceptions, owns processor questions, reviews acknowledgments and authorizes record changes. One person may cover several roles, but each recurring task needs an identified owner and backup. Record where current procedures live and when they were last checked. Avoid describing someone as “the administrator” without explaining which system and which actions that role actually covers. A handover is useful when the incoming person can find the next legitimate action without guessing.
Match access to the work being transferred
4aGoodCause documents Admin and Read-only staff roles, with very different modification rights. Do not infer a custom permission level from a job title. Have the organization’s authorized account owner assign appropriate access using the provider’s current process. The outgoing person’s password should not become the handover mechanism. Keep any credential delivery inside approved secure channels, and confirm the incoming person can reach the needed records before treating access as complete.
Use a small acceptance checklist
The incoming owner should be able to identify the authoritative record for a gift, find the official change route, locate acknowledgment settings and explain the open exceptions. Mark each item demonstrated, still waiting or unresolved in the organization’s own notes. Include the cut-off time and next review date. Do not close the outgoing role’s access until the organization’s authorized offboarding plan says to do so; this guide does not decide employment access or security policy.
A fictional first-day handover
The incoming coordinator can view reports but cannot modify subscriptions. That may be the intended role, not a broken account. The handover should identify the authorized colleague who makes changes and the escalation route for urgent donor requests. Three unresolved cases remain assigned rather than disappearing into a folder named “old work.” Use the anonymous status worksheet to check the queue’s arithmetic, and migration scope only if the software itself is changing.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- 4aGoodCause staff roles — Merchant documentation · help.4agoodcause.com · Merchant-controlled · checked 2026-09-30
- 4aGoodCause subscription changes — Merchant documentation · help.4agoodcause.com · Merchant-controlled · checked 2026-09-30
- NCSC: using SaaS securely — Research study · ncsc.gov.uk · Publisher independence not verified · checked 2026-09-30