Example
How to launch a nonprofit program without losing volunteers, dates, or the actual service
Denise has six enrolled children who can walk, two trained volunteers with a Monday gap, background checks still processing, and a room promise that is not yet usable key hours. The Board has to protect people, not the flyer.
Open homework hour only when the room, two covered adults, and a way home are actually true—or narrow Monday to walkers-only on purpose
Service promise and the no-flyer-as-ops rule
Keep Monday beside the two-adult rule
Adults, checks, and who is actually trained
Count who can actually cover Monday rather than everyone trained in general
Room and hours
Keep the unsent access request as work Denise still controls
Keep the promised room and Monday hours visible while Denise still owns sending the key-access request
Sign-up, flyers, and getting home
Compare keep-Monday, delay-a-week, and smaller-walking-group options
Treat public copy as a constraint that can still be changed on purpose
Ground the walkers-only option in the families who can actually use it
Submitted checks still processing and the requested school-busing reply
Keep submitted but incomplete checks from counting as coverage
Keep Denise's sent request from counting as a confirmed way home

The Homework hour launch Board keeps staffing, room access, family logistics, and replies already requested in one operational picture.
Open Choose Monday, delay, or walkers-only as a Room so every path includes the adults, keys, and way home it requires.
Ava can compare supplied facts. Denise owns safeguarding, staffing, school and family communication, and the launch call; Ava does not contact anyone or run checks.
A flyer is not a launch if coverage and a room are still maybes
The mission is specific: Open homework hour only when the room, two covered adults, and a way home are actually true—or narrow Monday to walkers-only on purpose.
The consequential choice is not something a board or an AI should quietly make: Whether to keep Monday only if key hours, two-adult coverage, and busing confirm, delay a week for keys, checks, and busing, or open walkers-only if keys and two adults confirm.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose Monday, delay, or walkers-only” decision visible through its Superboard view. Denise still owns the call: Denise chooses the date, talks to volunteers and the school, and owns safety and communications.
Available today
Homework hour launch: the working map
The Homework hour launch Board gives this mission one durable operating picture. Denise 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.
The Lists separate what Denise 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.
| List | What belongs here |
|---|---|
| Mission | Service promise and the no-flyer-as-ops rule |
| Coverage | Adults, checks, and who is actually trained |
| Place and time | Room and hours |
| Families | Sign-up, flyers, and getting home |
| Replies already requested | Submitted checks still processing and the requested school-busing reply |
Available today
Open one decision: Choose Monday, delay, or walkers-only
Opening the Card gives the visible item durable depth. Stage can hold Launch-path brief: Place Monday coverage, submitted background checks still processing, the unsent key-access request, the requested busing reply, and keep / delay / walkers-only options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Denise will choose whether Monday is honest.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose Monday, delay, or walkers-only” from the visible evidence. Ava can work from the context Denise deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Denise's call remains explicit: Denise chooses the date, talks to volunteers and the school, and owns safety and communications.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Launch-path brief: Place Monday coverage, submitted background checks still processing, the unsent key-access request, the requested busing reply, and keep / delay / walkers-only options on one page |
| Chat | Keep Denise's request and Ava's attributed response with the work |
| Pulse | Open decision: Denise will choose whether Monday is honest |
Useful Ava requests, with the boundary intact
These requests stay with the facts Denise has made visible around “Choose Monday, delay, or walkers-only.” Denise 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 Denise, watch other work on her own, or contact anyone.
Denise owns safety, staffing, and public messages. Ava does not contact families, run checks, or open the program.
A launch date that matches coverage: trained adults are counted, the flyer is a decision, and a promised room has a key job.
- Request idea: using only the context visible in this Card Room, compare keeping Monday, delaying a week, and opening for walkers only. Do not contact the school or choose for me.
- Request idea: use only the Launch-path brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Choose Monday, delay, or walkers-only,” show which visible fact could reverse the current choice
The limit of a flyer plus a volunteer email thread
A flyer plus a volunteer email thread can be enough while the situation stays simple: the room and adults are already confirmed.
It starts to break when submitted checks and the requested busing reply are still Replies already requested, the key-access request is unsent, and the flyer already went out.
The Homework hour launch Board earns its place only when the familiar tool—a flyer plus a volunteer email thread—can no longer keep the reason, Launch-path brief, conversation, current state, decision, and history connected.
A practical way to start the Homework hour launch Board
Denise should rename every List or Card that feels artificial. This recipe succeeds when “Choose Monday, delay, or walkers-only” 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.
| Step | Action |
|---|---|
| 1. Write the open rule | Adults, room, way home |
| 2. Count real coverage | Trained is not the same as checked |
| 3. Make access a job | Keys and hours |
| 4. Treat flyers as constraints | Public copy can still change on purpose |
| 5. Choose Monday, delay, or walkers-only | Open a Room before Monday becomes a scramble |
Where this example stops
- This is a fictional example, not a customer story.
- This is not safeguarding, legal, or school-policy advice.
- It does not show Ava contacting families or running background checks.
- It is not a measured program result.