You're three weeks out from the trip, and the research is everywhere. Booking confirmations in two email accounts. A friend's recommendations in a text thread. A handful of saved Instagram posts. A Google Doc you started and lost. The flight times are in one place, the hotel's address is in another, and the restaurant your cousin swore was the best in town is buried in a thread you can't find.
Most travelers run into this version of the same problem. The information exists; it just doesn't live anywhere together. So you spend the night before flying assembling a half-baked itinerary, and on the trip itself you're still tab-shuttling between booking emails, maps apps, and screenshots of recommendations.
A vault that holds one page per trip — with bookings, research, a daily plan, and the small notes you collect along the way — fixes most of it. The agent does the assembling. (For the more general "everything I noticed on the trip" archive habit, Turn Casual Captures Into a Searchable Life Archive is the broader practice.)
One parent page per trip, with everything underneath
In Docapybara, every trip gets a parent page. The page can hold the high-level shape of the trip — dates, who's going, the overall idea — and child pages branch from there for Bookings, Research, Daily plan, Restaurants, On the ground, Packing, and After.
Pages nest with no depth limit, OneNote-style. So Trips > Japan 2026 > Tokyo > Restaurants is a perfectly normal shape, and the agent treats this whole structure as one searchable pile when you ask a question.
For repeat travelers, a Trips parent page with one child per trip becomes a real archive. "Where did we stay in Lisbon last time and what did we say about it?" The agent finds the page from two years ago and quotes your own notes back at you.
Bookings that don't get lost across email accounts
The single most useful page is Bookings. Flights, hotels, trains, rental cars, museum tickets, restaurant reservations — all the confirmations that arrive as PDFs or emails and immediately scatter.
Drop every booking confirmation as a child page on Bookings, dated. PDFs convert to markdown automatically when you upload them, so the flight number, gate, hotel address, confirmation code, and check-in time become searchable text rather than locked inside a flat document.
Forwarded confirmation emails work the same way — paste the body or upload it as a file, and the agent can pull the relevant fields out. "What's the confirmation code for the Kyoto hotel?" Comes back with the code and the page it's on.
For the day of travel, ask the agent to assemble the day's facts. "Tomorrow's flights and check-ins — give me times, gates if known, hotel address, and the confirmation codes I might need at the desk." You get a one-screen brief built from your own bookings.
Research that turns into a real itinerary
Travel research lives in screenshots, Reddit threads, blog posts, and friends' messages. None of it is structured, all of it is potentially useful, and the gap between "I read something good about that neighborhood" and "here's what we should do on Tuesday" is where most trip planning falls apart.
A Research page (or a child per destination) catches the raw material. Paste links, paste blog excerpts, paste the messages your well-traveled friend sent. The agent can search across all of it.
For long-form research — a guidebook PDF, a magazine feature, a blog post you saved — drop the PDF on the page and let it convert. Now the agent can quote it back. "Pull every restaurant the Eater Tokyo guide recommended in Shinjuku, and rank them by how often they're mentioned across my other research too." You get a list grounded in your own collected sources.
The agent's web_search tool fills gaps. "What current reviews say about [restaurant] for vegetarians, and is it open Mondays?" The answer comes back with sources and a date, so you can decide whether the recommendation from two years ago still holds.
A daily plan the agent can build from your notes
Once you have the bookings and the research in the vault, the daily plan stops being a blank page. "Build a draft itinerary for the four days in Kyoto — anchor it on the bookings I've already made, work in the temples and restaurants from my research page, and group things by neighborhood so we're not crisscrossing the city."
You get a draft itinerary that uses your real bookings (so the hotel checkout time matches reality), pulls from your real research (so you're not sent to a place you specifically said you didn't want to go), and groups sensibly. You'll edit it. But editing is much faster than building from zero.
For trips with multiple travelers, ask the agent to flag the things that need a decision. "Look at the Kyoto draft and tell me which items need everyone to agree on, like dinner reservations or a long day-trip." The list comes back, you bring it to the group chat, you make the calls, you update the plan.
On-the-ground notes that survive the trip
The notes you take during the trip are what turn a vacation into something you can actually remember a year later. The dish you loved at that hole-in-the-wall. The street name where the light was extraordinary. The bookstore the cab driver mentioned.
A On the ground page (or one entry per day) catches them. Voice is the right tool — your hands are usually full of a coffee or a guidebook. Tap record, talk for thirty seconds. "Tonight we ate at [name] in Pontocho, the grilled mackerel was the best fish I've had in a year, the guy at the next table recommended a sake bar three streets over called [name]." The transcript lands on the page with a timestamp.
For longer captures — a tour guide's monologue at a temple, a conversation with a local at a market — record longer if it's allowed. The transcript comes back with speaker labels, so you can review what each person actually said, not just what you remembered.
The agent can summarize the trip when you're back. "Pull the highlights from every day's notes — the meals, the sights, the moments worth remembering — into a single trip summary." You get a recap you can send to family, post somewhere, or just keep as a record of what the trip was actually like.
A restaurant database that grows across trips
Travelers who care about food collect restaurants over years. A Restaurants page with an inline database — name, city, neighborhood, cuisine, who recommended it, status (planned / been there / loved / disappointed), notes — becomes a real travel asset.
The :::database::: directive lets the database live alongside whatever prose context you want. The agent can query it. "Pull the restaurants I've loved in any European city, grouped by city, with my notes." Useful when a friend asks for a recommendation, useful when planning the next trip in the same direction.
For the trip you're currently on, ask the agent to suggest tonight's dinner from the relevant rows. "Look at the Tokyo restaurants in my database that are still open and accepting walk-ins, and suggest one near where we are right now." If you've kept the database current, the answer is real and grounded. (Recipe-keepers running the same shape at home can use Your Recipe Box: Stop Losing the Good Ones for the kitchen version.)
Packing, paperwork, and the boring-but-essential stuff
Two pages most travelers wish they'd had: a Packing page and a Paperwork page.
Packing is a per-trip-type list. The shape changes for a beach trip versus a winter city trip versus a backcountry trip. Save the lists you actually used; the agent can adapt them. "Build a packing list for next month's Iceland trip based on what I packed for the Norway trip two years ago, and adjust for it being summer instead of winter."
Paperwork holds passport scans, vaccination records, travel insurance details, and emergency contacts. You hope to never need it. The day you do — at a border, at a clinic, after a lost wallet — having it findable matters. (Consider what you're comfortable storing centrally; sensitive scans can also live in dedicated password-managed vaults if you prefer.)
A related habit some travelers like: a Trip review page after every trip, written in the airport on the way home, capturing what was great and what you'd skip next time. Two years of these turn into the most useful travel-planning resource you own. (Multilingual travelers who want notes to stay in whichever language they arrived in — see Notes for Multilingual Professionals.)
A starter shape that works on day one
If you're moving from "trip stuff scattered across email, screenshots, and a half-finished Doc" to a vault, this is what we'd suggest:
- A Trips parent page — one child per trip you're planning, plus an archive of past ones if you want.
- **Per trip: Bookings, Research, *Daily plan, **and *On the ground.
- A Restaurants database that lives outside individual trips, growing across them.
- Reusable Packing lists to draw from for future trips of the same shape.
- Voice as the default capture tool while traveling — typing on a phone in an airport is rarely the answer.
That's it. Nothing colour-coded, no template required. The vault gets more useful with every trip you take.
The point isn't to turn travel into a logistics project. It's that the small amount of structure you keep means the trip itself is calmer (because the day-of facts are findable), the research compounds (because it lives somewhere stable), and a year later you can actually remember the dish you loved.
Try Docapybara free — start with the next trip you're planning, drop your bookings and research on a single page, and see what the daily plan looks like when the agent builds it from your own notes.