How to Onboard a Remote EA: The 30-60-90 Day Plan

Most failed executive assistant hires are not actually hiring failures. They are onboarding failures. The wrong process in the first 90 days kills more good EA hires than any recruiting mistake.

The reason founders skip onboarding is not laziness. It is the same reason they were behind on the EA hire in the first place: they are busy, they are stressed, and they assume the new hire will figure it out. The new hire will not figure it out. Senior remote operators are good at figuring things out, but they cannot figure out what your priorities are, how you make decisions, who matters in your world, or what your communication preferences are.

The founders who invest two hours per week in the first month of an EA hire get a working operator by month three. The founders who invest no time get an underperforming hire who leaves by month six. The math is not subtle.

Get them access in advance, calendar, email (delegate or shared inbox), document storage, team comms, and any other system they will need. Send a welcome packet: a 1–3 page document that introduces the business, key people, products or services, and the EA's role at a high level.

Schedule the first week. Pre-schedule shadow sessions with you, one-on-ones with key team members, time blocks for reading documentation, and the first weekly one-on-one. Pre-load context by sharing recordings of recent meetings and examples of how you have handled common situations.

Week 1: meet, observe, listen. The EA meets key team members, external partners, and clients. They sit in on your meetings as a fly on the wall, taking notes. By end of week one, they should know the names, roles, and basic context of the top 20 people in your world.

Week 2: the EA takes meeting notes, captures action items, and drives follow-ups. They start drafting first-pass responses to routine email, which you review and either send or edit. This is the apprenticeship phase.

Weeks 3–4: calendar shadowing, then initial autonomous tasks. By end of week four, the EA owns specific recurring tasks: weekly meeting notes, follow-up tracking, low-stakes scheduling, vendor coordination. They have stopped asking for permission on the small stuff.

The introduction of a new EA to your existing team is one of the highest-leverage moves you can make in the first week, and one of the most commonly fumbled.

The mistake is the one-line Slack announcement: "Hey everyone, please welcome [Name], my new EA. They'll be helping with my calendar and inbox." This sends the wrong signal to both the EA and the team. It positions the EA as administrative support rather than an operating partner, and it fails to clarify how the team should work with them.

The better approach has three parts.

A real introduction message. Five to seven sentences. Who they are, what their background is, what they will own, and what authority they have. "I'm thrilled to have [Name] joining the team as my Executive Assistant. [Name] comes from [background] where they supported [type of role]. They will be owning my calendar, inbox, travel, and meeting coordination, and over time will expand into broader operational support. When [Name] reaches out on my behalf, please treat it as coming from me directly. Their decisions on my behalf carry my authority. Please welcome them and make their first weeks easy."

A round of one-on-ones. In the first two weeks, the EA should have a fifteen to thirty minute one-on-one with every person on your leadership team and any other key team members they will work with regularly. Pure get-to-know-you conversations. No agenda. The goal is relationship-building and context.

A public signal of trust. Within the first month, do something visible that signals to the team that you trust the EA. Have them run a meeting on your behalf. Send out an important email from their address. Make a decision based on their recommendation publicly. The team is watching to see how seriously you treat the hire, and small visible signals shape how they treat the EA.

Weeks 5–6: calendar ownership. The EA accepts and declines meetings on your behalf within agreed parameters. They protect focus blocks. They handle conflicts. This is the highest-friction transition for most founders. Do it anyway.

Weeks 7–8: inbox ownership. The EA processes your inbox daily, triages urgency, drafts responses for routine matters, handles email autonomously that does not require your judgment. The 'agreed parameters' model is key, sit down at the start of month two and articulate explicitly what the EA can do without checking. The clearer the parameters, the more confidently the EA acts.

Weeks 9–10: expanded scope. The EA takes on functions beyond the core, vendor management, light project work, personal coordination if in scope, travel logistics fully autonomous, meeting prep including pre-reads and agenda drafts.

Weeks 11–12: steady state. The EA is operating at full scope. You should be spending less than an hour per week directly managing them. The signal of a successful onboarding at day 90: you can take a week off and the EA keeps your operational world running without you.

A common founder question: in what order should I hand over specific responsibilities? The order matters because some handoffs unlock others.

Week 1-2: Meeting notes and follow-up tracking. Low risk, high learning value. The EA absorbs context about your meetings and starts building visibility into your work.

