Loading...
operations

Case Closure and Discharge Summary Form

Case Closure and Discharge Summary Form for documenting services delivered, goal progress, closure reason, and the post-discharge plan before a case is formally closed.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Nonprofit · Social Services · Behavioral Health · Community Health

Overview

The Case Closure and Discharge Summary Form is a structured end-of-case record for documenting how a client file is closed, what services were provided, what goals were reached, and what support continues after discharge. It is designed for case managers who need a consistent way to summarize the full service history before a record is archived or transferred.

Use this template when a case is ending because goals were met, the client moved, services were transferred, the client disengaged, or the program is closing the file for another documented reason. The form helps you capture the client and case identifiers, closure reason, service summary, goal attainment, barriers, referrals, safety concerns, and supervisor review in one place. That makes it easier to maintain a clean audit trail and to explain the closure later if the record is reviewed internally.

Do not use this form as a substitute for active case notes or incident reporting. If the case is still open, if immediate safety action is needed, or if the situation requires a separate incident, abuse, or crisis report, those workflows should happen first. The template is also not meant for collecting unnecessary PII; keep fields limited to what the program actually needs and use conditional logic so only relevant discharge details appear. A good closure form should answer three questions clearly: what happened, what support was provided, and what happens next.

What's inside this template

Client and Case Identification

This section anchors the record to the correct person, program, and case timeline so the closure summary can be matched to the source file.

  • Client ID / Case Number (required)

    Enter the unique client or case identifier from your case management system. Do not enter Social Security Numbers or other sensitive identifiers here.

  • Client First Name (required)
  • Client Last Name (required)
  • Program / Service Line (required)

    Select the program under which this case was managed.

  • If 'Other', specify program name
  • Date Case Was Opened (required)
  • Date of Case Closure (required)
  • Case Manager Name (required)
  • Supervising Manager / Reviewer (required)

    Name of the supervisor who will approve this closure.

Reason for Closure

This section explains why the case is ending and preserves the context behind the closure decision.

  • Primary Reason for Case Closure (required)
  • Additional Detail on Closure Reason

    Provide any context that clarifies the closure reason, especially for ‘Lost to Follow-Up’, ‘Administrative’, or ‘Other’ selections.

  • Number of Contact Attempts Before Closure (if applicable)

    Required for ‘Lost to Follow-Up’ closures. Document attempts per your agency’s policy.

Services Delivered

This section shows what support was actually provided so the closure record reflects the work completed before discharge.

  • Services Provided During This Case (required)

    Select all service types delivered to this client.

  • If 'Other' service selected, describe
  • Total Number of Service Contacts / Sessions (required)

    Total documented contacts (in-person, phone, virtual) over the life of the case.

  • Narrative Summary of Services Delivered (required)

    Provide a concise narrative of the key services delivered and the client’s engagement over the course of the case.

Goal Attainment

This section documents progress against case goals and makes it clear which outcomes were achieved, partial, or unmet.

  • Goal Attainment Summary (required)

    List each goal from the service plan and rate its attainment at closure. Add a row for each goal.

  • Overall Goal Attainment Rating (required)

    Select the rating that best reflects the client’s overall progress across all goals.

  • Primary Barriers to Goal Achievement (if applicable)

    Select all barriers that significantly impacted goal attainment.

Post-Discharge Plan and Referrals

This section records what support continues after closure, including referrals, consent, and any safety-related follow-up.

  • Client's Status at Discharge (required)
  • Referrals Made at Discharge

    List each referral made, including the organization name, service type, and date of referral. Leave blank if no referrals were made.

  • Client Provided Informed Consent for Referrals

    Confirm whether the client consented to information sharing with referred providers, per your agency’s consent and data-sharing policy.

  • Were there any unresolved safety concerns at the time of closure? (required)

    If yes, document the steps taken and any mandatory reporting obligations fulfilled.

  • Safety Concern Details and Actions Taken

    Describe the safety concern, actions taken, and any mandatory reporting completed. Do not include information that would re-identify third parties unnecessarily.

  • Post-Discharge Plan Narrative (required)

    Summarize the plan for the client after closure, including any self-sufficiency steps, ongoing supports, or follow-up scheduled.

Case Manager Attestation and Supervisor Review

This section confirms the record is complete, accurate, and reviewed according to the program’s closure workflow.

  • Case Record Completeness (required)

    Confirm that the case record is complete before submitting for closure.

  • Accuracy Attestation (required)
  • Case Manager Signature (required)

    Electronic signature of the case manager submitting this closure.

  • Date of Submission (required)
  • Supervisor Review Notes (completed by reviewer)

    Supervisor may add notes, corrections, or conditions for approval here prior to signing off.

  • Supervisor Closure Decision

    To be completed by the approving supervisor.

