What is Case Management Software?

A definition for Australian service providers:

Unfortunately, the phrase “case management software” now means two completely different things, and the gap between them is costing not-for-profits dearly. To a community, health or public sector provider, it is the system that runs service delivery across the whole client journey, from intake to exit. It manages initial assessment, support planning, service delivery, reviews and outcomes for individuals, families and groups, often for clients receiving help from several programs and funding bodies at once. And it produces the data those funders require for reporting.

Case management in this context is not customer-service ticketing. It is not CRM, and it is not social media response software. Nor is it about using AI agents to speed up client response times. These distinctions matter, because the term “case management” has been steadily blurred by large technology vendors applying a customer-service framing to a sector that can ill afford to get its technology spend wrong.

This is a distinction I deal with constantly. I speak with several hundred not-for-profits a year, and helping them understand the line between the case management software they actually need and the “buzzy” CRM and customer-service products marketed to them comes up again and again. It is an issue that concerns me deeply, because choosing the wrong system is especially costly for not-for-profits, who rarely have the funds to absorb a decision this important going wrong. This article sets out what case management software actually is, for managers of non-profits and government agencies who need to measure and improve client outcomes and stay on mission.

What is case management software, really?

In human, community and health-based services, a “case” is an engagement a person, family or group receives from a non-profit provider or government agency, and “case management” is the structured practice of planning, coordinating, managing and delivering that support over time. Case management software is the operational backbone for that work. It holds the client record, tracks every interaction and service contact, manages the support plan, schedules and records service delivery work, captures notes and outcomes, and meticulously collects the datapoints necessary to report to the bodies that fund the services.

The defining feature is the workflow it supports: the full client lifecycle from first contact through to case closure. Everything in a case management system is built around moving a client through that journey and evidencing what changed for them. Sophisticated case management enables a “single view of client journey” through multiple (often concurrent) programs of service within an organisation, whilst ensuring only the correct teams and personnel have access to data about the client necessary for them to complete their work.

Why “case management” gets confused with CRM and customer service software

There are two unrelated things wearing the same label.

1. The first is human, community and health-based services’ case management (described above): service delivery for vulnerable clients, often funded by government and delivered by community organisations, health providers and government agencies. These services can be delivered to an individual person, group or family. They span areas such as family and domestic violence (DV) support, alcohol and other drug (AOD) treatment, mental health services, out-of-home care (OOHC), homelessness and housing support, child and family services, disability support, and settlement services for migrants and refugees. And this is only a fraction of the picture: the ACNC charity program register classifies Australian nonprofit programs across hundreds of distinct service types, a measure of just how broad and varied the missions in this sector really are.
2. The second is customer-service management, helpdesk and campaign management: In this world a “case” is a support enquiry, an “agent” (human or AI) resolves it, and the goal is fast resolution and individual customer retention. This is where a lot of major vendor marketing now lives. That same tooling has a genuine and valuable home in donation management, fundraising and donor or supporter engagement, which is where a CRM earns its keep. What it is not is service delivery case management. (If you are choosing a CRM for fundraising and engagement, we cover what to look for in CRM for nonprofits: what you need to know to choose the right one.)

Read the big CRM providers’ own descriptions of “case management” and the sleight of hand is easy to see. They open with customer service and social media response times, then define case management software as a tool for managing customer interactions across digital channels – social media, email, web contact forms – with agents logging in to work through cases sorted by priority. Every word of that describes a customer-support and engagement platform. The trick is the label on top: by calling it “case management,” they borrow a term that means something specific and far more demanding in human services, and quietly attach it to a product that does none of that work. It has almost nothing to do with what a family violence service, a primary mental health provider or a veterans’ affairs service means by case management.

The overlap is convenient for big vendors. They have a ticketing and engagement product, the human-services sector uses the word “case,” and so the category gets redefined in those vendors’ terms. If you deliver human, community and health-based services, that redefinition leaves out almost everything you actually need. We set out why the major platforms carry real risk for service delivery in Why Salesforce and Microsoft are risky for nonprofit client case management (CCMS).

What case management software covers: The client intake-to-exit workflow

Real case management software is organised around the service delivery lifecycle:

