Standard Operating Procedures are the difference between a VA who executes your vision and a VA who executes their best guess at your vision. Without SOPs, every task is an interpretation. With well-written SOPs, your VA can handle 80% of recurring situations without asking you a question - and knows exactly when the other 20% requires your input.

Most gym owners know they need SOPs but find the documentation process overwhelming. This guide breaks it down: what good SOPs look like, how to build them efficiently, where to store them, and a review cadence that keeps them current.

Why Most Gym SOPs Fail

The typical gym SOP is either a paragraph buried in an employee handbook (too vague), a 40-page document no one reads (too long), or a video recording from two years ago that references a platform that's since been replaced (too outdated).

Effective SOPs share four properties:

Specificity. Not "respond to member inquiries promptly" but "respond to all new member inquiry emails within 60 minutes during business hours using Template A (linked below). If the inquiry arrives outside business hours, respond within 30 minutes of your shift starting the next day."

Numbered steps. Paragraphs require interpretation. Numbered steps require execution. A 12-step SOP is clearer than a 3-sentence description of the same process.

Decision logic. Good SOPs anticipate the judgment calls your VA will face. "If the member requests a refund for an amount under $50, process it directly in MindBody and email them confirmation. If over $50, escalate to [owner] via Slack immediately before taking any action."

Maintenance ownership. Every SOP should have a named owner (usually you), a version date, and a scheduled review date. SOPs without review dates become outdated and misleading.

The SOP Stack: What to Document First

Not everything needs an SOP on Day 1. Prioritize by frequency and consequence: tasks your VA will do daily or weekly, and tasks where errors are costly (billing, member cancellations, public communications).

Tier 1: Document Before Your VA Starts

These SOPs should exist before your VA's first day, because they govern their highest-frequency tasks:

  1. New lead inquiry response - channels to monitor, response templates, qualification questions, CRM entry procedure
  2. Class booking and cancellation - how to process a booking change in MindBody, what constitutes a late cancel vs. no-show, how to apply the relevant fee or credit
  3. New member welcome sequence - what to send, when, via which channel, how to personalize
  4. Waitlist management - auto vs. manual processing, response window, what to do when no waitlisted member responds
  5. Instructor substitution protocol - who to contact, in what order, how to update MindBody, how to notify members

Tier 2: Document in Weeks 2-4

  1. Social media scheduling - how to use your scheduling tool, post frequency per platform, caption requirements, hashtag strategy, approval process
  2. Email newsletter production - which platform (Mailchimp, Klaviyo), template to use, content inputs required, send schedule
  3. Review monitoring and response - which platforms to check, response templates, escalation for negative reviews
  4. Failed payment follow-up - notification trigger, Day 1 message, Day 3 follow-up, Day 7 escalation
  5. Member retention outreach - how to identify at-risk members, outreach templates, escalation to coaching staff

Tier 3: Document by End of Month 1

  1. Membership change processing - upgrades, downgrades, pauses, cancellations (each has its own workflow in MindBody)
  2. Competitive research - what to track, how often, reporting format
  3. Data entry and CRM management - tagging conventions, field requirements, lead source attribution
  4. Monthly reporting - which reports to pull, from which systems, in which format, delivery schedule

SOP Template: The Format That Works

Use this structure for every SOP. It can be a Notion page, a Google Doc, or a ClickUp document - format matters less than consistency.

