The CEO's spouse calls Tuesday morning to confirm the dinner reservation for Friday. You know the dinner is on for Friday because you booked it. What the calendar doesn't show is that the principal asked you on Sunday night to swap the venue if the original spot can't accommodate his sister's allergies, that he'd prefer a quiet table away from speakers, and that his sister flies in from Singapore Friday afternoon and might be in no shape for a long dinner.
The calendar holds the time and place. The CRM holds the contacts. Email holds the back-and-forth. The actual working memory of supporting an executive — preferences, sensitivities, running threads, the texture of how each principal likes things done — usually lives in the EA's head, in a notebook, or in a folder of one-line emails to themselves.
This post is for the executive assistants and chiefs of staff whose job is the thread between the calendar, the contacts, the communication, and the principal's actual life.
What an EA's notes system actually needs to hold
The shape is specific to the role:
- Principal preferences and patterns — flight class, hotel chain, dietary restrictions, the gym he'll cancel a 7 AM call for, the partner whose dinner cannot be rescheduled
- Calendar context — the running notes for each meeting, the prep doc, the why-is-this-on-the-calendar history that gets forgotten three weeks later
- Contact intelligence — not the address-book version, the which assistant at this firm actually answers her email version
- Running threads — the open travel itinerary that's still being negotiated, the gift list for Q4, the board prep that's spread across six emails
- Operational continuity — how the principal likes briefing docs formatted, the standard talking points, the checklist for a board meeting prep
- Cross-principal pattern memory — for EAs supporting multiple executives, the same patterns multiplied
The system has to be private (some of this is genuinely sensitive), portable (you may move with the principal), and fast (the answer needs to be at hand when the principal asks). Adjacent shapes for client-context coordination are in How Account Managers Keep Client Context From Slipping and AI Notes for Customer Onboarding Documentation.
The page-per-thing structure
In Docapybara, every meaningful entity gets a markdown page. Page nesting goes as deep as the EA actually thinks. A common shape for an EA supporting a single principal:
Principal → Preferences (running master document — flight, hotel, food, schedule)Principal → Family → one page per family member with relevant contextPrincipal → Inner Circle → one page per close advisor, partner, key relationshipCalendar → Recurring Meetings (one page per standing meeting with context, attendees, prep template)Calendar → By Quarter (rolled-up notes for the planning rhythm)Contacts → by category — Board, Investors, Press, Counsel, Outside Vendors — one page per personTravel → Active Trips, Completed Trips, Travel Profile (the principal's standing preferences)Threads → one page per open multi-party thread (board appointment, executive search, real-estate transaction, etc.)Operations → standard procedures, briefing doc templates, gift list, expense workflow
Plain markdown. Searchable, copyable, portable. If you ever move with the principal to a new role or organization, the notes come with you in a form anyone can read.
A live database for travel and the calendar prep queue
Embed a :::database::: directive on the Travel page with one row per active trip: destination, dates, purpose, status, hotel, flights confirmed, ground booked, calendar blocked, briefing sent. Six column types — text, date, select, checkbox, link, number — cover the work.
Sort by departure date, you see what's most urgent. Filter by status, you see what's still being negotiated.
The same shape works for the Calendar Prep Queue — a database listing every external meeting in the next 14 days, with columns for the meeting, the attendees, prep status, briefing doc status, and any open questions. Capy, the assistant inside the workspace, can read across the queue when you ask: "What external meetings in the next ten days don't yet have a briefing doc, and what's the prep status for each?"
The agent reads the database, returns the list, and you work the queue.
The agent reads across your whole accumulated context
The EA's job creates an enormous amount of context that's only useful if it's instantly retrievable. The kinds of questions that get fast:
- "Last time we met with the Henderson family office, what did the principal flag as the next ask?" — the agent finds the meeting page, locates the relevant note
- "Pull every recurring 1:1 the principal has and tell me which ones have been rescheduled more than twice this quarter."
- "The principal is asking about the Singapore trip — what was confirmed and what's still open?" — the travel page surfaces both
- "Draft a briefing doc for tomorrow's 9 AM with Sarah Lee at Vector Capital. Use the principal's standard format and pull anything from our prior interactions with her."
The agent uses the prior interactions to draft. You review and adjust. The briefing doc that took forty-five minutes to write from scratch becomes ten minutes of reviewing what's already grounded in your own accumulated notes about the relationship. The agent-acts-on-docs idea behind that is described in Claude Code for Documents.
Recording the meeting that requires real follow-through
Most meetings the principal takes don't need recording. Some do. The board meeting where commitments are being made and you're the one tracking what each director agreed to. The executive search interview where you need to capture the candidate's exact language for later comparison. The strategy session where the principal walks through the next two quarters and you need every nuance.
Audio with speaker labels means each speaker is attributable on replay. The transcript drops on the meeting page. Tomorrow when the principal asks "what did Director Patel commit to on the audit timeline?", the answer is searchable text, not a half-remembered impression of a Tuesday afternoon.
The recording question is one the principal makes — what's appropriate to capture, what consent looks like, what gets retained. Once that's settled, the workspace just holds whatever you decide to record.
Old briefing docs, contracts, and travel records
EAs accumulate paper by the year. Briefing docs from past board meetings, signed contracts, travel itineraries, hotel folios, expense reports, the principal's standing wish list, the gift records. They're useful when findable and a problem when not.
Drop the PDFs into the workspace. Each one converts to markdown automatically, which means the agent can read across them. When the principal asks "what hotel did we use in Tokyo last June and what did the staff prefer about it?", the agent pulls the booking and the post-trip notes. When you're prepping for a board meeting, the agent can read the last four briefing docs and pull the standing themes.
For a long-tenured EA, the accumulated PDFs are often the single most valuable archive that's never been searchable. An afternoon of importing turns it into something the principal can actually rely on.
The contacts layer that the address book doesn't hold
A contact page in the workspace is short but useful: name, role, organization, the assistant's name and contact info, the principal's notes on the relationship, the running thread of recent interactions, anything you've learned about how to reach this person reliably.
A common pattern: every time the principal has a meaningful interaction with a contact, you spend two minutes adding to the page — what the conversation was, any commitments made, anything to remember for next time. Six months later when the principal asks "what did I tell Marcus the last time we talked?", the answer is on the page.
The agent can also help maintain the contact layer. "Read this morning's calendar invite. The principal is meeting with Marcus Chen at Apex. Pull the Marcus Chen page and add the meeting to his interaction history. Draft a one-paragraph briefing on what we discussed last time and what's currently open with him."
The briefing comes back. You adjust. The principal walks into the meeting with two minutes of preparation that has the texture of a long-running relationship.
The standing operations playbook
Every EA develops a personal operations playbook — the way they like to format briefing docs, the standard pre-trip checklist, the board-meeting prep sequence, the expense routine, the holiday gift list workflow. Most of it lives in the EA's head and gets re-derived every time.
In the workspace, the playbook is a folder of pages. Each procedure has a page. Each template lives in the Templates section. When you're onboarding a backup EA or preparing for a vacation, you point them at the Operations folder and they have everything you'd need to run the role for a week.
This is the part of the EA role that compounds across years. The first board meeting you prep takes a long Saturday. The fortieth one takes a couple of hours, because the workspace has the template, the prior briefings, the standing talking points, the previous board's questions, and the agent can draft most of the structure from what's already there. The repeatable-procedure layer specifically is covered in Standard Operating Procedures, Without the Wiki Maintenance Tax.
Try Docapybara free
The fastest test: pick the next external meeting on the principal's calendar that requires a briefing doc. Open Docapybara, drop in whatever you have on the contact and the topic, and ask the agent to draft the briefing in the principal's standard format. Then add a Calendar Prep Queue database for the next two weeks of external meetings. Try Docapybara free, bring the principal's actual upcoming week and one folder of past briefings, and see whether the workspace can hold the texture of supporting an executive the way your current setup tries to.