Skip to main content

Case Management

Case management is the coordinated handling of an individual case through ownership, status tracking, records, decisions, staff action, support, escalation, and outcome management.

Reference entry content

Concept facts

Case management is the coordinated handling of an individual case through ownership, status tracking, records, decisions, staff action, support, escalation, and outcome management.

Also known as
Case handling, case coordination, service case workflow, client case management.
Used in
Public service, health services, social services, civic services, complaints handling, support operations, eligibility review, and digital service workflow.
Interpret with
Service handoff, backstage, service ecosystem, case status, workflow, data quality, escalation, and outcome metric.

Plain-language explanation

Case management is how a service handles a person’s issue, application, referral, complaint, request, or support need over time. In UX and service architecture, it also matters in civic complaints, benefits, banking verification, telco fraud recovery, education applications, and development-sector delivery.

Why it matters

Users often need to know what is happening to their case, who is responsible, what evidence is missing, and what comes next. Poor case management creates repeated contact, lost documents, unclear status, inconsistent decisions, and staff rework.

Use contexts

  • applications, complaints, referrals, claims, or support requests
  • eligibility review or verification
  • case ownership by staff or teams
  • status tracking and user updates
  • escalation and exception handling

Application guidance

Define what counts as a case, when it starts and ends, who owns it, what statuses mean, and how records and escalations are maintained. Design user-facing status and staff-facing workflow together.

Practical example

A civic-tech complaint system receives reports of unsafe road damage. Citizens submit complaints online, but cases move manually between departments without visible ownership or escalation. A case-management redesign defines categories, responsible departments, status states, evidence requirements, escalation rules, and citizen notifications. The UX consequence is improved citizen trust, reduced duplicate complaints, clearer staff accountability, and faster response to safety risks.

Interpretive boundaries

Case management is not only a software module or CRM feature and should not be framed as medical-only or social-work-only. It must be adapted to digital and institutional service workflows.

Applied at Userhub

Userhub uses case-management framing to evaluate services where user outcomes depend on staff action, case ownership, status visibility, records, and escalation. In UX Lab work, this supports civic, development-sector, fintech, healthtech, edtech, and support-heavy service improvement.

Sources and references

National Association of Social Workers. (n.d.). NASW Standards for Social Work Case Management. https://www.socialworkers.org/Practice/NASW-Practice-Standards-Guidelines/NASW-Standards-for-Social-Work-Case-Management

Giardino, A. P., & De Jesus, O. (2023). Case management. In StatPearls. StatPearls Publishing. https://www.ncbi.nlm.nih.gov/books/NBK562214/

Government Digital Service. (n.d.). Service Standard. GOV.UK Service Manual. https://www.gov.uk/service-manual/service-standard

Bitner, M. J., Ostrom, A. L., & Morgan, F. N. (2008). Service blueprinting: A practical technique for service innovation. California Management Review, 50(3), 66–94. https://doi.org/10.2307/41166446

Cite this entry

APA

Userhub. (2026). Case Management. UX Reference. https://userhub.com.bd/reference/case-management/