SOP Title: [Descriptive name - what the task is, not what it's called internally]

Owner: [Name of person responsible for keeping this SOP current]

Version: [Date of last update - e.g., 2026-04-28]

Review Date: [When this SOP should next be reviewed - typically 90 days after creation, then every 6 months]

Purpose: [1-2 sentences explaining why this task matters and what good execution looks like]

Tools Required: [List every platform, template, or document the VA needs to complete this task]

Steps:

  1. [First action, specific enough that there's no ambiguity about what "done" looks like]
  2. [Second action - include login paths, menu locations, field names where relevant]
  3. [Decision point, if any: "If X, do Y. If Z, escalate to [person] via [channel]."]
  4. [Continue through every step...]
  5. [Final step should always include a logging or confirmation action - how does the VA record that this was done?]

Escalation Triggers: [Bullet list of specific situations that require owner involvement before proceeding]

Templates Used: [Link to any email templates, scripts, or message formats referenced]

Notes: [Edge cases, seasonal variations, anything that doesn't fit the steps above]

Real Example: New Lead Inquiry Response SOP

SOP Title: Responding to New Membership Inquiries

Owner: Studio Manager / VA Supervisor

Version: 2026-04-28

Review Date: 2026-07-28

Purpose: To ensure every new lead receives a warm, personalized, and prompt response that moves them toward booking a trial class or intro session. Response speed and quality directly affect conversion rates.

Tools Required: Gmail (shared inquiry alias), GoHighLevel CRM, MindBody (to check class availability)

Steps:

  1. Monitor the shared inbox ([email protected]) throughout your shift. Check for new inquiries every 30 minutes.
  2. Open any new inquiry email. Do not mark as read until you have sent a response.
  3. Identify the inquiry type: (a) general interest, (b) pricing question, (c) specific class inquiry, (d) personal training inquiry. Use the appropriate response template from the Templates folder (link below).
  4. Personalize the template: insert the member's first name, reference the specific class or goal they mentioned in their inquiry.
  5. Reply from the shared inbox within 60 minutes of the inquiry arriving during business hours (9am-6pm). If the inquiry arrived outside business hours, respond within 30 minutes of your shift starting.
  6. After sending, open GoHighLevel. Create a new contact record with: full name, email, phone (if provided), lead source (tag as "Inquiry Email"), inquiry type, and the current date.
  7. Add a Note to the contact record summarizing their inquiry in 1-2 sentences.
  8. Set a follow-up task in GoHighLevel for 3 days from today: "Day 3 follow-up if no response to inquiry."
  9. Log the inquiry in the daily tracking sheet (link below) with: name, inquiry date, response sent timestamp, inquiry type.

Escalation Triggers:

  • Any inquiry that mentions a complaint about the gym, a negative prior experience, or a request for a refund - escalate to [owner] via Slack before responding.
  • Any inquiry from a corporate or partnership prospect (multiple memberships, B2B) - flag to [owner] before responding.

Templates Used: [Link to Template A: General Interest, Template B: Pricing, Template C: Class Specific, Template D: Personal Training]

Notes: During January and September (high-volume inquiry months), prioritize inquiry response over other tasks when volume exceeds 10 new inquiries per shift.

Where to Store Your SOPs

The tool matters less than the structure. Three good options:

Notion

The best option for most gym businesses. Notion allows you to organize SOPs by department (Operations, Marketing, Member Services), link SOPs to each other, embed templates and videos, and give your VA view or edit access per document. The search function finds any SOP by keyword, which is critical when your VA has a question mid-task and needs to find the relevant procedure quickly.

Build your SOP hub as a Notion database with properties: SOP title, department, owner, version date, review date, and status (current / needs update / archived). This gives you a master view of your entire procedure library and flags which SOPs are due for review.

Google Drive

Effective for smaller operations. Store SOPs as Google Docs in a shared Drive folder with a clear naming convention: [Department] - [Task Name] - v[Date].doc. The main weakness is navigation - a 40-document folder becomes hard to search by context rather than by exact filename.

Use a Google Sheet as your SOP index: columns for SOP name, link, owner, last updated, next review date. Your VA checks the index first, clicks through to the document.

ClickUp or Asana

If you're already using a project management tool, SOPs can live there as Docs (ClickUp) or integrated documents. The advantage is co-location with your task management - your VA can reference an SOP while working on the related task without switching tools.

Building SOPs Efficiently: The Watch-and-Document Method

The fastest way to create an SOP for a task you currently do yourself is to execute the task while narrating, recorded via Loom, then have your VA transcribe it into step format.

The process:

  1. Open Loom and share your screen.
  2. Complete the task at a slightly slower-than-normal pace, narrating every step as you go: "Now I'm going to MindBody Reports, clicking on Class Enrollment, setting the date range to last 7 days..."
  3. Send the recording to your VA with the instruction: "Please watch this and write up the steps as an SOP using our standard template. Send me the draft for review."
  4. Review the draft. Your VA will have interpreted some steps - correct any that are wrong and add any decision logic they couldn't infer from watching.
  5. Publish the approved version to your SOP hub.

This method produces a draft SOP in under an hour for most tasks, versus the 3-4 hours most gym owners estimate it would take to write one from scratch. The VA also learns the task while creating the document - two outcomes from one activity.

SOP Review Cadence

SOPs that aren't reviewed become outdated - and outdated SOPs are worse than no SOPs, because your VA follows them confidently while producing wrong results.

90-Day New SOP Review

Every newly created SOP should be reviewed 90 days after creation. Questions to ask:

  • Has this SOP been followed? (Check your VA's task logs - if a procedure exists but the task keeps being done differently, the SOP isn't working)
  • Have any tools changed that affect this procedure?
  • Did any edge cases arise that the SOP didn't anticipate?
  • Is the escalation logic still accurate?

Bi-Annual Full Library Review

Every 6 months, run through your entire SOP database and verify each document is still current. This is a 2-3 hour process when done systematically - your VA can run the initial pass (checking tool names, links, template references) and flag anything that needs your judgment.

Trigger-Based Reviews

Certain events should automatically trigger an SOP review regardless of schedule:

  • Any platform update that changes a workflow (MindBody UI changes, GoHighLevel feature updates)
  • Any staff or VA change - a new VA following an outdated SOP creates problems immediately
  • A recurring error your VA makes - the first question is always "does the SOP cover this clearly?"

The Compound Value of Strong SOPs

Well-maintained SOPs do something beyond enabling your current VA: they make your business transferable. A gym with documented procedures can onboard a replacement VA in days rather than weeks when turnover happens. It can scale to multiple VAs without the institutional knowledge bottleneck. It can potentially be sold or franchised because the operations are documented and repeatable, not locked in the owner's head.

That's the long game. The short game is simpler: your VA executes consistently, errors drop, you get fewer interruptions, and your mental model of "I have to do everything myself" dissolves into something more useful - a clear picture of who does what, documented, repeatable, and working.

Build the first five SOPs this week. Add five more next month. In 90 days, you'll have a system.

For where SOPs fit in the broader role, see our Fitness VA tasks list and the hiring playbook.

Frequently asked questions

How long should an SOP be?

Most operational SOPs are 1 to 3 pages. Anything past 5 pages signals you're trying to document multiple workflows in one doc - split it.

Loom or written SOP - which is better?

Both. Loom captures tone and edge cases; written captures the canonical steps. The pattern that works: 5-bullet written summary at the top, embedded Loom below, then numbered detailed steps.

How often should SOPs be updated?

Quarterly review for stable SOPs; immediate update when the underlying workflow changes. SOP drift is the most common reason "trained" VAs start performing worse 6 months in.

Where should SOPs live?

Notion or a shared Google Drive folder. Anywhere both the coach and VA can edit and search. Avoid scattering across email, Slack, and personal docs - those break within months.

What if I don't have time to write SOPs?

Record a Loom while you do the task once, write 5 bullet points summarizing what you did, and ship it. The VA improves the doc as they execute. This produces drafts in 30 minutes that would otherwise take 3 hours of typing.

#fitness va SOPs#gym standard operating procedures#virtual assistant documentation#fitness business systems#gym workflow management