Care follow-through
Four programs. Six appointments. One person doing all of it.
Somebody has to make the calls, chase the paperwork, be there on Thursday and still get dinner on the table. It is almost always the same person, and nobody ever decided it would be.
or have the thinking sent to you
That is us set.
We will only email when there is something worth reading. The ongoing side of this is at Family Observatory.
One week, one family
Six of the eight things this week land on Dana. Not because anyone said no. Because nobody was asked, and an unasked task defaults to whoever booked the appointment.
Most assistance systems stop at discovery
They are built to answer one question: what exists. That is a real question and worth answering well. But a household that receives a list of twelve programs and contacts none of them has received nothing, and the reason is almost never that they did not care enough.
It is that the week happened. One application needed a document nobody could find. One needed a signature from a man who is not certain he wants to sign it. One office answers the phone between nine and eleven on weekdays, which is exactly when the daughter handling it is at work. A sister said she would call and genuinely meant it.
The gap between what a household is entitled to and what it receives is mostly made of unfinished admin, not missing information. Which means better search does not close it. Somebody has to do the work, and something has to keep track of who.
What follow-through actually does
It takes each item from a plan and converts it into something a tired person can do on a Tuesday. That conversion is the whole mechanism, and the difference is not tone:
A finding
Apply for in-home supportive services.
A task
Call the county office to start an application. About 20 minutes. Have ready: proof of address, and the Medicaid number if there is one. Owner: Dana.
A task names who to contact, roughly how long it takes, and what to have ready. Anything vaguer is a reminder, and reminders do not get done.
How the logic works
From a finding to a task, in order, with an owner. The five steps the mechanism runs, and the rules it holds itself to.
Read the mechanism
Who does what
The appointment is booked. Now: who drives, who picks up dinner, and who cannot because their Thursday is already gone.
Read the assignment logic
Why plans stall
Five specific ways a plan stops moving, and which of them a system can actually do something about.
Read the stall points
It finishes, and then it stops
Follow-through covers one plan. When the applications are in and the answers are back, it is over. That limit is deliberate and it is enforced in the design rather than promised in the copy: a plan is created with an end date, and there is no way to add a task by hand to keep it alive.
What does not stop is everything else. The appointments keep coming. Someone still has to drive on Thursday, and someone still has to know that Marcus cannot this week. That is a permanent job rather than a finite one, and treating it as an extension of follow-through would be a promise nobody could keep.
Last reviewed 29 July 2026
The part that does not end
One plan finishes. The driving, the meals and the appointments do not.
Follow-through closes out a single plan and then stops, on purpose. The ongoing work of a family sharing care is a different job: who is taking him on Thursday, who is picking up dinner, who is quietly doing all of it. That is what Family Observatory is for.
Get what we learn
We are writing down how care follow-through actually works, in public, as we build it. Leave an email and we will send the useful parts. No sequence, no drip, and you can stop it in one click.
That is us set.
We will only email when we have something worth reading. In the meantime, the ongoing side of this is at Family Observatory.