How to use this template

  1. Enter the client and case identification details, including program name, case dates, and the case manager responsible for the file.
  2. Select the closure reason and add a short detail that explains the specific circumstances, including outreach or contact attempts when the client was hard to reach.
  3. List the services provided, note any other services in the free-text detail field, and summarize the total service contacts in a way that matches the case record.
  4. Complete the goals table by marking each goal’s status, then record the overall goal attainment and the barriers that affected progress or closure.
  5. Document the post-discharge status, referrals made, client consent to referral, and any safety concerns, then write a clear plan narrative for what happens after discharge.
  6. Review the attestation section, confirm the record is complete and accurate, obtain supervisor review if required, and submit the form for final closure.

Best practices

  • Use a date picker for case_open_date and case_close_date so the closure timeline is accurate and easy to audit.
  • Keep closure_reason specific and pair it with closure_reason_detail when the label alone does not explain the case ending.
  • Record contact_attempts only when they are relevant to the closure path, and summarize the method and outcome instead of writing a vague count.
  • Use progressive disclosure for referrals, safety concerns, and consent so staff only see the fields that apply to the closure scenario.
  • Match services_provided to the actual service taxonomy used by the program, and use services_other_detail only when the service is truly outside the list.
  • Document goal attainment in plain language that ties each goal to a measurable outcome, not just a subjective impression.
  • If safety_concerns_at_closure is flagged, write the next-step actions clearly and do not bury them inside the general discharge narrative.
  • Keep the form focused on necessary data only, especially when client information will be stored in a shared record system.

What this template typically catches

Issues teams running this template most often surface in practice:

The closure reason is too generic, such as 'completed' or 'ended,' which makes the record hard to interpret later.
Contact attempts are missing when the client was unreachable, leaving the closure path unsupported.
The service summary does not match the listed services provided, creating a gap between the structured fields and the narrative.
Goal attainment is marked without describing barriers, so it is unclear why some goals were not fully reached.
Referrals are listed without documenting client consent to referral when consent was required.
Safety concerns are mentioned in the narrative but not flagged in the dedicated safety section, which can hide follow-up needs.
The supervisor review section is left blank even when the workflow requires approval before record finalization.

Common use cases

Housing Case Manager Closure
A housing navigator closes a file after the client secures stable housing and no longer needs active support. The form captures the services delivered, remaining barriers, and any referral to ongoing community resources.
Family Support Program Discharge
A family services worker documents closure after parenting goals are met and scheduled check-ins end. The summary shows which goals were achieved and what follow-up resources were offered.
Behavioral Health Transition Summary
A clinician or case manager closes a supportive services case when the client transitions to another provider. The form records consent for referral, safety concerns at discharge, and the handoff plan.
Reentry Program Case End
A reentry coordinator closes a case after the participant completes the program or moves out of service area. The record explains outreach attempts, services delivered, and the discharge status at exit.

Frequently asked questions

What is this form used for?

This form is used to formally close a client case and create a clear end-of-service record. It captures who the client was, what services were delivered, what goals were achieved, why the case is ending, and what happens after discharge. It is especially useful when multiple staff touch the case and you need one final summary for the file.

Who should complete the case closure summary?

The case manager usually completes the form, because they know the service history, contact attempts, and discharge plan. A supervisor may review it before the record is finalized, especially when the closure involves safety concerns, incomplete goals, or referral follow-up. If your workflow uses co-signature or approval, this template supports that handoff.

When should this form be filled out?

Complete it at the point of closure, after the final service contact or when the team has determined the case should end. It should not be left until weeks later, because details like contact attempts, barriers, and referral status are easiest to document while the case is still fresh. If the client disengages, document the closure reason and outreach attempts as soon as the decision is made.

What kinds of closure reasons does it cover?

The template supports common closure paths such as goals met, client moved, client withdrew, services transferred, unable to locate, or administrative closure. It also includes a detail field so you can explain the specific context instead of relying on a generic label. That helps the record reflect what actually happened and reduces ambiguity during audits or internal review.

How does this template handle referrals and consent?

The post-discharge section includes referrals made, client consent to referral, and a narrative for the discharge plan. That makes it easier to document whether the client agreed to share information with another provider or program. If you are collecting any PII for referral purposes, keep the fields limited to what is necessary and note the consent basis clearly.

Can this be customized for different programs?

Yes. The structure already includes a program name field and an 'other' option for program-specific labeling, so you can adapt it for housing, family support, reentry, behavioral health, or general case management. You can also tailor the goals table, service list, and referral options to match your program’s workflow without changing the overall closure logic.

What are the most common mistakes when using this form?

Common mistakes include leaving the closure reason too vague, skipping contact attempts when the client is unreachable, and writing a discharge plan that does not match the referrals actually made. Another frequent issue is marking every field required, which can block completion when some details are legitimately unknown. The best records are specific, concise, and consistent with the case timeline.

How does this compare with closing a case informally in notes?

Informal notes can explain the end of a case, but they often leave gaps in the final record and make supervisor review harder. This template gives you a structured closure summary with clear fields for services, goals, barriers, referrals, and attestation. That makes the record easier to read later and reduces the chance that important discharge details are missed.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Case Closure and Discharge Summary Form with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?