Skip to content
You.one

Join the You.one waitlist

Example

How to propose a riverfront-cleanup posture when rain and sharps exceed volunteer authority

A large turnout does not widen volunteer authority. Olivier must propose one event posture without sending thirty-six untrained people toward unstable shoreline or hazards they may only report.

You.one · Superboard viewRiverfront access zones

Propose one event posture with safe access limits and a report path for hazards volunteers must not handle

Safe-use promise2

Purpose, boundaries, and the definition of enough

No bag count is worth sending an untrained volunteer toward sharps or onto unstable shoreline

Hold the mission and boundary: propose one event posture with safe access limits and a report path for hazards volunteers must not handle

Sharps are report-only for this event

State the non-negotiable handling limit

Zone actions3

The decision and preparation that deserve attention next

Propose cancel, upland-only, or split zones if conditions allow

Hold the live choice—whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow—so Olivier can decide from the evidence in this Room

Draft the zone briefing

Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed

Mark general and trained boundaries on the hazard map against city handling limits

Use the result of the first owned action to update the Access-scope brief; record the finding, not merely the effort

Site evidence6

The visible proof behind the plan—not a vague feeling of readiness

Shoreline hazard map

Keep the shoreline hazard map beside the four trained volunteers so rain cannot slide thirty-six untrained people into a report-only zone

Registered headcount: forty

Keep total turnout beside the restricted shoreline

Confirmed shoreline-trained volunteers: four

Ground the split-zones option in actual trained capacity

Rain and footing observations for the shoreline section

Record the dated condition evidence that can rule out the split-zones posture

General volunteers are not sharps trained

Keep the volunteer boundary visible

Shoreline section requires trained access

Separate the specialized zone from general cleanup

City reply already requested1

External answers that matter but should not occupy the active-work List

City sharps-disposal reply

Record who owns the answer, what was asked, and that city sharps-disposal reply is still unconfirmed

An illustrative Board built from this fictional scenario. Adapt the Lists and Cards to your own mission.
Structured Board artifact for Olivier’s riverfront cleanup: forty registrants, four shoreline-trained volunteers, rain and footing evidence, report-only sharps, city collection reply, and three event postures.
The access picture keeps turnout separate from training and municipal hazard authority; event leadership, trained professionals, and the city retain real safety, cancellation, access, and collection decisions.
01

In You.one’s Superboard view, the Riverfront access zones Board separates the safe-use promise, zone actions, dated site evidence, the city reply already requested, and hazards only qualified authorities have cleared or collected.

02

Open Cancel, upland-only, or conditional split zones as the consequential Card Room. Start by marking general and trained boundaries on the hazard map against the city’s handling limits.

03

After an explicit request, Ava can compare visible conditions and capacity only. Ava cannot cancel the event, contact the city, interpret weather or hazardous-material rules, handle hazards, or choose; event leadership, trained people, and the city retain authority.

Riverfront access zones has one live choice: Propose cancel, upland-only, or split zones if conditions allow

The mission is specific: Propose one event posture with safe access limits and a report path for hazards volunteers must not handle.

The consequential choice is not something a board or an AI should quietly make: Whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow.

You.one can keep the work, evidence, anything already waiting on another person or event, and the “Propose cancel, upland-only, or split zones if conditions allow” decision visible through its Superboard view. Olivier still owns the call: Olivier can propose canceling the event, an upland-only event, or split zones if conditions allow. Event leadership owns the event decision, the city owns sharps collection, untrained volunteers may not handle sharps, and Ava cannot contact the city or handle hazards.

Available today

Riverfront access zones: the working map

The Riverfront access zones Board gives this mission one durable operating picture. Olivier can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.

The Lists separate what Olivier can move now, what is evidence, what is already waiting on a named person or event, and what still needs a decision.

Swipe or scroll sideways to see every column.

Riverfront access zones Board shape
ListWhat belongs here
Safe-use promisePurpose, boundaries, and the definition of enough
Zone actionsThe decision and preparation that deserve attention next
Site evidenceThe visible proof behind the plan—not a vague feeling of readiness
City reply already requestedExternal answers that matter but should not occupy the active-work List

Available today

