Onboarding a Remote Executive Assistant: The First Two Weeks

The first two weeks decide whether a remote assistant becomes indispensable or quietly underused. Leaders who invest a few focused hours up front typically get a teammate who owns their calendar and inbox within a month. Leaders who don't often conclude "it didn't work." Here is a practical two-week plan.

Before day one: prepare access and context

Access checklist

Set up named accounts — never shared logins — with the minimum access needed:

• Email delegate access (start with read and draft; add send-as later)
• Calendar edit access
• Your team chat (Slack or Teams)
• Password manager vault for shared credentials
• Project and document tools (Notion, Google Drive, SharePoint)
• CRM and expense tools if relevant

Turn on multi-factor authentication for every account. CISA's guidance on MFA is a good, plain-English reference. See our security approach for more.

The "About Me" document

Write — or dictate — a one- to two-page document covering:

• Your role, goals this quarter and top priorities
• Key people: your manager or board, direct reports, top customers, family members who may contact the assistant
• Working preferences: meeting hours, focus time, buffer rules, travel preferences
• Communication preferences: tone, sign-offs, what you never want sent on your behalf
• Pet peeves

This single document saves dozens of questions.

Week 1: Learn and shadow

Day 1: Kickoff (60 minutes)

• Walk through the About Me document.
• Agree working hours and overlap with yours.
• Agree the daily communication rhythm: a morning check-in message and an end-of-day summary.
• Explain the first three tasks they'll own.

Days 2–3: Shadow and document

• The assistant observes your inbox and calendar without acting.
• Record two or three short screen videos of tasks you repeat (booking travel, preparing a meeting brief). The assistant converts these into checklists. See how to write an SOP.
• They build a contact sheet of the people who matter most.

Days 4–5: First ownership, with review

• The assistant starts scheduling internal meetings and drafts replies for approval.
• They prepare meeting briefs for the following week.
• End-of-week review: what went well, what was unclear, what rules need writing down.

Week 2: Take ownership

Calendar

Move calendar management to "act, then tell": the assistant schedules and reschedules within your rules and summarizes changes at end of day.

Inbox

Agree a folder or label system, for example:

• Action — you: needs your decision or reply
• Waiting: awaiting someone else
• Read: FYI, no action needed
• Done/Archived

The assistant triages twice a day and drafts replies for routine messages.

Recurring deliverables

Add one or two weekly deliverables: a Friday look-ahead of next week's calendar, a Monday priorities list, an expense report.

End-of-week-two review

Review against the 30-day plan. Which tasks can move up an authority level? Which rules need refining? See the 30-day success plan.

The communication rhythm that works

Remote-specific tips

• Overlap matters. Make sure at least a few hours of your working day overlap fully with theirs.
• Over-communicate early. In the first two weeks, respond to questions quickly; it builds momentum.
• Use video for feedback. Tone gets lost in text. A five-minute call beats a long message.
• Make it safe to ask. Tell your assistant explicitly that questions are welcome and expected.

Mistakes to avoid

1. Waiting for the "right moment" to hand over the calendar. There isn't one. Start in week one with rules.
2. Granting admin access to everything. Least privilege protects both of you.
3. Skipping the About Me document. It's the highest-leverage hour you'll spend.
4. Judging too early. Evaluate at day 30, not day 3.

A worked example: the day-one access sheet

Most onboarding delays come from access. Here's an illustrative sheet to complete before day one. The principle throughout is the same: named accounts, least privilege and MFA.

The context pack

Write this once. It saves hours of questions:

• Org chart with the people the executive works with most, and notes on how each likes to communicate
• Top 20 external contacts: who they are, the relationship, and any sensitivities
• Current priorities: the executive's top three goals this quarter
• Recurring meetings: purpose of each, and what prep is expected
• Preferences: meeting times, travel preferences, dietary needs for bookings, communication style
• Phrases and sign-offs the executive uses in email
• No-go list: topics, people or folders the assistant should leave alone

A two-week onboarding schedule

Checklist: signs onboarding is on track by day 14

• [ ] The assistant runs the calendar with few corrections
• [ ] Routine emails are drafted in the executive's voice with light edits
• [ ] A daily handoff note arrives every day without reminders
• [ ] At least three SOPs exist and have been reviewed
• [ ] The executive has a clear list of what's next to hand off

If two or more of these aren't true by day 14, slow down and fix the gaps before adding scope.

The bottom line

Remote EA onboarding is a two-week project with a clear sequence: access and context, shadowing, supervised ownership, then real ownership with a daily rhythm. Do that, and most leaders find their assistant running calendar, inbox and recurring deliverables within the first month.

ExecWing runs a structured onboarding for every placement — see how it works and our Executive Assistant service.

Sources

• Cybersecurity and Infrastructure Security Agency, Multifactor Authentication.