Example
How to plan an international family trip without losing documents, connections, and rest days
Hana’s relative built a beautiful itinerary, but a museum shares the long-connection day and a third city would erase the only rest day. The family must keep two cities, drop that museum day, or wait to ticket until the passport is back.
Travel only with documents in hand, connections that the youngest can actually make, and at least one rest day—without treating the Board as a visa office
Documents, pace, and the no-legal-advice line
Keep the in-process passport beside the relative’s dense spreadsheet
Passports and printed letters as inventory
Separate documents already in the packet from the child's passport still in process
Flights, connections, and buffers
Show a day that is currently two plans
Cities, rest, and museum days
Compare keep-rest-day, drop-museum-connection, and wait-for-passport
Protect a day a third city wants to eat
Passport office and airline holds
Name the document that is not yet in the packet
Keep a clock from being ignored by itinerary excitement
The Two-week trip packet Board separates documents, travel days, on-the-ground pace, and the airline hold dates without giving visa advice.
Open Choose two cities, drop a day, or wait to ticket as a Room with the Pace-and-packet brief.
Ava can compare visible pace and packet facts. Hana owns passports, immigration questions, bookings, family safety, spending, and every travel choice; Ava does not advise, contact, ticket, or transact.
A beautiful itinerary is not a trip if a passport is still in process
The work has a clear center: Travel only with documents in hand, connections that the youngest can actually make, and at least one rest day—without treating the Board as a visa office.
Organizing the evidence does not authorize the software to decide: Whether to keep two cities and the rest day, drop the museum-on-connection day, or wait to ticket until the passport is back.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose two cities, drop a day, or wait to ticket” decision visible through its Superboard view. Hana still owns the call: Hana chooses the itinerary, handles documents, and owns every booking. Ava does not give visa advice.
Available today
Name the work in plain language
These Card titles come directly from Hana's situation: “Choose two cities, drop a day, or wait to ticket” is the live choice, “Long connection same day as museum” holds evidence, and “Child passport in process” names something genuinely in motion outside Hana's control. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| Documents first, then pace | Mission | Keep the in-process passport beside the relative’s dense spreadsheet |
| Choose two cities, drop a day, or wait to ticket | On the ground | Compare keep-rest-day, drop-museum-connection, and wait-for-passport |
| Long connection same day as museum | Travel days | Show a day that is currently two plans |
| Only rest day on the spreadsheet | On the ground | Protect a day a third city wants to eat |
| Child passport in process | Replies and outside conditions | Name the document that is not yet in the packet |
| Airline holds expiry | Replies and outside conditions | Keep a clock from being ignored by itinerary excitement |
| Two adult passports in hand | Documents | Separate documents already in the packet from the child's passport still in process |
Available today
Two-week trip packet: separate the kinds of attention
The Two-week trip packet Board gives this mission one durable operating picture. Hana 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 use Hana's own language so actions, evidence, open questions, and decisions do not collapse into one queue. A separate place for replies is useful only after Hana has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Mission | Documents, pace, and the no-legal-advice line |
| Documents | Passports and printed letters as inventory |
| Travel days | Flights, connections, and buffers |
| On the ground | Cities, rest, and museum days |
| Replies and outside conditions | Passport office and airline holds |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Hana has made visible around “Choose two cities, drop a day, or wait to ticket.” Hana 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 Hana, watch other work on her own, or contact anyone.
Hana owns bookings, documents, and family choices. Ava does not give immigration advice, contact airlines, or ticket travel.
A trip packet: the passport is waiting or in, the rest day is a decision, and a museum is not stacked on a connection by default.
- Request idea: using only the context visible in this Card Room, compare keeping two cities, dropping the museum-connection day, and waiting to ticket. Do not book travel or choose for me.
- Request idea: use only the Pace-and-packet brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Choose two cities, drop a day, or wait to ticket,” group the visible evidence by option and leave the decision open
Available today
One Card Room for the consequential choice
Opening the Card gives the visible item durable depth. Stage can hold Pace-and-packet brief: Place passport status, connection day, rest day, and the three options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Hana will choose a pace that matches documents.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose two cities, drop a day, or wait to ticket” from the visible evidence. Ava can work from the context Hana deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Hana's call remains explicit: Hana chooses the itinerary, handles documents, and owns every booking. Ava does not give visa advice.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Pace-and-packet brief: Place passport status, connection day, rest day, and the three options on one page |
| Chat | Keep Hana's request and Ava's attributed response with the work |
| Pulse | Open decision: Hana will choose a pace that matches documents |
Build only enough Board to make the next decision
Hana should rename every List or Card that feels artificial. This recipe succeeds when “Choose two cities, drop a day, or wait to ticket” 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. Inventory documents | In hand versus in process |
| 2. Card travel days with buffers | Connections are work |
| 3. Protect a rest day | Name it so a third city cannot eat it quietly |
| 4. Park passport-office receipts | Replies and outside conditions until the document exists |
| 5. Choose two cities, drop a day, or wait to ticket | Open a Room before ticketing a fiction |
Where this example stops
- This is a fictional example, not a customer story.
- This is not visa, immigration, or airline-legal advice.
- It does not show Ava booking travel or contacting a government office.
- It is not a measured trip result.