Level of Care Transition Documentation
Document a level-of-care reassessment, ASAM criteria review, and transition decision in one clinical form. Use it to justify continued service, transfer, or discharge with a clear audit trail.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Behavioral Health · Substance Use Treatment · Addiction Medicine · Community Health Clinics
Overview
Level of Care Transition Documentation is a clinical form for recording why a patient should remain in, move to, or leave a current treatment level. It brings together the reassessment, ASAM dimension review, transition decision, and follow-up plan so the chart shows both the clinical picture and the reasoning behind the change.
Use this template when the patient’s risk, functioning, substance use status, or treatment response has changed enough to require a formal level-of-care decision. It is useful for continued service reviews, step-up or step-down transitions, and discharge planning where the receiving team needs a concise handoff. The form also helps when a payer, supervisor, or utilization reviewer needs to see the rationale in one place.
Do not use it as a routine daily progress note or for cases where no transition decision is being considered. It is also not the right tool if your organization needs a separate consent form, referral packet, or discharge summary with different legal requirements. The template works best when the clinician can document specific findings, note any barriers to transition, and record what the patient was told and agreed to next.
Standards & compliance context
- The form supports minimum-necessary documentation by collecting only the clinical details needed to justify the transition decision.
- If patient-identifying information is collected, the template should include clear disclosure language and role-based access controls for the resulting record.
- The patient_notified and consent_discussion fields help support informed communication and a defensible audit trail for care transitions.
- If your workflow spans multiple providers, preserve the clinician_signature and submission_note fields to show who made the decision and when.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Patient and Encounter Details
This section anchors the review to the correct patient, date, current setting, and reassessment type so the transition decision is traceable.
-
Patient Identifier
Use the internal patient ID or medical record number. Do not enter SSN.
- Encounter Date
- Current Level of Care
- Reassessment Type
Clinical Reassessment
This section captures the current clinical picture and the change since the last review, which is the basis for any level-of-care decision.
-
Current Clinical Concerns
Summarize the symptoms, risks, or functional concerns relevant to the level of care decision.
- Current Risk Level
- Substance Use Status
- Functional Status
-
Summary of Clinical Change Since Last Review
Describe what has changed since the last assessment, including improvement, deterioration, or new concerns.
ASAM Criteria Review
This section organizes the six ASAM dimensions so the rationale for continued service or transfer is explicit and reviewable.
- ASAM Dimension 1: Acute Intoxication and/or Withdrawal Potential
- ASAM Dimension 2: Biomedical Conditions and Complications
- ASAM Dimension 3: Emotional, Behavioral, or Cognitive Conditions
- ASAM Dimension 4: Readiness to Change
- ASAM Dimension 5: Relapse, Continued Use, or Continued Problem Potential
- ASAM Dimension 6: Recovery/Living Environment
- Are continued service criteria met at the current level of care?
- Are transfer criteria met for a different level of care?
Transition Decision and Rationale
This section records the actual decision, the reasoning behind it, and any barriers that affect timing or destination.
- Transition Decision
-
Clinical Rationale
Explain the rationale for the decision, including ASAM criteria, risks, supports, and treatment response.
- Barriers or Risks Considered
- Planned Receiving Level of Care or Program
Plan, Consent, and Attestation
This section shows what happens next, whether the patient was informed, and who is attesting to the completed documentation.
-
Next Steps
List referrals, follow-up timing, safety planning, handoff actions, and any required monitoring.
-
Patient Notified of Transition Plan
Confirm whether the patient was informed of the decision and plan.
-
Consent and Disclosure Notes
Document any consent, privacy disclosures, or information-sharing limitations relevant to the transition.
- Clinician Name
- Clinician Signature
- What happens after I submit
How to use this template
- 1. Enter the patient identifier, encounter date, current level of care, and reassessment type so the record clearly shows which transition review is being documented.
- 2. Summarize the presenting concerns, current risk level, substance use status, functional status, and the clinical change since the last review using specific, observable details.
- 3. Complete each ASAM dimension field and mark whether continued service criteria or transfer criteria are met based on the reassessment findings.
- 4. Select the transition decision, explain the rationale, and document any barriers that affect timing, destination, or readiness for transfer.
- 5. Record the next steps, note whether the patient was notified, capture the consent discussion if applicable, and finish with the clinician name, signature, and submission note.
Best practices
- Use conditional logic so only the fields relevant to the current transition scenario are shown.
- Document the clinical change summary in plain language that ties directly to the ASAM review and decision.
- Mark required versus optional fields clearly so the form does not force unnecessary PII collection.
- Use a date picker for the encounter date and structured fields for level of care and transition decision.
- State what happens after submission so the clinician knows whether the note routes to review, referral, or the chart.
- Capture patient notification and consent discussion separately so the record shows both communication and agreement.
- Keep the rationale specific to this encounter and avoid copying generic phrases from prior notes.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template is used to document a clinical reassessment when a patient may need a different level of care. It captures the current status, ASAM dimension review, the transition decision, and the rationale behind that decision. It is designed to support continuity of care and create a clear record for the chart.
When should a level of care transition be documented?
Use it whenever the patient’s needs change enough that continued service, step-up, step-down, or discharge should be considered. It is especially useful after a change in risk, function, substance use status, or treatment response. It should not replace routine progress notes when no transition decision is being made.
Who should complete this form?
A licensed clinician or other authorized care team member should complete it, depending on your organization’s policy and scope of practice rules. The clinician making the transition recommendation should be the person documenting the rationale and attesting to the decision. If your workflow requires review or co-signature, this form can support that process.
Does this template support ASAM-based documentation?
Yes. The ASAM section is structured to capture the six dimensions, continued service criteria, and transfer criteria in a way that supports clinical reasoning. It helps the reviewer connect the reassessment findings to the level-of-care decision instead of leaving the rationale implicit.
What are the most common mistakes when using this form?
Common mistakes include writing vague rationale, leaving ASAM dimensions blank, and documenting a transition decision without showing the clinical change that led to it. Another frequent issue is failing to note whether the patient was notified or whether consent was discussed. The form works best when each field is completed with specific, observable information.
Can this template be customized for different programs?
Yes. You can tailor the reassessment type, transfer destinations, and next-step fields to match detox, residential, outpatient, or step-down workflows. You can also add conditional logic so only the fields relevant to the current level of care appear. Keep the core decision fields intact so the documentation remains consistent.
How does this compare with ad hoc chart notes?
Ad hoc notes often miss one or more elements needed to explain why a patient stayed, moved, or discharged. This template gives you a repeatable structure for the reassessment, the ASAM review, and the transition rationale. That makes the record easier to review, audit, and hand off to the next provider.
What should happen after the form is submitted?
After submission, the note should be routed into the patient record and reviewed according to your workflow. The next steps section should make it clear what happens next, such as referral, scheduling, handoff, or follow-up monitoring. If your process requires it, the submission should also create an audit trail for the transition decision.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Learn how AI-driven workflows close compliance gaps in hiring, field inspections, and compensation — before they become audit findings.
-
Spring '26 adds real-time Google & Outlook calendar sync, Google Workspace file creation in Files, upgraded Messenger, and expanded mobile parity.
-
Learn how nonprofit tracking of KPIs, donations, and operational workflows reduces turnover and improves decision-making with the right knowledge management...
-
Compare the best employee apps of 2026—MangoApps, Blink, WorkJam, Flip, and more—to find the right fit for your frontline workforce.
Ready to use this template?
Get started with MangoApps and use Level of Care Transition Documentation with your team — pricing built for small business.
