Jump to a section
Which nonprofits need case management software?
Consider case management software when your organization provides ongoing services and needs a reliable shared record of responsibility, activity, and progress.
Start with the service relationship. A community program may receive a referral, speak with a participant, agree on a goal, provide several services, and follow up over time. The software needs to help staff understand that sequence. A list of names and contact details is only one part of the record. The next action and the person responsible for it matter just as much.
Use this guide if your team coordinates community support, recovery services, reentry, navigation, or another ongoing human services program. If your primary task is fundraising, event registration, property management, or clinical treatment, identify those requirements separately. Buying a participant tracking system should not depend on an assumption that it will replace every tool your nonprofit uses.
NTEN’s technology assessment framework considers engagement, infrastructure, leadership, and organization. That is a useful reminder that a purchase involves staff capacity and operating decisions as well as software features. Before building a shortlist, name the person who will own the rollout and the people who must approve the workflow.[1]
How is case management different from a nonprofit CRM?
Compare the work each system must support, rather than treating a contact database and a service record as interchangeable.
| System purpose | Typical question to test | What not to assume |
|---|---|---|
| Donor relationships | Who contributed, and what acknowledgement or fundraising follow-up is due? | Fundraising access should not automatically expose participant service records. |
| Participant services | What support occurred, who owns the next step, and what changed? | A contact history alone may not represent enrollment, notes, or service plans. |
| Volunteer coordination | Who is scheduled, trained, and assigned to a role? | A volunteer account should not imply unrestricted access to case records. |
| Program reporting | Which people and services meet the report’s definitions? | A dashboard total is not proof of the required funder submission. |
If a vendor uses the term customer relationship management, ask to see your service workflow. Some organizations configure a broad platform successfully; others prefer a purpose-built workflow. The decision should depend on the demonstrated result, maintenance responsibility, and cost. A category label does not establish that a particular product includes your required forms, permissions, or reports.
Document which system remains authoritative for donations, services, staff information, and finance. Identify any information that must move between them and who checks the transfer. Avoid assuming that an integration listed on a website includes the exact fields, direction, frequency, or error handling your team needs.
What should your requirements worksheet include?
Describe each requirement as a staff task with an expected result and an owner who can accept it.
| Task | Evidence to request |
|---|---|
| Receive a referral | Show how an inquiry becomes an enrolled participant without confusing the two. |
| Assign staff | Identify the responsible worker, coverage arrangement, and open next steps. |
| Document a service | Record the completed activity and show review and correction. |
| Coordinate a referral | Separate a resource suggested, a referral sent, and a confirmed response. |
| Manage several programs | Explain how involvement in each program appears without creating misleading totals. |
| Report to a funder | Reproduce one reporting question from a small dataset with known results. |
| Control access | Demonstrate a limited staff role as well as an administrator. |
| Leave the service | Provide a sample export and explain what it includes and excludes. |
Mark each row required, preferred, or optional. A required export may matter more than a visually appealing dashboard. Decide who can accept a workaround and who must approve a change in scope. Capture those decisions before the sales presentation, when it is easier to separate genuine requirements from attractive extras.
Include ordinary exceptions. A participant returns after closure, two programs serve the same person, a worker leaves, a note needs correction, and a referral has no response. These situations reveal whether staff can maintain a coherent record when work does not follow a straight path. Ask for evidence, not just a yes beside a feature name.
What should you ask to see in a nonprofit software demo?
Follow one fictional participant from referral through follow-up and reporting, with the staff who will use the system observing.
Create a short scenario: a participant contacts your program for help connecting with community services. One worker completes intake, another provides an agreed service, and a supervisor later covers a missed follow-up. Include one referral awaiting a response. Use the same scenario with every vendor so your team can compare the workflow rather than unrelated demonstrations.
- Find the person and show the relevant program involvement.
- Assign the next action and explain who sees it when the original worker is unavailable.
- Record a completed contact, then distinguish it from an unsuccessful attempt.
- Show a referral that remains unresolved and explain the follow-up process.
- Demonstrate a correction without silently making the original entry disappear.
- Open a report and identify how this person and the service appear.
- Show a limited-access role and an example of an export.
Ask a frontline worker to describe what they would do at each step. Ask the supervisor what they need to review. Ask the reporting owner to identify the records behind the total. Keep a decision log with observed evidence, unanswered questions, and a responsible follow-up person. A short focused demonstration should identify fit and questions for a more detailed implementation discussion.
Smores Health’s community services overview covers coordination, documentation, staff workflows, and reporting. Bring a blank form and a fictional example to evaluate that fit. Confirm specialized requirements separately, including external submissions and integrations. Use the demonstration to identify what fits, what needs configuration, and which questions need follow-up.[3]
How should you evaluate multi-program participant tracking?
Check whether staff can distinguish the person, their involvement in each program, and the services delivered during the reporting period.
Use a fictional person who participates in two programs. Ask the vendor to show where the organization records each involvement, who can see the relevant information, and how a program-specific report treats that person. Then run an organization-wide question. Decide whether that question counts unique people or program enrollments before judging the result.
A person participating in two programs can legitimately contribute to two program counts while remaining one person in an organization-wide unique-person measure. The definition must be visible. Do not allow the software’s default labels to decide the meaning of a funder report without review. Test duplicate records and uncertain matches through the supported process rather than guessing that similar names belong to the same person.
Also test a return after closure. Which previous information remains relevant, and what needs updating? Who decides that a new service period begins? What appears in the active caseload? Record these operating choices in the implementation scope. They affect staff work and reporting even when the screens initially look straightforward.
How can you test outcomes and grant reporting?
Bring one report specification and a small fictional dataset, then compare the output with totals your team calculated independently.
Choose a dataset simple enough to review by hand. Include five people, several contacts, one unfinished referral, and one outcome whose result is unknown. Write down who should count, which dates apply, and what evidence qualifies. If the vendor produces a different answer, trace the difference before adding more records.
| Measure | Question |
|---|---|
| People served | Which activity or enrollment qualifies a person for inclusion? |
| Service contacts | Which completed activities count, and how are attempts separated? |
| Referral results | Are you counting referrals sent, responses received, or services obtained? |
| Progress | What evidence supports the result and which date is used? |
| Unknown results | How are missing follow-up and incomplete information shown? |
| Corrections | How does a later correction change an earlier report? |
Ask the reporting owner to explain how the result will be reviewed and delivered. An export can support a reporting process without being a direct submission to a funder. Confirm accepted formats and any manual steps. Avoid assuming that a vendor’s use of the phrase grant reporting includes budget accounting, restricted-fund accounting, or grant application management.
Use operational reporting to identify unanswered questions and improve follow-up. Do not turn a rise in recorded activity into a claim that the software caused better long-term outcomes. The record can support evaluation, but conclusions depend on the quality of the underlying information and the evaluation method.
How should nonprofits compare case management software pricing?
Compare a written first-year, renewal-year, and growth scenario using the same scope for every vendor.
Specify the staff roles, number of users, programs, locations, participant volume, storage needs, and required integrations. Ask whether supervisors, temporary workers, volunteers, or external collaborators are priced differently. Identify what changes when the organization adds a program or increases usage. Request current, written pricing for that scope so your team can compare like-for-like costs.
| Cost | What to clarify |
|---|---|
| Recurring subscription | Included features, usage limits, and charging basis |
| Configuration | Forms, roles, reports, and meetings included in setup |
| Migration | Records, attachments, relationships, and acceptance checks |
| Training | Number of sessions, audiences, materials, and later retraining |
| Optional services | Integrations, additional storage, messaging, and extra support |
| Internal effort | Staff time to clean data, review forms, and prepare the team |
| Renewal and exit | Notice, potential changes, export assistance, and any charges |
Add quoted recurring charges, one-time setup, expected usage charges, and internal effort to compare the first year. Keep assumptions visible. A cheaper subscription can require more internal work if the nonprofit must build its own reports or maintain a separate follow-up tracker. Ask each vendor who owns each task and what support is included.
If a grant funds the purchase, have the responsible finance or grant reviewer check the award’s rules and timing. Do not assume a software expense is eligible merely because the organization is a nonprofit. Keep that approval separate from evaluating whether the product meets program needs.
What access and data questions should you resolve?
Inventory the information you hold and ask the responsible reviewer to define access, sharing, retention, and vendor requirements.
The National Council of Nonprofits recommends beginning data-risk assessment with an inventory of collected information and where it is stored. Use that inventory to identify which records are needed for service delivery and who needs access. This guide provides purchasing questions, not a determination of your organization’s legal obligations.[2]
Ask for a demonstration of a limited role. Can it search for people outside its assignment, open sensitive attachments, export records, or share information? Review coverage and departure scenarios too. If volunteers help with scheduling, they may need a very different view from a supervisor reviewing service documentation. Document that distinction rather than relying on job titles alone.
Request current security materials, incident contacts, recovery commitments, and data-return terms. Have the designated reviewer assess them against the actual information and services in scope. A logo is not a complete answer to a specific access or contractual question. Keep the written commitments and unresolved items with the purchasing decision.
How should you plan migration and staff adoption?
Launch around a defined workflow with named owners, a checked migration sample, role-based practice, and clear support responsibilities.
Inventory active and historical records before discussing migration. Map important fields, attachments, and relationships. Identify inconsistent status labels and uncertain duplicates for review. Decide what will transfer, what will remain accessible elsewhere, and who accepts the result. A successful upload is only one step; staff must also be able to find and understand the information.
Practice with fictional records first. Have staff complete intake, record an activity, correct an entry, hand off work, and answer a reporting question. Include an ordinary exception, such as an unavailable worker or an unanswered referral. Ask where staff expect to find information and where they become uncertain. Use that feedback to improve configuration or training before launch.
Agree on where new records will be entered during the transition and how outstanding follow-ups will move. Set a support contact and a process for reporting issues. After launch, review actual workflow problems with the owner rather than continuously adding fields without a purpose. Keep changes controlled enough that earlier records and reports remain understandable.
How do you make the final software decision?
Choose based on demonstrated requirements, written scope, implementation capacity, and cost, with unresolved questions made explicit.
Use a simple scoring scale: unknown or unmet, workaround proposed, demonstrated with details pending, and demonstrated with scope confirmed. Apply it to each requirement. Do not let a high average conceal one failed mandatory requirement. Ask the people who will use the system whether they can explain their daily workflow and the remaining manual work.
Smores Health is worth evaluating when your nonprofit coordinates relationship-based services and wants to review participant records, staff responsibility, documentation, referrals, and reporting together. Bring your most important workflow to a 20-minute walkthrough. Use the conversation to identify fit and the configuration questions that need a written answer before purchase.
Frequently asked questions
Is nonprofit case management software the same as donor software?
Not necessarily. Test participant services and fundraising as separate workflows, with appropriate access and records for each. Do not assume one system replaces the other because both store contact details.
What should a small nonprofit buy first?
Identify the most important service workflow and the problems your current tools create. Start with the requirements needed to solve those problems, including reporting and access. Compare implementation effort as well as subscription cost.
Can software automatically produce our grant report?
Provide the exact reporting specification and test it with known records. Confirm definitions, fields, format, and delivery separately. A generic report or export does not establish that an external submission is supported.
How do we get Smores Health pricing?
Use the pricing and information page or book a walkthrough. Describe staff roles, programs, required workflows, migration, and training needs so the discussion has a concrete scope.
What should we bring to the demo?
Bring a blank form, a fictional service journey, and a reporting question. Choose the two or three tasks your team most wants to improve. Do not send identifiable participant records for a sales demonstration.
Sources and product pages
Sources support the specific guidance cited above. Program guidance is not a universal requirement. Product pages describe capabilities to verify against your organization’s needs.
- Technology adoption in nonprofits: An analysis of NTEN’s Tech Accelerate data: NTEN. Reviewed October 9, 2026. Organizational technology assessment context.
- Cybersecurity for Nonprofits: National Council of Nonprofits. Reviewed October 9, 2026. Data inventory and security planning guidance.
- Community services workflows in Smores Health: Smores Health. Product overview. Confirm included capabilities and implementation scope.