• Intake and referral. Capturing referrals from multiple sources, recording consent, and triaging clients into the right program.
• Assessment. Structured, often standardised assessment tools that determine eligibility, risk and need. Capacity and waitlists are also often managed here.
• Support planning. Goals, actions, and the plan that coordinates services around the client.
• Service delivery. Recording every session, contact, activity or workshop/event, against the right program and funding source. This area can be different per program/service offered. Some services report to DEX, some need brokerage and financial details recorded, some require incident reporting, some are focused on Out-of-Home-Care (OOHC) or criminal justice functions and require an entirely more complex dataset for handling service delivery… the list goes on.
• Review. Reassessment over time, plan updates, and escalation where risk changes.
• Exit and closure. Closing the episode of care, recording the reason, and capturing outcomes at exit.
• Outcomes. Measuring and evidencing change for the client, not just counting activity.

A customer-service platform models a ticket/case that opens and closes. A human or health-based case management system supports a person, group or family whose circumstances change over months or years, across many services. Those are different data structures and require completely different software.

Case management for different service delivery models

Human, community and health-based funded services are not uniform, and the software has to handle that variety natively:

• Single and multiple clients. Individual case management, family or whole-of-household work, and group programs where many clients attend the same activity. This is a major dividing line. Customer-service “case management” is usually built around one client, one case, one enquiry, and one resolution, so it almost never handles group-based service delivery. For providers running group programs that gap is fatal: once you need to record attendance, outcomes and funding against a group, a ticketing-based system cannot do it, and you are forced to replace it.
• Light-touch to intensive. A single information-and-referral contact and a multi-year intensive support arrangement are both “cases,” with very different recording needs.
• Episodic and continuous. Short closed episodes of care alongside long-term ongoing support.
• Voluntary and statutory. Self-referred clients and mandated or court-directed clients, with the consent and reporting differences that implies.
• Individual and program-level funding. Tracking funding or brokerage at both the individual level or the program level.
• Incident management. Recording, escalating and following up incidents tied to clients and service events, including the obligations that come with mandatory and statutory reporting.
• Risk management. Capturing and reviewing client and worker risk over time, with assessments that update as circumstances change and trigger the right response.
• Reporting to many funding bodies. Producing the different reports each funder requires from the same underlying service data, across multiple programs and jurisdictions, while maintaining good data governance.

If a system can only support one of these well, it is not built for the sector.

Case management across multiple programs, services and funding models

Most larger providers run many programs at once, each with its own funding agreement, rules, activities as well as outputs and outcomes reporting. A single client might be receiving services under two or three programs simultaneously. Often a client receiving services under one program is internally referred to others.

Case management software has to keep program, service type and funding source attached to every piece of activity, so that the same client record can correctly attribute service delivery to the right contract. This is also what makes funding models work: output-based, outcomes-based, block-funded and fee-for-service arrangements all need the activity tagged so it can be acquitted against the correct agreement.

Case management software and statutory funder reporting

This is the part that customer-service software and CRM simply does not do, and it is one of the clearest lines between the two categories. Many Australian service providers report into government data collections as a condition of funding. Case management software has to capture data in the right shape and produce compliant outputs for each collection a provider is funded against. A few of the major ones include:

DSS Data Exchange (DEX)

The Department of Social Services’ program performance reporting solution. It shifts the focus from outputs to service delivery outcomes, and uses Standard Client/Community Outcomes Reporting (SCORE) to measure client change. From 1 March 2026, reporting requirements for most DSS-funded client-facing services have been streamlined. DEX details here.

Primary Mental Health Care Minimum Data Set (PMHC MDS)

The collection used by Primary Health Networks, their commissioned providers and the Department of Health and Aged Care to monitor primary mental health service delivery, structured around episodes of care. PMHC MDS details here.

AODTS National Minimum Data Set

The Alcohol and Other Drug Treatment Services collection reported to the Australian Institute of Health and Welfare. AODTS NMDS details here.

…and all the rest

These three are only the start. There are literally hundreds of Commonwealth, state and territory collections, each with their own data specification, codes, formats and submission process – and most providers report into several at once.

Getting the underlying data model right is key

A provider operating across multiple programs and jurisdictions may need to report into several different portals and formats. This is where the underlying data model matters more than any single report.

The same client details – gender, Aboriginal and Torres Strait Islander (ATSI) status, country of birth, primary presenting issue – are asked for by collection after collection, but each one can code and format them differently. A case management system with a flexible data model captures each fact once, then maps and transforms it to whatever each collection requires. Gender, for example, is recorded a single time and flows out correctly to DEX, to PMHC MDS and to everything else.

A rigid system, or one not built for human, community and health-based services, cannot do this. It forces staff to re-enter the same information in a different shape for every funder, or to keep parallel records that quietly drift apart. Worse, it can mean duplicating a client record for each program they touch, so the same person exists several times over with no single view of their journey.

Good case management as the foundation for Monitoring and Evaluation (M&E)

