# 12-Week Case Management Plan — Standard Structure (v0.1 DRAFT)

**Status:** DRAFT | **Source:** 05-02 debrief call (Kelly's actual Erin plan + Fabian's redesign mid-call)

---

## Why a fixed 12-week structure

Kelly's Erin plan was already 12 weeks. The structure was sound. What failed: no hardcoded milestone gates, no consequence logic when tasks slipped, no weekly status forcing function. The client refused tasks for 3+ weeks before crisis hit; the plan never escalated.

This template hardcodes those gates so the next case can't drift the same way.

---

## Plan structure

### Phase 0: Outcome definition (week -1, before plan starts)
- **Define the end state** in concrete, measurable terms. Example for Erin: (a) accepted a long-term treatment program; (b) out of the apartment by [date].
- Every case has at most 2-3 ultimate outcomes.
- These are written in the contract; client signs to acknowledge.

### Phase 1: Plan construction (week -1 cont.)
For each outcome:
1. Decompose into milestones (3-6 per outcome).
2. Each milestone has a hard date.
3. Each milestone decomposes into specific tasks (5-15 per milestone).
4. Each task has: owner (client or case manager), due date, evidence-of-completion criterion, **if-not-done consequence**.

### Phase 2: Standard 12-week timeline

| Week | Focus | Standard milestones | Hard gate |
|---|---|---|---|
| 1 | Financial baseline | Identify all debts, income, expenses | If client refuses → engagement paused, family notified |
| 2 | Asset stabilisation | Resolve immediate practical asset (car, lease, etc.) | If asset slips → revised plan or terminate |
| 3-4 | Living situation | Housing plan agreed (stay vs. move vs. inpatient) | Decision required by end of wk 4 |
| 5-8 | Income / treatment | Job search OR treatment program enrollment OR housing search | At least one income/care milestone hit by wk 8 |
| 9-10 | Stability gates | Income or treatment locked in. Family communications normalised. | If neither → escalation to family + Avina exit decision |
| 11-12 | Closeout | Transition to standalone or extended program | Final review with family |

(Adapt template per case; this is the spine, not a rigid protocol.)

### Phase 3: Weekly operating rhythm
- **Monday:** case manager generates one-page status report covering: where we ended last week, what must happen this week, current consequences if missed.
- **Tuesday-Thursday:** scheduled check-ins per plan; every check-in opens with status review.
- **Friday:** end-of-week review — milestones hit / missed; consequence logic activates for missed items.
- **Sunday:** case manager pre-files next week's plan; generates Monday status doc.

### Phase 4: Consequence logic (the part that was missing for Erin)

Every milestone is paired with **explicit, pre-agreed consequences for non-completion**. Examples:

| Missed milestone | Consequence (immediate) | Consequence (sustained) |
|---|---|---|
| Wk 1 financial review | Family notified that intake phase failed | Engagement paused after 7 days |
| Wk 4 housing decision | Apartment-search option removed; family co-sign expires | Inpatient treatment becomes default recommendation |
| Wk 8 income/treatment | Family steps in financially; case manager scope reduced | Engagement re-scoped to crisis-only |
| Failed safety check-in | Welfare check initiated per safety contract | Hospital protocol activated |

Consequences are **automatic, not discretionary**. They're written into the contract. Client cannot debate them in the moment.

### Phase 5: Client-proposed alternatives
If client disagrees with the plan, the standard response is:
> "Show me your alternative with the same level of detail — milestones, dates, consequences. We'll work to your alternative if it has equal rigour."

Client owns their alternative the same way they would have owned the original.

---

## Templates

- `weekly-status-report-template.md` — the Monday one-pager
- `client-intake-checklist.md` — what's required before week 1 starts

---

## Revision log

- v0.1 — 2026-05-02 — Initial structure from debrief-call architecture