How to coordinate a volunteer drive without a signup sheet that lies

Tom is a fictional 51-year-old volunteer coordinator for a weekend park cleanup in Thunder Bay, Ontario. Tom posted a signup form. Eighty people said yes. The site can safely use thirty at a time, but tool inventory caps a shift at twenty-four rakes. Sunday is available as an overflow shift under the same cap if Saturday cannot absorb the yeses. Tom already asked a neighboring group to lend six more rakes, and a local radio mention could add more people on Saturday morning.

A form spreadsheet, a tool closet count, and a radio producer’s text do not share a cap.

A group of ten from a workplace asked to come as a team at noon, which is already the peak hour.

In You.one's Superboard view, Tom can give “Run the cleanup weekend with shifts that match tools and a safe headcount, and treat extra publicity as a held option rather than a crowd” a Board of its own. That Board connects community promises, volunteer capacity, local evidence, and human authority; opening “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Run the cleanup weekend with shifts that match tools and a safe headcount, and treat extra publicity as a held option rather than a crowd.

The consequential choice is not something a board or an AI should quietly make: Whether to run Saturday only at twenty-four with radio held, run Saturday and Sunday at twenty-four per shift with radio held, or defer the cap and radio mention until the six borrowed rakes confirm.

You.one can keep the work, evidence, live dependency, and “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” decision visible through its Superboard view. The Owner boundary stays explicit: Tom chooses the cap, talks to teams and the radio producer, and owns site safety.

The Cleanup weekend Board gives this mission one durable operating picture. Tom 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 Tom's situation: “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” is the live choice, “Workplace team of ten at noon” holds evidence, and “Borrowed-tool reply from neighboring group” names something genuinely in motion outside Tom's control. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Capacity brief: Place tool count, the noon workplace team of ten, form yeses, and Saturday-only / Saturday-plus-Sunday / wait-for-six-rakes postures on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Tom will choose the cleanup weekend posture.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Capacity brief and this Card Room's visible notes and left “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” with Tom.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare Saturday-only at twenty-four with radio held, Saturday and Sunday at twenty-four per shift with radio held, and deferring the cap and radio mention until six borrowed rakes confirm. Do not contact the station 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.

Tom's call remains explicit: Tom chooses the cap, talks to teams and the radio producer, and owns site safety.

These requests use the visible supported context inside the “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Tom 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 Tom, watch other Lists, or act outside this Card Room.

Tom owns safety, communications, and who is invited. Ava does not message volunteers or run the site.

A Saturday that matches tools: the cap is chosen, the noon team is placed or waitlisted, and a radio mention is not an unplanned crowd.

• Request idea: using only the context visible in this Card Room, compare Saturday-only at twenty-four with radio held, Saturday and Sunday at twenty-four per shift with radio held, and deferring the cap and radio mention until six borrowed rakes confirm. Do not contact the station or choose for me.
• Request idea: use only the 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 signup spreadsheet is enough when yeses are fewer than tools.

It starts to break when eighty yeses, twenty-four rakes, and a radio maybe all claim Saturday.

The Cleanup weekend Board earns its place only when the familiar tool—a signup spreadsheet—can no longer keep the reason, Capacity brief, conversation, current state, decision, and history connected.

Tom should rename every List or Card that feels artificial. This recipe succeeds when “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” 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 a shift Card has no named lead, still leaving every invite with Tom.

A future unified You.one experience could carry relevant context from “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” 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.

• Tom is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not safety, insurance, or labor advice.
• It does not show Ava contacting volunteers or a radio station.
• It is not a measured turnout result.