Week 3-4: Recurring scheduling tasks. Standing meetings, easy reschedules with people you have met before, simple calendar maintenance.

Week 5-6: Calendar ownership with check-ins. Full calendar access. The EA proposes moves and you approve. By the end of this phase, you should only be approving complex or sensitive moves.

Week 7-8: Inbox triage and routine responses. The EA starts processing email daily, drafting responses for routine matters, and surfacing only what needs your direct attention.

Week 9-10: Travel logistics fully autonomous. Within your standing preferences, the EA books trips, handles changes, and manages logistics without check-ins.

Week 11-12: Vendor and stakeholder coordination. External relationships start running through the EA. Your accountant, lawyer, key executive partners interact with the EA for scheduling and routine coordination.

Months 4-6: Project ownership. The EA starts owning specific projects: fundraise logistics, board meeting prep, hiring administration, internal events.

Months 6 plus: Strategic scope. The EA takes on parts of your operating system: weekly leadership meetings, monthly business reviews, annual planning logistics.

The sequence matters because each handoff builds on the previous one. You cannot delegate inbox triage well until the EA understands your priorities. You cannot delegate projects well until the EA owns the operational rhythm around them. Skipping steps almost always leads to handoffs that fail and have to be redone.

Format: 30 minutes. Every week. Same time. Same medium. Cover: what is working, what is not working, the week ahead, their growth, and your specific feedback.

The biggest mistake founders make is treating the weekly one-on-one as optional. It is not. Skipping it sends the message that the relationship is not a priority. The EA notices. Compounding small signals like this is what erodes a working relationship over six to twelve months.

Loom for recorded walkthroughs (faster than written SOPs). A shared notebook (Notion, Google Docs, Coda). A shared task system (Asana, ClickUp, Trello). Calendar tools that let the EA manage your time without confirming every block. A password manager (1Password, Bitwarden) for secure credential sharing.

You do not need every tool on this list. You do need to be intentional about what tools the EA gets access to and how you collaborate inside them.

Not giving real access. Vague scope. No weekly one-on-one. Daily approval requests after day 45. No feedback loop.

Withholding feedback because you do not want to be unkind ends up being the most unkind thing you can do. Tell them specifically what is working and what is not, every week.

Sometimes despite best intentions, the first ninety days do not go smoothly. The EA is not absorbing context fast enough, mistakes are happening, or the relationship feels strained. The good news: most struggling onboardings can be salvaged if you catch them early and intervene directly.

The diagnostic questions to ask yourself in week six or seven if things feel off:

Am I actually delegating, or am I doing the work and asking the EA to watch? If you are still making every calendar decision yourself and the EA is just executing, the EA is not learning judgment. Force yourself to delegate decisions, even imperfect ones, and let the EA learn from the outcomes.

Is my feedback specific and frequent enough? If you have given the EA five pieces of specific feedback over six weeks, that is not enough. They need feedback weekly at minimum, and ideally several small moments of feedback each week.

Am I doing the weekly one-on-one consistently? Cancelling or skipping the weekly one-on-one even once is a soft signal that the hire is not a priority. The EA notices. Hold it religiously.

Is the scope clear? If the EA does not know exactly what they own and what they have authority to decide, the role is structurally unworkable. Write it down. Send it to them. Have them confirm understanding.

Is the hire actually senior enough for the role? Sometimes the answer is that the candidate was the wrong fit. If after honest reflection the gap is the operator's seniority, not your management, the right answer is to part ways early rather than drag the relationship out for six months.

The honest conversation that saves struggling hires sounds like: "I want to check in on how things are going. I feel like we are not yet at the pace I expected. Here is what I think is happening, here is what I am willing to change, and here is what I need from you. What do you think?"

This conversation is uncomfortable and ninety percent of founders avoid it. The avoidance is what kills the hire. The conversation, even if it ends in parting ways, almost always produces a better outcome than letting the relationship deteriorate silently.

Your calendar runs without you managing it. Your inbox is triaged daily and you only see the messages that need your direct attention. Travel happens without your involvement. You are spending less than an hour per week directly managing the EA. You have recovered 10–15 hours per week of your time.

The EA is confident in their role, feels trusted, and is starting to suggest improvements to how things work. They are pushing back when they disagree, and the disagreements lead to better decisions about half the time. If you are at day 91 and this is not the picture, the diagnosis is usually one of two things: the hire was not senior enough for the role, or the delegation has not actually happened.