Most fitness VA relationships fail in the first three weeks - not because the wrong person was hired, but because no one told them how the business actually runs. They get access to your inbox, a vague "just jump in," and a month later you are frustrated and they are guessing.

A structured 14-day onboarding changes that outcome. It gives you a clear read on the VA's capability while giving them the context they need to work without constant hand-holding. By day 14, you will know whether this person will still be with you in six months.

If you are still finalizing who to hire, start with the guide on how to hire a Fitness VA, then return here for the onboarding plan.

Before day one: setup tasks (owner's job)

Do these before your VA logs in for the first time.

Create a dedicated email address. Something like [email protected]. Never give access to your personal inbox or the primary owner address. Route client-facing accounts through this address.

Set up password sharing. Use LastPass, 1Password, or Bitwarden. Create a shared vault. Add your VA as a user. Never send passwords in Slack or email.

Provision tool access with the correct permission level. For MindBody, that means a staff user role with permissions scoped to their tasks - not admin access. Same logic applies to GoHighLevel, Trainerize, TrueCoach, and any other platform.

Build a shared drive folder. Google Drive or Notion works. This is where you put SOPs, brand assets, client communication scripts, and the onboarding checklist itself.

Prepare a 30-minute voice or video walkthrough of your business. Record it once in Loom. Cover: who your clients are, how a client moves from lead to paying customer, what happens when something goes wrong, and who they contact when they are unsure. This replaces dozens of future questions.

Days 1-3: access and orientation

The goal for the first three days is full access and context. No real tasks yet.

Day 1

  • Walk through the shared drive structure together on a video call
  • Confirm they can log in to every tool (MindBody, GoHighLevel, Trainerize, email, scheduling tool, social accounts)
  • Share the recorded business overview Loom from setup
  • Send them the SOPs for their first three tasks in writing - not just verbal

Day 2

  • Review each SOP together. Ask them to restate each process back to you in their own words in writing
  • Have them shadow one real task without touching anything - watch you process a new lead or handle a client check-in while on a screen share

Day 3

  • First live task: process one real lead from start to finish with you watching
  • Debrief immediately after: what they did well, what needs adjustment, any questions they have about the SOP
  • Confirm communication channel and response time expectations in writing (Slack, email, or WhatsApp - pick one and document it)

Days 4-7: supervised execution

Now they work independently on a narrow task set, with daily check-ins.

Tasks to assign in this window:

  • Lead triage and follow-up in your CRM
  • Client scheduling confirmations and reminders
  • Daily social media posting from pre-approved content queue
  • Updating client records after sessions or check-ins

Check-in structure:

  • 15-minute Loom from them each day summarizing what they completed, what they could not resolve, and what they are handling tomorrow
  • You review and respond with brief written feedback within the same day

What you are watching for:

  • Do they follow the SOPs or improvise?
  • Do they flag uncertainty before making a wrong call, or do they quietly do the wrong thing?
  • Is communication clear, brief, and on time?

One SOP deviation is normal. A pattern of SOP deviations in week one is information you need early.

Days 8-10: expanded scope

If days four through seven went well, add two more task categories.

  • Payment failure follow-up using the approved script
  • Weekly KPI report pull from MindBody or GoHighLevel
  • First draft of one email newsletter

Move daily Looms to every other day. You are checking outputs, not process steps.

Key milestone: By end of day 10, they should complete the KPI report pull with no intervention from you. If they need significant hand-holding on a task they were trained on by day three, note it.

Days 11-13: independence and edge cases

This is where you deliberately introduce complexity.

  • Give them one edge-case scenario in writing: "A client emails asking to pause their membership but is mid-contract. What do you do?" The right answer is to flag it to you with context, not to resolve it unilaterally.
  • Ask them to identify one SOP they think is missing or needs updating. Their answer tells you a lot about how they think about systems.
  • Have them run one full week of their task set without any Loom prompts - just deliver outputs on time.

Day 14: go/no-go checkpoint

Sit down for a 30-minute structured review. Cover four points:

  1. Outputs. Did tasks get done on time, every day? Pull the work log. Be specific.
  2. Quality. Were client communications on-brand? Were records accurate? Did reports match reality?
  3. Escalation behavior. Did they flag the right things and handle routine things without escalation? Or the reverse?
  4. Self-assessment. Ask them directly: what part of this role feels most natural and what is hardest? Honest answers here predict long-term fit better than any task you observed.

If outputs and quality are strong and escalation behavior is appropriate, extend the contract and set a 30-day check-in.

If you see consistent issues - missed tasks, SOP deviations, poor escalation judgment, communication problems - address each one specifically. Give one more week to correct. If the pattern continues, this is the point to part ways before the relationship costs more to exit than it would have to pass on at day 14.

After day 14: sustaining the relationship

Onboarding ends, but the structure continues.

  • Weekly 20-minute async Loom check-in (them to you) forever
  • Monthly synchronous call to review scope, workload, and performance
  • Quarterly rate review if they are offshore - acknowledge when they have grown into the role

Write every task expansion into a new or updated SOP before you assign it. The most common reason a good VA starts declining in performance after month three is scope creep without documentation.

Frequently asked questions

What if my VA already has fitness experience - do I still need 14 days?

Yes. They may know MindBody cold but not know your specific workflows, client personas, or communication style. The onboarding plan is about your business, not general fitness VA knowledge. Even an experienced hire benefits from days one through three of structured access and orientation.

How many hours per day should onboarding take?

For the VA: their full scheduled hours. For you: about 30 minutes on days one through three, then 15 minutes daily through day seven. By week two, your time drops to reviewing async Looms and written outputs.

Should I pay for onboarding time?

Yes. You are asking them to work and learn simultaneously. Pay the agreed hourly rate from day one. Trying to negotiate a reduced onboarding rate signals poor faith and you will lose good candidates to it.

What tools should I use to manage the onboarding checklist?

Notion, Google Docs, or a simple shared checklist in Asana or ClickUp. Pick whatever your business already uses. The format matters less than the fact that both parties can see and update the same document.

What if I do not have SOPs written yet?

Write them before the VA starts, even if rough. If you hand-record a Loom of yourself doing each task and write a five-bullet summary, that counts. Hiring a VA without SOPs means you are training them on tribal knowledge that will not survive their first sick day.