The assignment problem
Who does what
The hard part of care is rarely the decision. It is that a decision creates five small obligations, and every one of them lands on a real person with a job, a commute and a Thursday that is already spoken for.
A Tuesday
The neurology appointment is confirmed for Thursday at 2pm. It took six weeks to get and it cannot move.
It is a forty minute drive each way. He does not drive any more. Somebody has to take him, somebody has to bring him back, and the appointment will run past the point where anyone was going to think about dinner. Dana is the one who booked it, so Dana is quietly assumed to be handling all of it, including the part nobody has said out loud.
Marcus would take the drive. Marcus is in a client meeting from one until four and has not mentioned it, because nobody asked and it did not occur to him that Thursday was the day.
That is the entire problem, and notice what it is not. Nobody lacked information about the appointment. Nobody was unwilling. The plan was fine. What was missing was a shared answer to four questions that a family will not ask each other directly, because asking them sounds like keeping score.
The four questions
-
1
What did this actually create?
One appointment is not one obligation. It is a drive out, a drive back, roughly four hours of somebody's day, and a meal that nobody is now going to cook. Until those are named separately they cannot be shared, and an unnamed obligation defaults to whoever booked it.
-
2
Who could plausibly do each piece?
Not who ought to. Who is genuinely able, given where they live, what they can lift, whether they drive, and what they have already taken on this month. Ability and willingness are different questions from availability, and they change slowly rather than weekly.
-
3
Who is actually free, without anybody having to explain themselves?
Marcus is not free on Thursday afternoon. That is all anyone needs to know. Not the client, not the account, not whether it could be moved if the family leaned on him. The moment being available means disclosing your week to your siblings, people stop connecting anything.
-
4
Did somebody actually say yes?
The gap between assumed and accepted is where almost everything is lost. A name appearing next to a task because an algorithm thought it fit is not ownership. It is a message somebody is going to read at 11pm and resent.
Knowing who is free without reading anyone's calendar
This is the part most family scheduling gets wrong, and it is worth being precise about, because the wrong version of it is invasive enough that adults simply stop participating.
The wrong version connects everyone's calendar and shows the family what is in it. Now a son's job interview, a daughter's therapy appointment and somebody's divorce lawyer are all visible to their siblings, in a product they joined to help with their father.
What is stored
Thursday, 1pm to 4pm, not available. Reported an hour ago.
What is never stored
The title. The location. Who else is on it. Whether it could move. Why.
A window is open or it is closed. That is the whole record. Built this way, the system can answer who is free on Thursday afternoon with confidence and can never answer what anybody was doing, because it does not have that and there is no column it could be written into.
There is a third state that matters as much as the first two: we do not know yet. Somebody who has not connected anything, or whose information is a fortnight stale, is not the same as somebody who is busy, and must never be shown as though they were. Silence is not a no. Treating it as one is how a brother who was perfectly willing ends up looking like the one who never helps.
Asking is the mechanism, not assigning. The system works out that Marcus and two others could take the Thursday drive, sees that Marcus cannot, and asks the other two. One of them accepts, and only then does the work belong to anyone. Nothing is ever placed on a person who has not said yes to it.
And then dinner
Dinner is the honest test of whether a coordination system is real, because dinner is beneath the notice of every product built for this. It is not clinical. It has no provider, no benefit code and no appointment. It is just the thing that has to happen at six o'clock whether or not the day went to plan, and it lands, silently, on whoever is already carrying the most.
The same four questions apply and they resolve faster: this is a small obligation, more people can do it, and somebody who cannot drive forty minutes can absolutely order food to a house. Spreading the small pieces is usually what makes the large ones survivable.
Why this is not follow-through
Everything on this page is real, and none of it is what this property does.
Care follow-through takes the tasks from one plan and tracks them until they are resolved, and then it is over. It has no calendar, no availability and no scheduling anywhere in it, and those absences are deliberate: they are what stops a finite piece of work quietly becoming a permanent one.
But Thursday is not finite. There is another appointment in three weeks, the transport will need arranging again, and someone still has to know that Marcus cannot do afternoons. That is a permanent, repeating job with no end state, because the need has no end state. It needs a product that is honest about being permanent.
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.