When nobody says yes

Consent-based assignment is the right design, and it turns a scheduling problem into a social one. Software is good at the first and has almost no power over the second. What follows is where that breaks, written down here rather than discovered later.

Four ways asking fails

1. 1
   Silence is not a decision, and it cannot be read

   A person who has not seen the ask and a person who has seen it and is hoping somebody else takes it look identical in the data. Any system that guesses between them will be wrong about half the time and confident every time, and the wrong guess is the expensive one: it marks a willing person as unreliable. The only honest handling is to treat silence as unanswered, say so, and put a clock on it.

2. 2
   A pool of one makes the question dishonest

   When exactly one person can realistically do a thing, an ask is a demand with a question mark on the end. Worse, a decline does not remove the obligation, it just returns the task to the pool it came from, so the person who is already carrying the most gets asked the most often. That is the coordination load the whole approach claims to spread, arriving through the mechanism meant to spread it.

3. 3
   A no costs more than silence

   Inside a family, declining is never only about Thursday. It is read as a statement about how much you care, in front of the siblings who will remember it. Given that, going quiet is the rational move: it is cheaper than a no. So the design has to make declining the cheapest possible action, never show anybody a tally of what they turned down, and never phrase a reminder in a way that a tired person could read as being chased.

4. 4
   Nothing escalates, because nothing has authority

   There is no manager here. When an ask expires, the system has exactly three moves: widen it to more people, make the obligation smaller, or say out loud that nobody accepted. It cannot compel a person, and a product that pretends otherwise is only sending guilt on a timer to people who did not do anything wrong.

What happens instead of pretending

Unowned is a real state, and it is shown. A task nobody accepted is not silently attached to whoever booked the appointment, which is the default every family falls into and the reason one person ends up doing everything. It sits there unowned and visible, and the plan summary counts it as open.

The failure no software fixes

Sometimes the pool really is one person, or nobody. A daughter three hundred miles away, an only child, a spouse who cannot drive at night. No amount of asking creates a second adult, and any tool that keeps re-asking in that situation is just measuring a person's exhaustion back at them.

When that is the honest reading, the problem is not the ask, it is the plan. The step needs to change rather than change hands: paid transport, a medical transport benefit, a volunteer driver program run locally, or a different appointment time. Whether any of those apply to a specific person is decided by the agency or provider that runs them, and never here.

It is worth being blunt about what this leaves. A coordination system will measure a household where one person does everything, and it will not change it. Measuring it is not nothing: an invisible load cannot be discussed and a visible one can. But nobody should buy this expecting it to produce a second driver, and this page exists so that expectation is set before Thursday rather than after.

What to do tonight

• Shrink the obligation before re-asking. A lift one way is a different question from a lift both ways, and it is one many more people can say yes to.
• Ask one named person, directly. A message to a group is addressed to nobody, and everybody in it knows that.
• Put the deadline and the fallback in the ask itself. Knowing what happens if everyone says no is what makes saying no possible.
• Treat a no as a finished answer. A person who declined and was left alone will consider the next ask. A person who declined and got a follow-up will not.

Last reviewed 14 August 2026