A question inside Care Follow-Through, beneath why you see three at a time
Done is a claim. Did it happen is a different question.
A tick is a report from one person about their own past. It is usually honest and it is usually incomplete. Somebody has to ask the other question, and most families never do, because asking it feels like checking up on a relative who is already doing more than their share.
Three separate events sit behind most steps on a care plan. Somebody acts: a call is made, a form is posted, a name is given. An organisation decides: an application is accepted, an assessment is scheduled, a benefit is approved or refused. And something changes at the house: a worker arrives, a rail is fitted, a van turns up on a Thursday.
A tick records the first event. A family reading the tick believes the third has happened. Weeks pass in that gap, and nobody is lying to anybody: the son who rang really did ring, the agency really did say it was in hand, and the parent still has nobody coming on Monday. The question that closes the gap is small and slightly awkward to say out loud. Did it happen.
What a real answer looks like
Most answers to this question are not answers. They soothe. Four properties separate the ones worth recording from the ones that only feel reassuring.
-
A date that came from the organisation, not from the family
They said soon is not a date. They said someone will be in touch is not a date. The useful sentence is the one an employee of the agency said, with a day in it, and the useful follow-up is asking what happens if that day passes. An organisation that will not give a date is telling you something true, and writing that down is a better record than writing down a hope.
-
Something a person can point at
A letter, a reference number, a case worker's name, an appointment on a calendar, a piece of equipment in the hallway. Written proof is not distrust of the person who did the work. It is what lets the next question, six weeks later and to a different member of staff, start from a fact instead of from the beginning again. Every family that has had to re-explain a whole situation to a new employee knows what a reference number is worth.
-
Somebody who was in a position to see it
Distance is the ordinary condition here, not the exception. The person managing the plan is often several hundred miles from the front door, so the confirmation has to come either from a document or from a person who is physically there. A neighbour, a sibling who visits on Sundays, the parent themselves. When neither exists for a particular step, that is worth knowing in advance, because it means the step will have to be written around something that arrives in the post.
-
An answer that could have been no
If the way the question is asked makes no socially impossible, the yes is worth nothing. Are you all set produces yes from almost anyone. Where has the application got to produces information, including the information that it has not moved, which is the answer the plan actually needed.
Nobody wants to be the family member who checks up on the others. That reluctance is not laziness or denial: it is somebody protecting a relationship they need to keep, and it is the single most common reason the question goes unasked. The design response is to make the record ask rather than the relative. A shared plan that shows the date a step was last confirmed puts the awkwardness on a page instead of on a person.
Ask on the day the answer exists
Verification has a right moment, and it is set by the step, not by the week. When a task is written, the same conversation should produce the day by which the result should be visible: the letter should be here by the fourteenth, the first visit should be in the diary by the end of the month. That day is when the question gets asked, and until it arrives the question is noise.
Asking early is not harmless. It produces still waiting, which teaches everybody that the question means nothing, and it spends goodwill with the person who owns the step at exactly the point they can do nothing about it. A plan where every task is chased every Sunday trains a family to stop reading the messages. One check, on a chosen day, with the answer written down where nobody has to ask again, is a different thing entirely.
The three answers, and what each one means next
Yes, with something to point at. The step closes and the artefact goes on the record. If completing this step unblocked another one, that is the moment the next thing starts, not next Sunday.
Yes, but nobody can show it. Not a failure and not a lie. It becomes a step of its own: get the thing in writing. Half the time the writing turns out never to have been sent, and that is discovered now rather than at the point somebody needs to prove eligibility.
Nobody knows. The most useful of the three, and the one a plan usually hides. Not knowing is a state, it belongs on the record with the date it was last asked, and it points at a specific missing thing: a name to call, a person nearby, a document that never arrived. A plan that has stalled is almost always a plan full of unanswered versions of this question.
Where checking cannot reach
This is not a solved problem and it should not be sold as one. Nothing on a screen can see a parent's front door. A confirmed yes goes stale: services stop, staff leave, approvals expire, and a benefit that started in March can quietly end in September with the record still reading done. Some outcomes are genuinely unobservable from outside the house, and a family that only ever asks the person who owns the step will hear that person's honest impression rather than the fact.
So the honest limit is this: asking well converts most invisible failures into visible ones, and it converts none of them into guarantees. The steps that stay unverifiable should be named as unverifiable rather than ticked, because a state model is only as true as the last person who touched it. And the yes that needs re-asking every few months is the signal that a finite plan has run out of road: that is where Family Observatory picks it up, and where follow-through stops.
Related: the six parts of a step, which is where the observable result gets written in, and why a task with no name on it has nobody to ask.
Last reviewed 15 August 2026
The part that does not end
One plan finishes. The question keeps coming back.
A finite plan can be checked and closed. The refills, the redeterminations, the rides and the appointments come round again, and each one needs somebody to know whether it actually happened this time. That is ongoing coordination, and it is what Family Observatory is for.