New executive assistant onboarding without predecessor documentation

You are two weeks into a new EA role supporting a VP at a company with 200 employees. The previous EA left a month before you started. There was no overlap period. The “handover documentation” is a shared Google Doc with a list of recurring meetings, a few vendor contacts, and a note that says “Sarah in finance handles the travel policy.” Everything else, the VP’s preferences, the stakeholder relationships, the context behind ongoing projects, the history of decisions made in the last year, left when the previous EA did.

The situation

Your first week is a cascade of things you do not know. The VP mentions a conversation with a board member “from the offsite” and expects you to pull together follow-up materials. You do not know what offsite, what was discussed, or what was committed to. You ask the VP. They give you a partial answer and suggest you check the calendar and email. The email thread has 47 messages. The relevant decisions are buried in message 23 and message 41. It takes you 45 minutes to piece together what happened.

This pattern repeats throughout the day. Every task requires context you do not have. Industry research confirms this is the norm: more than half of EAs report their onboarding was minimal and they had to figure it out on their own. Most EA relationships fail in the first 90 days, not because of hiring mistakes, but because of poor onboarding structure. The most common failure mode is “task dumping”: handing over responsibilities without the context needed to execute them.

One EA described the experience on a community forum: “I was hired as an experienced professional but the company has very specific processes and workflows, none of which I was onboarded to. My colleague believes it is because I did not get properly onboarded. Even so, the client only sees an incompetent member of staff.”

Where friction appears

The first friction is stakeholder blindness. Your VP has relationships with dozens of people: board members, clients, direct reports, cross-functional partners. You do not know the history, tone, or context of any of these relationships. Every interaction is a guess. You send a formal email to someone who expected a casual Slack message. You schedule a 30-minute meeting when a 10-minute check-in was the norm.

The second friction is decision amnesia. Decisions were made in meetings you never attended, during a tenure you were not part of. When someone references “what we agreed last quarter,” you have no way to verify or provide context. You cannot be the organizational memory for decisions you were not present for.

The third friction is process archaeology. The recurring tasks on your list have no documented reasoning. Why does this report go to this distribution list? Why is this vendor preferred over the cheaper alternative? Why does the weekly leadership meeting have this specific format? The answers existed in your predecessor’s head. Now they exist nowhere.

How the memory layer helps

When the organization has been using a persistent knowledge system, the new EA inherits something far more valuable than a handover document. They inherit the full conversation history: every decision made in meetings, every commitment tracked, every stakeholder interaction logged with context.

On your first day, instead of asking the VP “what happened at the offsite?” you query the system. The answer includes what was discussed, what was decided, what follow-ups were assigned, and who raised which concerns. You have context that would normally take three months of relationship-building to accumulate.

When you need to prepare for a meeting with a board member you have never met, the system shows you the last four conversations, the open commitments, and the topics that matter to this person. Your first briefing is not a guess. It is informed by the same knowledge your predecessor had, minus the months it took them to build it.

When you encounter a process with no obvious reasoning, you can search for when and why it was established. The decision that created the current reporting structure was made in a meeting eight months ago. The reasoning is preserved. You understand not just what to do, but why, which means you can make intelligent adjustments instead of blindly following inherited procedures.

The onboarding shift

Without a knowledge system, the typical EA onboarding takes three to six months before the EA is fully effective. The first 90 days are spent asking questions, building mental models, and slowly earning trust through proximity. The institutional knowledge that was lost is rebuilt one interaction at a time.

With a persistent memory layer, the onboarding period compresses. The new EA starts with context instead of building it from zero. The trust-building still takes time, because trust is personal. But the competence gap, the period where the EA cannot provide context because they were not there, shrinks dramatically.

The hidden cost of scattered knowledge shows up most acutely during transitions. Every fact the new EA has to rediscover is time the organization already spent learning once before. A system that preserves that learning makes what happens when the EA leaves a manageable transition instead of an organizational crisis.

Related answers

If your organization is planning for an EA transition, or if you are a new EA who inherited nothing, the foundational problem is the same: knowledge from conversations was not captured in a form that survives the person who held it. Fixing that requires a system that builds knowledge continuously, not a better handover checklist.