Independent recurring-gift guidance for small nonprofit teams: understand records, route donor changes and hand over unfinished work clearly.
These field notes explain the product, workflow, and tradeoffs that can change the decision.
Donor Continuity Desk is for nonprofit staff and volunteers who need a clear view of recurring-gift administration. A contact, a historical donation and an active recurring instruction are not interchangeable. Our guides help you find the right evidence and the next authorized owner, without collecting donor records or handling payments.
Start with Records if a spreadsheet or import is unclear. Choose Gift changes when a donor asks for an amount change, cancellation or missing acknowledgment. Use Handover when a colleague or platform is changing. The fictional exception board is an illustration, not a live donor dashboard.
Our worksheets work locally with anonymous counts. The product assessments cite current primary documentation and explain limitations, alternatives and the option of keeping an adequate existing system. We have not performed customer-product tests and do not promise increased donations. This is an independent publication by Jure Erlic, not a nonprofit support desk or a merchant partner site.
Who is this person?
A profile is not an instruction to take a payment.
What was recorded?
A past gift does not prove another is scheduled.
What should happen next?
Its current state belongs in the authorized provider record.
Choose the task in front of you.
Identify the right evidence before accepting an import or a count.
Follow this path →02 · 3 guidesSeparate future instructions, donor access and acknowledgment questions.
Follow this path →03 · 5 guidesTransfer responsibility, assess migration and compare platforms only when needed.
Follow this path →Anonymous numbers only. Nothing saved or sent.
One review item, one category, one cut-off time. Matching totals are not evidence of successful payments.
Read the category definitions →Start with the missing evidence.
Leave uncertainty visible for the next owner.
Choose the question closest to your situation, then follow the related guides when they help you take the next step.
Start with the question: who is the person, what happened, or what is scheduled next? Those questions need different evidence.
Read the guide →Practical guideCount each review item once at one cut-off time. Matching totals show that the queue is classified, not that donations succeeded.
Read the guide →Practical guideCheck the intended record type, mapping and exception report before accepting an import. A successful upload is not a completed migration.
Read the guide →Practical guideChanging a future gift, stopping future gifts and reviewing an earlier payment are separate requests. Confirm which one the donor wants before acting.
Read the guide →Practical guideStart from the nonprofit’s genuine donation receipt or donation page. Do not guess a portal address or ask the donor to share a password.
Read the guide →Practical guideA missing email is a communication symptom. Check the recorded gift and receipt configuration separately before describing the payment outcome.
Read the guide →Practical guideHand over responsibilities, authorized access and unresolved cases—not shared passwords or an unexplained export.
Read the guide →Practical guideContacts and historical gifts are not the same as active payment instructions. Obtain a specific provider-to-provider plan before promising continuity.
Read the guide →Buying guideKeep an adequate system when the problem is ownership or procedure. Compare platforms only against a written requirement your current setup cannot meet.
Read the guide →Original planning aid. Keep real identifiers in your organization’s approved systems.
Prepare the handover →The starting distinction is grounded in 4aGoodCause’s separate contact import, donation-history import and staff-role documentation. These are merchant-controlled sources, not independent performance tests.