How to coordinate an animal-rescue foster network without losing animals in a spreadsheet

Dev is a fictional 34-year-old volunteer dispatcher for a small foster network in Lethbridge, Alberta. Dev has three dogs in care, two foster homes at capacity, and a transport volunteer driving Thursday. A small-dog surrender call landed tonight. One approved backup home has one small-dog space. A printed vet reminder card for Friday at 10:30 is on a fridge. Dev already asked a neighboring group whether it can help.

A spreadsheet, a group chat, and fridge reminder cards do not share Thursday.

A well-meaning volunteer offered to “just take one more.” That home already has a dog listed as reactive with others.

In You.one's Superboard view, Dev can give “Place animals only into homes and a van that can actually hold them, with the printed vet date visible, without placing animals into homes or a van that are already full” a Board of its own. That Board connects community promises, volunteer capacity, local evidence, and human authority; opening “Choose the new surrender call” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Place animals only into homes and a van that can actually hold them, with the printed vet date visible, without placing animals into homes or a van that are already full.

The consequential choice is not something a board or an AI should quietly make: Whether to pause the new intake, use the neighboring group if its requested capacity reply confirms room, or use the approved backup home’s one small-dog space.

You.one can keep the work, evidence, live dependency, and “Choose the new surrender call” decision visible through its Superboard view. The Owner boundary stays explicit: Dev and the network choose placements, talk to homes and clinics, and own animal care.

The Foster week Board gives this mission one durable operating picture. Dev can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Dev's situation: “Choose the new surrender call” is the live choice, “New surrender call: small dog” holds evidence, and “Neighboring-group capacity reply” names something genuinely in motion outside Dev's control. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Intake-capacity brief: Place home capacity, van seats, the Friday 10:30 vet reminder, and pause / confirmed-neighbor / approved-Home-C options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Dev and the network will choose whether the new surrender can be placed this week.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Intake-capacity brief and this Card Room's visible notes and left “Choose the new surrender call” with Dev and the network.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare pausing the new intake, using the neighboring group if its reply confirms capacity, and using approved Home C’s one small-dog space. Do not call anyone or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.

Dev's call remains explicit: Dev and the network choose placements, talk to homes and clinics, and own animal care.

These requests use the visible supported context inside the “Choose the new surrender call” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Dev must provide the relevant facts and check the result.

Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Dev, watch other Lists, or act outside this Card Room.

The network owns animal care, placements, and clinic conversations. Ava does not give veterinary advice, contact homes, or transport animals.

A week that matches homes: the new call is a decision, van seats are counted, and a kind extra is not an overload.

• Request idea: using only the context visible in this Card Room, compare pausing the new intake, using the neighboring group if its reply confirms capacity, and using approved Home C’s one small-dog space. Do not call anyone or choose for me.
• Request idea: use only the Intake-capacity brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
• Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

A spreadsheet plus a group chat is enough when homes and the van have spare room.

It starts to break when a new call, a full home, and Thursday seats all look like yeses.

The Foster week Board earns its place only when the familiar tool—a spreadsheet plus a group chat—can no longer keep the reason, Intake-capacity brief, conversation, current state, decision, and history connected.

Dev should rename every List or Card that feels artificial. This recipe succeeds when “Choose the new surrender call” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, Ava may help this Board notice when animals-in-care exceed home capacity Cards, still leaving every placement with Dev and the network.

A future unified You.one experience could carry relevant context from “Choose the new surrender call” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.

• Dev is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not veterinary, legal, or animal-control advice.
• It does not show Ava contacting homes, clinics, or transporting animals.
• It is not a measured rescue result.