A 30-Day Onboarding Plan for a New Remote Executive Assistant

A new executive assistant can be excellent and still stall for a month if onboarding is improvised. Remote work makes this worse: there is no hallway, no overheard context, and no easy way to absorb the unwritten rules of how the executive likes to work.

This plan is deliberately front-loaded. It assumes the executive and assistant work in different locations and that the assistant needs written access to context rather than memory. The goal by day 30 is not perfection. It is a person who can own a defined slice of the executive's day without constant direction.

Before day one: access and context

Do not let the assistant start with a blank screen. Prepare three things before the first working day.

First, provision named accounts with least privilege. Do not share the executive's credentials. Grant access to the calendar, the approved inbox delegation feature, the document workspace, and the task system, and record who approved each grant and when it will be reviewed.

Second, write a one-page operating brief. It should name the executive's top priorities for the quarter, the ten people who must always reach them, the recurring meetings that cannot move, and the tools the team actually uses. Keep it to a page the assistant can reread.

Third, assign a peer buddy. The buddy answers tooling questions so the executive does not become the help desk.

Week 1: observe and map

Week one is for observation, not output. The assistant should sit alongside the calendar and inbox, read what comes in, and build a map of the work. No sends, no commitments, no changes without review.

Ask the assistant to produce two artifacts by Friday. The first is a preference register: how the executive wants meetings booked, how travel is structured, which messages are drafted versus sent, and what language is acceptable. The second is a request inventory: the recurring categories of work arriving through email, chat, and in-person requests, with rough volumes.

Both artifacts are guesses in week one. That is fine. The point is to make the assistant's mental model visible so it can be corrected cheaply.

Week 2: reversible tasks with review

Move from observation to small, reversible tasks. Drafting replies, scheduling internal meetings, preparing a daily brief, and reconciling a task list are all good candidates because mistakes can be corrected without external damage.

Set a fixed 15-minute review at the end of each day. Walk through what the assistant did, what they chose not to do, and where they were unsure. This is the highest-leverage habit in the whole month. It converts corrections into rules instead of one-off fixes.

Keep a running decision log. When the executive says "next time, decline this type of request unless it comes from finance," that becomes a line in the log and eventually a documented rule.

Week 3: own one slice end to end

By week three, hand over one complete slice of the role. Good first slices include the executive's calendar for a defined set of internal meetings, the daily brief, or travel logistics for one upcoming trip.

Ownership means the assistant decides within the agreed boundaries and escalates only the genuine exceptions. The executive should resist the urge to hover. Instead, review the outcome at the end of the week and adjust the boundaries.

This is also the week to test an exception. Introduce a disrupted day: a flight change, a double-booked slot, or a request from a board member. Watch how the assistant classifies it, whether they escalate at the right moment, and what they record. The response tells you more than a month of routine work.

Week 4: independent operation with guardrails

In week four, the assistant runs the slice independently. Publish a short service agreement: what the assistant owns, the expected response times, the escalation path, and the review cadence. Then hold a first retrospective.

The retrospective should cover three questions. What did the executive stop doing this month? What still required the executive's attention that should not have? What rule needs to change so the answer improves next month?

By day 30, the assistant should be able to run a normal week without daily instruction.

Metrics to watch

Track a small number of signals. How many items did the assistant return to the executive for missing context? How many escalations arrived after the decision window closed? How many times did the executive have to correct the same preference? Falling counts are the clearest sign the ramp is working. Do not use these numbers as a scorecard for the person. Use them to find gaps in the written rules. A high return rate in week two is normal; the same rate in week six means the operating brief is incomplete.

Common onboarding mistakes

The most common mistake is starting with the hardest work. A new assistant asked to manage a board cycle in week one will fail and lose confidence. Another is skipping the written brief because the executive believes they will explain things as they come up. They will not, and the assistant will be left guessing. A third is treating access as permanent; review every grant at day 30 and remove anything that is not needed.

Frequently asked questions

How much of the month should the executive be involved?

Expect to spend roughly 30 to 45 minutes a day in week one, 15 minutes a day in week two, and a weekly review after that. The time investment is front-loaded on purpose. Cutting it produces a slower ramp, not a faster one.

What if the assistant has prior executive experience?

Experienced assistants still need the operating brief. Prior experience shortens tooling questions but does not transfer the executive's specific preferences, relationships, and boundaries. Run the same plan and let the assistant move faster through the early weeks.

When should we decide whether it is working?

Use the day 30 retrospective as a checkpoint, not a verdict. Judge whether the assistant is independent on the defined slice and whether the number of repeated corrections is falling. If both are true, expand scope. If neither is true, diagnose the onboarding materials before blaming the hire.

Getting the ramp right

A remote executive assistant is most valuable once they can operate without being managed task by task. The 30-day plan above is how you get there deliberately. If you would rather not build the plan yourself, our remote executive assistant services are designed around this exact ramp, and you can compare the model with an in-house chief of staff before you decide. For the security side of week one, see our access review routine. The U.S. Small Business Administration also publishes a practical guide to hiring and managing employees that is useful when you formalize the role.