The 30-Day Success Plan for a New Remote Assistant

"How do I know if it's working?" is the most common question leaders ask in the first month with a new assistant. The answer is to decide what "working" means before you start. A 30-day success plan does exactly that: it sets goals, defines a few measures and schedules the review.

Why a written plan matters

Without a plan, evaluation becomes a feeling — and feelings in the first month are dominated by a few early mistakes. A written plan:

• Makes expectations explicit for both sides
• Sequences work so the assistant isn't overwhelmed
• Creates objective checkpoints
• Turns day 30 into a decision point rather than a vague impression

The structure

A good 30-day plan has four parts:

1. Outcomes: three to five things that should be true by day 30.
2. Weekly milestones: what gets added each week.
3. Measures: a handful of KPIs with baselines.
4. Review: a scheduled conversation at day 30.

Example outcomes

Adapt these to the role:

Executive assistant - Calendar fully managed by the assistant within your rules - Inbox triaged twice daily with fewer than 20 items needing your attention at day's end - Meeting briefs delivered for all external meetings

Revenue assistant - Weekly CRM hygiene checklist run before every pipeline review - Target account lists built for two segments - Meetings booked and confirmed within 24 hours of request

Bookkeeper - Bank and card accounts reconciled for the prior month - Bills captured and payment runs prepared weekly for approval - Month-end close checklist completed with reviewer sign-off

Week-by-week template

Week 1: Access, context, shadowing

• All access provisioned with MFA
• About Me / company context document reviewed
• Two to three SOPs drafted from recorded walkthroughs
• First low-risk recurring task owned (e.g., scheduling internal meetings)

Week 2: Supervised ownership

• Core daily workflows owned with review
• Daily end-of-day summary established
• First weekly deliverable delivered (report, list or close task)

Week 3: Expanded scope

• Authority level raised on tasks that went well
• Second weekly deliverable added
• SOP library expanded to cover all recurring tasks

Week 4: Steady state and review

• All agreed workflows running without daily prompting
• KPI snapshot compared with baselines
• Day-30 review held

Choosing measures

Pick three to five measures. Make them observable and tied to the outcomes:

Record a baseline in week one. Without it, you're comparing against memory.

Running the day-30 review

Spend 45 minutes. Cover:

1. Outcomes: which are met, partly met or not met?
2. Measures: how do they compare to the baselines?
3. What's working: be specific. Reinforce it.
4. What isn't: is it a missing rule, a skills gap or a fit issue?
5. Next 30 days: new tasks, authority upgrades, and any training needed.

If it's a skills gap, agree a coaching plan. If it's a fit issue after honest effort, act — with a managed provider, that's when you ask for a replacement. ExecWing replaces assistants at no additional cost if the fit isn't right (how it works).

Tips for leaders

• Protect 15 minutes a day for questions in the first two weeks.
• Batch feedback into the weekly review unless something is urgent.
• Praise in writing. It builds confidence and documents what good looks like.
• Don't add everything at once. Sequencing is the point of the plan.

For the assistant

The best assistants treat the 30-day plan as their own. They keep a running log of questions answered and rules learned, propose SOPs before being asked, and come to the weekly review with a short list of what they want to take on next.

A filled-in example plan

Here's an illustrative 30-day plan for an assistant supporting the founder of a 40-person agency. It shows the level of specificity that makes the day-30 review easy.

The day-30 review agenda

Hold it as a 45-minute conversation, not a performance appraisal:

1. Scorecard (10 minutes): go line by line. Green, amber or red.
2. What's working (10 minutes): each side names two things.
3. What's not (10 minutes): each side names one or two things, with a specific example.
4. Next 30 days (10 minutes): two or three new areas to hand off, and what "done" looks like for each.
5. Logistics (5 minutes): access gaps, tool requests, schedule adjustments.

Write the outcomes in the plan document and carry them into the 60-day plan.

Checklist: before day one

• [ ] The plan document is shared with the assistant before they start
• [ ] Each outcome has a measure and a starting point
• [ ] Access for each outcome's systems is ready
• [ ] The weekly review is on both calendars for weeks 1–4
• [ ] The day-30 review is booked

Questions the assistant should ask in week one

Good assistants ask these. If yours doesn't, offer the answers anyway:

• What does a great week look like for you?
• What are the things you never want to see slip?
• Who are the people whose emails always come first?
• What decisions can I make without asking you?
• How do you prefer to get updates: Slack, email, or a call?
• What frustrated you about past support, if you've had it?

When the plan goes off track

If an outcome is red at day 15, don't wait for day 30. Check three things in order: was "done" defined clearly, did the assistant have the access and information needed, and is it the right task to hand off at this stage? Most early misses come from the first two, not the assistant's ability.

The bottom line

A 30-day plan turns onboarding from a leap of faith into a managed project: clear outcomes, staged milestones, a few measures and a scheduled review. It's the simplest thing you can do to make a new assistant succeed.

For the first two weeks in detail, read onboarding a remote EA. To delegate more effectively, see how to delegate to an EA.