You start a wedding plan with a Google Doc, a Pinterest board, a spreadsheet for the guest list, an inbox folder for vendor emails, a Notes app entry from the venue tour, and a group chat with your partner that has somehow become the source of truth for half of it. By month four, you can't remember which florist quoted what, whether the photographer's deposit cleared, or what your partner said about the music three weekends ago.
Major life events all do this. Weddings, big anniversaries, big birthdays, baby showers, retirement parties, family reunions — they're all the same logistical shape. Lots of small pieces, hard date, several people involved, dozens of decisions. A single vault per event, with the agent doing the searching, takes the chaos out without forcing you into a rigid project-management tool you don't actually want.
One event, one parent page, child pages for every dimension
In Docapybara, the event gets a top-level page named for it: October Wedding, Mom's 70th, Family Reunion 2026. Pages nest indefinitely, OneNote-style, so the parent can have child pages for Vendors, Guests, Budget, Timeline, Day-of, Decisions, and whatever else the event needs.
The agent treats the whole tree as one searchable surface. "What was the photographer's deposit and when's the balance due?" gets answered from wherever you put it — the contract PDF, the email you pasted, the note from the meeting. Not from where you think you put it. (For the broader "trip, event, or move" version of this shape, see Planning Any Trip, Event, or Move in One Vault.)
Vendors — contracts, deposits, and the conversation history
The Vendors page is the one that gets used most. An inline database via the :::database::: directive handles it well: vendor type (venue, catering, photo, video, florist, music, hair, makeup, transport), name, contact, contracted price, deposit paid, balance due, deadline, status.
Every vendor gets a child page underneath. On the child page, paste the contract PDF, the email thread, your notes from the meeting. Docapybara converts uploaded PDFs to markdown via docstrange, so the agent can actually read them — "what's the venue's policy on bringing in outside alcohol?" comes back with the answer and points to the contract section.
After every vendor call, drop a quick note. Audio recording is helpful for the longer meetings — tap record (with consent), and you get a transcript with speaker labels. The agent can summarize: "Summarize today's meeting with the florist — what we agreed on, what's still open, what they're sending us."
When the vendor sends an updated quote two months later, the diff is easy. "Compare the florist's original quote to the one she sent this week — what changed and how much more is it?"
Guests — the list, the RSVPs, and the dietary spreadsheet
The guest list outgrows a spreadsheet faster than people expect. Names, plus-ones, addresses for invitations, RSVP status, meal choice, dietary restrictions, table assignment, accommodation needs, song requests, the small note about the cousin who can't sit near a specific other cousin.
An inline database handles all of it. The agent can pull subsets: "Who's confirmed with a vegetarian or vegan meal?" "Who's traveling from out of town and needs hotel info?" "What's the current head count, and what's our contracted minimum?"
For the seating-chart problem specifically, the agent can help with first drafts. "Looking at the dietary table, group people who'd seat well together — keep the family-side notes I wrote in mind." You're still making the calls, but the first pass takes a fraction of the time.
Budget — the running total and the surprise costs
The Budget page is where most weddings drift. An inline database with category, vendor, planned amount, actual amount, deposit paid, and balance handles the tracking. The agent updates it on demand. "Add a line — alterations, $400 estimate, Sandra's, deposit not paid." Row appears.
The agent can also summarize the running picture. "What's the current total spent vs. budgeted, and which categories are most over?" Comes back with the gap. Useful for the conversation about whether to add the photo booth or skip it.
For weddings with multiple contributors (your parents, your partner's parents, the both of you), a separate database column for who's paying keeps it clean. The agent can pull each person's exposure.
Timeline — the day-of, hour by hour
Once the date approaches, the Day-of page is the one you actually open on the day. Hour-by-hour, with addresses, phone numbers, who's responsible for what, and the vendor arrival times. Stripped down — everything else stays in the deeper pages.
The agent can build it from the Vendors and Timeline pages. "Generate the full day-of timeline starting at 8 a.m. — vendor arrival times, ceremony, reception, last call. Include phone numbers." You get a clean printable. Send it to the wedding party, the venue coordinator, your day-of contact.
For the morning-of stress specifically, a Getting ready sub-section handles the small details: hair appointment time, makeup arrival, the breakfast order, the music playlist for the suite. Anything that's not on the main timeline but matters at 7 a.m.
Decisions — what you picked, and what you and your partner agreed
Weddings involve hundreds of small decisions. Most of them you'll never have to defend. A few you'll re-litigate at midnight in the kitchen.
A Decisions page captures the calls you've made and why. "Why we picked the indoor-outdoor venue option — rain backup, photographer preference, cost." Three sentences. Next time it comes up — and something always comes up — the agent can pull the context. "What did we decide about the ceremony music, and why?"
For decisions you and your partner are still working through, drop them in a Conversations sub-section dated. The agent can summarize the state: "What's the state of the rehearsal-dinner question — what have we agreed on, what's still open?" Lower stakes than retirement-planning conversations, but the same shape — and the related note-taking discipline carries directly to Capture and Compare Options for Any Major Decision.
After the event — the thank-yous and the keepsakes
Before the event, Inspiration deserves a small page of its own. Pinterest is fine for visual mood, but it doesn't connect to anything else. For the inspiration that actually feeds decisions — flower arrangements you want to show the florist, a venue layout you saw online, a color palette you keep coming back to — drop it on an Inspiration page in the vault. Images can drop on the page. Links can drop on the page. The agent can pull them when needed: "Find the three centerpiece references I saved — I want to send them to the florist." Comes back with the images and your notes. For specific vendor conversations, you can quote your own notes back at the vendor without re-finding the image. That alone saves an hour of looking through saved tabs.
Once the day is done, the vault keeps two more pages doing real work. A Thank-yous page tracks who gave what gift, who needs a card, what you said in the card if you want to avoid repeating yourself across 80 of them. The agent can draft personalized notes from a few inputs: "Draft a thank-you to Aunt Marge for the candlesticks — warm, mentions our trip up to see her last year."
And a Keepsakes page is where the photos, the playlist, the vendor recommendations, and the lessons-learned for friends getting married next year all live. Useful when a friend asks for the florist's name eighteen months later. (For the broader life-archive shape this becomes part of, see Turn Casual Captures Into a Searchable Life Archive.)
A starter shape for the first month
If you're moving from "scattered across docs and inbox folders" to a vault, this is what we'd suggest starting with:
- Event name — top-level parent
- Vendors — page + inline database, child pages per vendor
- Guests — inline database
- Budget — inline database
- Timeline / Day-of — chronological
- Decisions — running notes
- Inspiration — images and links
- Conversations — dated entries between you and your partner
That's it. Nothing color-coded, no template required, no project-management tool to learn. The vault grows with the event. For ongoing pricing details, see /pricing/ — but the shape works on the free tier for most events.
The point isn't to turn the wedding into a project-management exercise. It's to have one place where the answer to "what did we decide / what did they quote / who's coming" lives, so the planning weeks aren't also memory-tax weeks.
Try Docapybara free — start with the Vendors page and the Decisions page, and the next time something comes up, the answer will be in one search.