A capable case management system does more than run individual cases. Because it captures structured data across every client, program and service, it becomes the foundation for an organisation-wide monitoring and evaluation (M&E) framework: the way an organisation measures whether its services are working and improving.

This is where data captured at the front line turns into organisational intelligence. A proper case management system lets you layer M&E across the whole organisation to:

• Identify service needs and gaps. Aggregated client and demand data shows who is being reached, who is not, where waitlists and unmet need are building, and which services to grow or redesign.
• Drive service delivery excellence and continuous improvement. Consistent data on what is delivered and what works feeds a genuine improvement loop, instead of relying on anecdote.
• Evidence client outcomes. Measuring client circumstances at intake, through service, and at exit shows how much better off people are as a result of the service, not just how much activity took place.
• Provide evidence to funders, donors and boards. Credible outcomes data supports acquittals, funding submissions, donor reporting and board assurance, and strengthens the case for renewed and new funding.
• Align and demonstrate mission. Ultimately, M&E connects daily service delivery back to the organisation’s mission, showing whether the work is achieving what the organisation exists to do.

This is also why the outputs-versus-outcomes distinction matters so much. Counting activity (sessions delivered, clients seen) tells you what you did. An M&E framework tells you what changed. Frameworks like DEX’s SCORE are built precisely to capture that shift, and a case management system that records outcomes at the point of service makes organisation-wide M&E a by-product of good practice rather than a separate reporting burden.

Privacy, security and the Australian Privacy Act in case management – The risks of getting it wrong

Case management also means holding some of the most sensitive personal information there is. The Privacy Act 1988 and the 13 Australian Privacy Principles (APPs) govern how that information is collected, used, disclosed and stored, and health information is treated as sensitive information, which carries higher protection than ordinary personal information. This shapes how case management software, and especially any AI features inside it, must be handled.

The key points for providers:

• The Privacy Act applies to AI, not just to people. The OAIC has confirmed the Privacy Act and APPs apply to all uses of AI involving personal information, including where information is used to train, test or run an AI system. Putting client information into an AI feature is a use and disclosure of that information, and it must comply.
• Sensitive information needs extra care. Health and other sensitive information generally cannot be used for a secondary purpose without consent. As a matter of best practice, the OAIC advises organisations not to enter personal information, and particularly sensitive information such as health information, into publicly available AI tools, given the significant privacy risks, and to check that a product’s terms do not permit the vendor to use those inputs to train its own models. Public tools, where inputs may be stored, accessed by vendor staff, or used to train future models, are high-risk for sensitive data.
• You stay accountable for overseas vendors. Under APP 8, where data is disclosed to an overseas provider (which includes most major cloud and AI vendors), your organisation remains accountable for what that provider does with it. Where the data physically sits, and who can access it, matters.
• Vendor model training is usually not permitted. If a vendor uses your client data to improve its models, that is a secondary use of sensitive information that was almost certainly never consented to, and generally is not lawful under APP 6.

In practice, do not embed AI services into your case management system unless you can answer yes to all of the following:

• You have a Data Processing Agreement (or equivalent) with the vendor that guarantees how data is handled, where it is stored (data sovereignty), and that it will not be used to train the vendor’s models.
• You have confirmed the data does not leave the jurisdictions your funding and consent allow.
• You have approval from your funding body to use those tools, where the funding agreement requires it.
• You have completed a privacy impact assessment for the AI use.

“The platform has AI” is not a good reason to use it.

The OAIC is explicit that AI products should not be used simply because they are available. For a provider handling vulnerable clients’ health and personal information, getting this wrong is not a feature gap, it is a breach.

Why the “Nonprofit Cloud” framing misrepresents case management

A common move in the tech industry is to take a CRM and customer-service platform, bundle it, and brand it for nonprofits. The branding signals “this is for you,” but the underlying product is still a sales and service platform with a sector label on it.

The problem is not that many nonprofits do not need a CRM, especially those whose primary source of income is grant funding. Many may use one for fundraising, donor management and marketing, which is genuinely what a CRM is good for. The problem is the implication that a nonprofit-branded CRM is therefore a case management system. It is not. Fundraising, donor communications and social media engagement are the front-of-house activities of running an organisation. Case management is the service delivery itself: the statutory, often externally-funded work the organisation exists to do.

Branding a marketing and customer-service platform as a “cloud for nonprofits” reframes case management as a CRM feature. For a provider with funding agreements, statutory reporting obligations and complex service models, that framing leads to expensive implementations that still cannot do the core job, because the core job was never what the product was built for.

