EA Insights Executive Intake
executive intake
Key Executive Intel to support the Operational Model

Defining where to start

Understanding how an executive works comes with establishing a partnership. One where trust and transparency are built on a structured approach. Clarity on the preferences, boundaries, and context give the guardrails needed to anticipate what is needed instead of reacting to what’s already happened.

Understanding patterns before judgment

Architecting data and information includes the calendar. When we think in systems, we know that the data added to the executive’s schedule aligns to not only the executive’s remit, but also to the overarching mission of the organization. Executive assistants are the primary coordinators of the executive’s calendar which involves a level of expertise in time blocking where it matters. A well-known Harvard Business School study tracked how CEOs actually spent their time over several months. What the research found: the best calendars were formed on a skill that is not easily obtained through experience alone. It is built overtime, understanding how the executive operates, clarity about where the executive’s attention needs to be, where it shouldn’t and where the boundaries are.

Gathering the data and the information starts with an executive intake. It is where the EA identifies the baseline. This is the foundation that the EA will rely upon to determine how each ask fits, how it matters, and why so that the executive can move with intention. When there’s a signal that there wasn’t alignment on a calendar entry, log it. Use a pattern recognition log to help see where the gaps were, when the energy was off, and how the executive showed up on that day. Managing a calendar comes with understanding everything under the umbrella of steering the operations of the executive, including their executive presence.

Not all the fields are essential for every executive. The most important ones are those that intersect with action an EA needs to perform on a regular basis. For instance, when coordinating travel, the EA requires the executives preference when drafting the itinerary. From travel reservations to briefing documents, and passport/visa requires that can impact the overall trip when the right elements are not confirmed. And if travel is required for a speaking engagement, the necessary engagement requires the extra level of detail from prep days in advance of the stage time to the live event where mics, staging and all particulars matter.

How to use it: A short statement under the label explains what the field is for. In side the fields are placeholder text examples or the formate.

The sections above capture what you learn directly from the executive. These are the tools that fill in the rest, the research an EA does independently to support travel, logistics, and whatever else the remit calls for. Review the ones relevant to this executive now, and come back as the portfolio changes.

Document preparation

PassportIndex

Checks passport strength and visa requirements by nationality and destination.

Recommended step: Cross-check every international leg against passport and visa requirements before booking, and flag anything that needs 30 or more days to process.

Manage costs

Corporate Travel Index Calculator

Benchmarks hotel, meal, and ground transport costs city by city.

Recommended step: Run it before submitting a travel budget for sign-off, especially for a first trip to an unfamiliar or high-cost city.

City guides

Citymapper

Real-time transit routing and city navigation.

Recommended step: Pull ground transit times into the itinerary whenever the executive is optimizing for time or cost over a car service.

Monitor flights

FlightAware

Live flight tracking, gate information, and delay alerts.

Recommended step: Track connecting flights the day of travel, and build buffer time into the next commitment the moment a flight starts running late.

Manage layovers

LoungeBuddy

Lounge access and amenities at layover airports.

Recommended step: Check lounge access ahead of any long layover, especially where status alone doesn’t guarantee entry.

Planning

Travel Advisory

Government-style travel risk ratings by country.

Recommended step: Check the destination’s risk level before finalizing any international trip, particularly a first-time destination.

Destination guides

World Travel Guide

Country-by-country guides covering visas, customs, climate, and local know-how.

Recommended step: Skim it while prepping the itinerary for an unfamiliar destination, especially for customs or etiquette that won’t show up on a calendar.

Itinerary consolidation

TripIt

Consolidates flights, hotels, and car reservations into a single shareable itinerary.

Recommended step: Forward each confirmation email to it as you book, so the executive always has one current itinerary instead of a stack of separate emails.

Currency

XE Currency

Live currency conversion and historical exchange rates.

Recommended step: Check it again just before finalizing an international expense estimate, rates from early planning can shift by the time the trip happens.

If you are using a large language model connecting to your files, calendar or inbox, this intake can become more than a document you fill out once. Structured as a context file inside a vault the agent is instructed to reference, it become something the agent can rely upon to consult so you are not re-iterating the same preferences in every new chat.

A typical vault is a folder of numbered context files the agent reads before acting, each one covering a different part of how the executive operations. Travel and logistics usually gets its own file.

  • 📁 EA Operations Vault
    • 📄 README.txt
    • 📄 SKILL.md
    • 📁 EA Context
      • 📄 01-EA-Agent-Constitution.txt
      • 📄 02-Executive-Office-Operating-Model.txt
      • 📄 03-Calendar-Judgment-Model.txt
      • 📄 04-Executive-Briefing-Model.txt
      • 📄 05-Meeting-Prep-and-Recap-Model.txt
      • 📄 06-Open-Loops-and-Action-Tracker.txt
      • 📄 07-Communications-and-Voice-Model.txt
      • 📄 08-Onboarding-and-Ramp-Model.txt
      • 📄 09-Achievements-and-Impact-Model.txt
      • 📄 10-Travel-and-Logistics-Model.txt
      • 📄 11-Confidentiality-and-Governance-Rules.txt
      • 📄 12-Starter-Prompts-and-Examples.txt

The Travel Preferences and relevant Calendar Management answers from this intake are usually what instructs that file. Once it’s in the vault, an agent operating under the system and rules in the other context files can reference it directly, drafting an itinerary, flagging a documentation gap, or answering a quick question about seat preference, without you repeating yourself.

What it looks like in practice: a sample file, built from fictional preferences to show the structure.

# 10-Travel-and-Logistics-Model.txt # EA Operations Vault / EA Context # Last updated: [date] by [EA name] ## Executive Profile Name: Ruby Radiance Role: Chief Operating Officer Home base: Global Universe ## Airlines & Loyalty 1. United (1K status), loyalty number on file in Concur 2. American (Executive Platinum), backup carrier only Seat preference: aisle, front of the plane, never the bulkhead ## Hotels & Loyalty Preference order: Marriott Bonvoy (Titanium); a well-reviewed boutique property when no Marriott option exists Room preference: high floor, away from the elevator ## Ground Transfers Airport: black car service, booked at least 24 hours ahead City: rideshare acceptable for anything under 20 minutes ## Documentation Passport: valid through 2031, confirmed against the physical document Global Entry: on file, renewal due 2027 TSA PreCheck: active ## Train Acceptable versus flying when the route is under 3 hours and saves a connection ## Non-Negotiables Tied to Travel No red-eyes before a same-day morning meeting Sunday travel only after 2:00pm, protects family dinner ## Notes for the Agent – Confirm seat and hotel preference before finalizing any booking – Flag any trip requiring a visa 30 or more days out – See also: 03-Calendar-Judgment-Model.txt, for how travel time interacts with protected agenda blocks – See also: 11-Confidentiality-and-Governance-Rules.txt, for what this agent may surface about travel documents, and to whom

Notice the last two lines. A travel and logistics file rarely stands alone, it typically points back to the files that govern judgment and access, so the agent knows the rules to work with.

Worth building in from day one: Worth building in from day one: Keep the vault in a permission based location or connector, not a shared drive open to the whole team. Define in the governance file what the agent may surface about travel documents and to whom, especially passport numbers, home addresses, and emergency contacts. Redact identifiers and personal/confidential information you don’t want in a third-party model’s context before pasting this intake. And keep the file current: after the download or copy summary above, that’s your starting point for this file.