Open one decision: Propose cancel, upland-only, or split zones if conditions allow

Opening the Card gives the visible item durable depth. Stage can hold Access-scope brief: Place rain conditions, trained access, volunteer mix, sharps, and city disposal authority together. Live choice: Whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Olivier will decide whether to propose canceling the event, an upland-only event with the shoreline closed, or split zones for four trained and thirty-six general volunteers if conditions allow.”

A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Propose cancel, upland-only, or split zones if conditions allow” from the visible evidence. Ava can work from the context Olivier deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.

Olivier's call remains explicit: Olivier can propose canceling the event, an upland-only event, or split zones if conditions allow. Event leadership owns the event decision, the city owns sharps collection, untrained volunteers may not handle sharps, and Ava cannot contact the city or handle hazards.

Swipe or scroll sideways to see every column.

Inside the Propose cancel, upland-only, or split zones if conditions allow Room
SurfaceJob in this example
StageAccess-scope brief: Place rain conditions, trained access, volunteer mix, sharps, and city disposal authority together. Live choice: Whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow
ChatKeep Olivier's request and Ava's attributed response with the work
PulseOpen decision: Olivier will decide whether to propose canceling the event, an upland-only event with the shoreline closed, or split zones for four trained and thirty-six general volunteers if conditions allow

Useful Ava requests, with the boundary intact

These requests stay with the facts Olivier has made visible around “Propose cancel, upland-only, or split zones if conditions allow.” Olivier supplies the evidence, checks Ava's work, and decides what belongs in the Room.

Current Ava can prepare help after an explicit request. She cannot make the choice, represent Olivier, watch other work on her own, or contact anyone.

Olivier can propose canceling the event, an upland-only event, or split zones if conditions allow. Event leadership owns the event decision, the city owns sharps collection, untrained volunteers may not handle sharps, and Ava cannot contact the city or handle hazards.

Olivier finishes “Mark general and trained boundaries on the hazard map against city handling limits,” keeps “Shoreline hazard map” beside “Propose cancel, upland-only, or split zones if conditions allow,” and does not treat “City sharps-disposal reply” as resolved before the outside answer arrives.

  • Request idea: using only the context visible in this Card Room, compare proposing event cancellation, an upland-only event with the shoreline closed, and split zones for four trained and thirty-six general volunteers if conditions allow. Cite only notes visible in this Room. Do not cancel the event, contact the city, handle hazards, or choose the posture for me.
  • Request idea: use only the Access-scope brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
  • Request idea: in “Propose cancel, upland-only, or split zones if conditions allow,” show which visible fact could reverse the current choice

The limit of a shoreline site map

A shoreline site map can be enough while the situation stays simple: sharps reporting and trained shoreline access are already set for the current weather.

It starts to break when “Shoreline hazard map” and “City sharps-disposal reply” must inform the same choice.

The Riverfront access zones Board earns its place only when the familiar tool—a shoreline site map—can no longer keep the reason, Access-scope brief, conversation, current state, decision, and history connected.

A practical way to start the Riverfront access zones Board

Olivier should rename every List or Card that feels artificial. This recipe succeeds when “Propose cancel, upland-only, or split zones if conditions allow” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Swipe or scroll sideways to see every column.

Start with the Riverfront access zones Board
StepAction
1. Write the missionPropose one event posture with safe access limits and a report path for hazards volunteers must not handle
2. Open the live choicePut “Propose cancel, upland-only, or split zones if conditions allow” in a Room of its own
3. Attach the evidenceAccess-scope brief: Place rain conditions, trained access, volunteer mix, sharps, and city disposal authority together. Live choice: Whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow.
4. Name what is already waitingKeep “City sharps-disposal reply” visibly waiting
5. Take the first owned actionMark general and trained boundaries on the hazard map against city handling limits

Where this example stops

  • This is a fictional example, not a customer story.
  • This fictional example is not environmental, medical, hazardous-material, weather, or municipal safety advice; event leadership, trained professionals, and the city own real decisions and hazard handling.
  • It does not show Ava completing external actions or contacting anyone for Olivier.
  • It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.

Draw the authority boundary before turnout pressure redraws the shoreline zone.

See how Superboard works