Avina.
⚠ SANDBOX · methodology canvas · v2 final · derived from the Erin case
A
AVN-OPS-CVS-001.2 · Methodology canvas

The Avina Methodology, vision to daily reflection.

A repeatable five-layer architecture for case management. Built from the Erin Webb case, 1 May 2026 incident. Designed to be retrofittable to existing clients (Blair) and the operating default for new engagements.

↩ Sandbox index Avina hub →
01 · Architecture

Five layers, each shorter and more concrete
than the layer above.

Each layer answers a different question. Together they form the operating backbone of an engagement. Skip a layer and the engagement runs on improvisation, which is what 1 May exposed.

Vision → Goals → Plan cascade → Consequence → Reflection
01

Vision and Insight

What the family says success looks like twelve months out, plus Avina's professional read of the client's pattern. Set in the first mother-meeting. Reviewed quarterly. Anchors every downstream decision back to a stable horizon when day-to-day events get noisy.

02

Goals

Two or three named outcomes derived from Layer 1. Concrete, measurable, time-bound. Posted where the client and family can see them. Tracked weekly. Closed when met or replaced when superseded.

03

Plan Cascade

Monthly canvas, weekly plan, daily plan, progression narrative. Each layer shorter and more concrete than the one above. The cascade is the operational backbone of any week.

04

Consequence Architecture

Every milestone in the plan cascade has, in writing, the specific consequence that activates if it is missed. Pre-agreed at intake. Triggered automatically. No real-time judgement, no negotiation. The forcing function that prevents slow drift becoming sudden crisis.

05

Daily Reflection Loop

Ten minutes per active client per day. Six questions: what was done versus planned; what was good; what was bad; consequences activated and whether they were enforced; what is next; vision link. Logged. Compounding asset over the life of the engagement.

The methodology was not invented.
It was extracted from one case that didn't have it.

02 · Six learnings

From the Erin case.

Each learning maps to a layer above. They are operational rules, not aspirations. They activate at intake of every new engagement.

Learning 01
Forcing function written and signed before week one. Without a pre-agreed consequence schedule, the engagement runs on case-manager judgement in real time, which the client tests until something breaks. With a forcing function, the structural pressure is on the client's choices, not the case manager's stamina.
Learning 02
Recording consent and storage before week one. California Penal Code section 632 is all-party consent. The engagement contract must explicitly authorise the recording, the storage location, the retention period, and the conditions under which recordings can be referenced or produced. The Erin case made this evidentiary need acutely visible.
Learning 03
Family commits to the consequence schedule, not just to fees. The biggest single failure mode is family agreeing to fees but not to the boundary the engagement is enforcing. When the moment comes the family relaxes the boundary, the case manager's authority collapses.
Learning 04
Daily reflection prevents slow drift becoming sudden crisis. Three weeks of missed milestones with no forcing function is what made the 1 May escalation possible. A ten-minute daily reflection log catches drift inside two missed days, not three weeks.
Learning 05
Case manager wellbeing is operational, not personal. Saturday is the case manager's wellbeing day. No client work, crisis only. This is not optional. A burnt-out case manager makes the kinds of decisions the Erin case showed cannot be made on tired judgement.
Learning 06
Family voice channelled, not bypassed. The position-document workflow gives the family a structured way to set the engagement's direction without bypassing the case manager. Phone calls run on emotion; written positions run on consideration.
03 · How to use this canvas

For the three audiences who will see it.

The canvas exists to be shared. With families considering an engagement, with clinical partners assessing fit, with the case manager herself as a daily reference. Hand it over; it explains itself.

For the family

A walkthrough at intake

Read top to bottom in a single sitting. Each layer is short and concrete enough to discuss together. The consequence layer is where the family commits — not just to paying for the engagement but to enforcing the boundary it will hold.

For clinical partners

A frame for handoff

Hospitalists, residential program intake clinicians, outpatient therapists. Hand them this page and they understand how Avina runs the case-manager seam between clinical care and family. It travels with the engagement.

For the case manager

A daily anchor

When a day goes sideways, the canvas is what to read first. Each layer reasserts the operating discipline. The reflection loop closes the day. The vision panel reopens it tomorrow.