I personally know of several multi-million-dollar implementations of big-vendor CRM systems, sold as “case management,” that have fallen well short of what the organisation needed. The pattern from there is familiar: rather than walk away from the sunk cost, the organisation keeps funding fixes and customisations, pouring good money after bad to patch a problem that began as a poorly framed and poorly sold “case” solution.

Are Salesforce and Microsoft “nonprofit” products case management systems?

In short, no. This is the most expensive mistake in the sector, and it happens repeatedly. The nonprofit offerings from the major platform vendors are CRM and business platforms. They are very good at what they are designed for: relationships, fundraising, donor and supporter management, marketing and engagement. They are not purpose-built human, community and health-based services case management systems.

Salesforce Nonprofit Cloud and case management

Salesforce’s nonprofit offering (Nonprofit Cloud) is a CRM platform. It can be configured towards case management, but intake-to-exit service delivery, multiple service and funding models, and statutory reporting such as DEX, PMHC MDS and AODTS are not capabilities you get out of the box. They are often expensive and unnecessary custom builds on top of the platform.

Microsoft nonprofit products and case management

Microsoft’s nonprofit offering is built on Dynamics 365 and the Power Platform. The same applies: it is a business platform on which case management can be built, not a case management system you can switch on. The heavy lifting of funded service delivery is development work, not configuration.

A mismatch, not a con

The pattern not-for-profits report runs like this:

• They are drawn in by low entry pricing, generous nonprofit discounts or grants, and heavy “AI everything” marketing.
• They sign up believing the platform will handle case management out of the box, because it is marketed under a nonprofit banner and uses the word “case.”
• Then the real work begins: intake-to-exit workflows, multiple service delivery models, multiple programs and funding sources, government reporting, outcomes measurement and the rest. None of that exists out of the box.
• They are told the functionality has to be built and customised, at significant cost and over a long timeline, usually through a third-party implementation partner. The case management capability they thought they were buying was never actually there.

I doubt this is deliberate.

More often the vendor is selling exactly what it has – a capable CRM – and the buyer reasonably assumes that “case management,” sold under a nonprofit banner, means what it means in their sector. Both sides can be acting in good faith. The word does a lot of quiet work, and the gap only becomes clear once delivery starts. But the outcome is the same regardless of intent: organisations spend large sums building case management from scratch on a CRM foundation, end up with something fragile and expensive to maintain, and within a few years realise they bought the wrong type of product and have to replace it.

Two simple questions cut through the confusion. Ask any vendor:

• Does the product deliver intake-to-exit case management, multiple service and funding models, and my mandated statutory reporting, configured for my programs, out of the box and without custom development?
• Can you show me an existing Australian provider running the same service types and funder reporting on it today?

If the answer is “we can build that for you,” you are not buying a case management system that’s purpose-built for your sector.

Why you need a team that understands NFP case management

A case management system is only as good as the understanding behind it. The sector knowledge is the hard part, not the technology.

If your vendor or implementation team does not already understand how funded service delivery works – intake and consent, episodes of care, light-touch versus intensive support, multi-program clients, the difference between outputs and outcomes, and what DEX, and the many other reporting portals actually require – then you are paying them to learn on your budget. You end up rebuilding the wheel: reconstructing, often badly, capability that purpose-built systems already have, and discovering the gaps only after go-live when the data will not report correctly.

A proper client and case management system (CCMS) is built around the realities of the work from the start. The right partner can map your programs, service models and funder obligations to the system without you having to explain what case management is. That is the difference between a system that fits the sector and a custom build that needs replacing in a few years.

The test is simple: can the vendor talk fluently about your funding bodies and reporting obligations before you explain them? If not, they will be learning the sector on your project, and you will be paying for it twice, once to build the wrong thing and again to replace it.

What to look for in case management software

If you deliver funded services, evaluate against the work, not the marketing:

• Configurable intake-to-exit workflows that match how you actually deliver each program.
• Standardised and custom assessment tools, including the ones your funders mandate.
• Support plans with goals, actions and review cycles.
• Service delivery recording that attaches every contact to the correct program and funding source.
• Multiple service delivery models in one system: individual, family, group, light-touch and intensive.
• Outcomes measurement, not just activity counts.
• Organisation-wide monitoring and evaluation: aggregated reporting on needs, outputs, outcomes and trends across every program.
• Native statutory reporting: DEX with SCORE, PMHC MDS, AODTS NMDS and the relevant state collections.
• Record-once, report-many across multiple funding bodies and jurisdictions.
• Configuration without code, so the system can be shaped to each program rather than each program being forced to fit the system.