People & HR

How to offboard a departing employee as Fitness Studio Founders

People & HRFor Fitness Studio Founders3 apps11 steps~22 min to set up

When an instructor or front-desk staffer leaves your studio, offboarding falls entirely on you. You're manually revoking their Mindbody or Wodify login, texting them to return their key fob, hunting through Gmail threads to find which class slots they owned, and hoping you remember to update the sub schedule before members notice. There's no checklist, no paper trail, and no single place where 'what does this person have access to' is documented. You lose an afternoon, miss something, and two weeks later a former employee can still log into your scheduling system.

Build this on Starch → See the apps used

People & HRFor Fitness Studio Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A documented offboarding checklist that lives in one place — access revocation, class reassignment, equipment return, and final pay — so you never run it from memory again

Automated email drafts that notify affected members and substitute instructors the moment you kick off the offboarding, pulled from your actual class schedule

A task list with deadlines and P1–P4 priorities so you can hand pieces of the process to a studio manager without losing track of what's done

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Knowledge Management Email Agent Task Manager

Data sources & config

Knowledge Management connects directly to Notion for any existing staff documentation via Starch's scheduled sync. Email Agent connects directly to Gmail via scheduled sync, pulling the instructor's class thread history and your member contact list so drafts are pre-populated with real names and class times. Task Manager runs standalone; no external sync required. Mindbody and Wodify are automated through your browser — no API needed — to pull current access levels and class assignments before you start.

Prompts to copy

Build me an employee offboarding wiki page for fitness studio staff. Include sections for: system access to revoke (Mindbody, Wodify, ClassPass, Instagram, Square, Slack), class schedule changes needed, key and equipment return checklist, final paycheck and benefits notes, and member communication steps. Auto-flag any section that hasn't been updated in 60 days.

Draft a member-facing email notifying them that [instructor name] will no longer be teaching [class name] on [day/time], introduce the substitute, and invite them to rebook. Keep it warm but short — three sentences max.

Create an offboarding task list for a departing instructor. Set P1 tasks for: revoke Mindbody login today, update the public class schedule, notify affected members. Set P2 tasks for: collect key fob and uniform, remove from staff Slack, update the website bio page. Due dates: P1s due same day, P2s due within 48 hours.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Open Knowledge Management and pull up your staff offboarding SOP. If you don't have one, type: 'Build me a fitness studio offboarding checklist covering system access, class coverage, equipment return, and member comms' — Starch drafts it from scratch and stores it in your wiki.

2 Before you do anything else, use Starch's browser automation to log into Mindbody (or Wodify/MarianaTek) and capture a screenshot of the departing instructor's current class schedule, access level, and any admin permissions they hold. Starch automates this through your browser — no API needed.

3 Open Task Manager and type: 'Create an offboarding task list for [name], leaving on [date]. P1: revoke system logins. P2: reassign classes. P3: collect equipment. P4: archive their staff wiki page.' Task Manager generates the list with due dates and priority levels automatically.

4 Go to Email Agent and type: 'Draft an email to all members enrolled in [instructor]'s Tuesday 7am Vinyasa class telling them [substitute] will be covering starting next week. Pull their names from my Gmail contact history for that class.' Email Agent drafts it; you review and send with one click.

5 Send a second email to your substitute instructor pool. Type into Email Agent: 'Draft a message to [sub name] offering them [day/time] slot permanently, include the class details and pay rate of $[X] per class.' Adjust the draft and send.

6 Use browser automation to revoke the departing employee's login to Mindbody or Wodify. Starch navigates to the staff management panel and walks through the deactivation — you confirm each step. Repeat for ClassPass partner portal if applicable.

7 Back in Task Manager, mark 'revoke system access' complete and check off any equipment return items as they happen. If your studio manager is handling returns, share the task list link so they can update status without texting you.

8 Update your public class schedule. If your schedule lives on a website or Mindbody's public page, Starch automates the update through your browser — you describe the change ('replace [instructor] with [sub] on Tuesday 7am'), Starch navigates the page and makes the edit.

9 Archive the departing employee's Knowledge Management wiki page. Type: 'Move [name]'s staff page to the archived employees section and add a note with their last date, final class, and who took over their schedule.' This keeps your records clean without deleting institutional knowledge.

10 One week after offboarding, have Email Agent send a pulse check. Type: 'Draft a short message to the Tuesday 7am class members asking how they're enjoying the class under the new instructor and if there's anything we can do better.' Three sentences, reply-friendly.

11 Review the completed offboarding in Knowledge Management and update the SOP with anything that came up — a system you forgot, a step that took longer than expected. Type: 'Add a note to the offboarding checklist: ClassPass partner portal access takes 24 hours to revoke; initiate it the day before last shift.' The wiki updates instantly.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 — Departing Lead Instructor, 6 Weekly Classes

Sample numbers from a real run

Classes needing coverage	6
Members in affected classes	94
Systems to revoke access	5
Emails drafted by Email Agent	3
Tasks created in Task Manager	11
Time spent by founder (hours)	1.5

Maya teaches six classes a week at a 200-member Pilates studio in Austin — two Tuesday mornings, a Thursday lunch, and three Saturday slots. She gives three weeks' notice. In the past, the founder would have spent a full afternoon manually emailing 94 members across those six classes, updating the Mindbody schedule class by class, texting three substitute instructors to piece together coverage, and hoping she remembered to remove Maya's admin access before the last day. This time: she opens Starch and types the offboarding task prompt. Task Manager generates 11 tasks with P1 through P4 priorities and due dates. Email Agent drafts three member emails — one per class block — pre-addressed to the right groups pulled from Gmail contact history. Starch automates the Mindbody schedule update through the browser, replacing Maya's name with each sub across all six slots. Access revocation for Mindbody, ClassPass partner portal, Square employee login, Instagram shared login, and the studio's Slack workspace happens in one browser automation session. Total founder time: 90 minutes spread across two days. Knowledge Management stores the completed checklist so the next offboarding — whenever it happens — starts from a real playbook, not memory.

Measurement

How you'll know it's working

Time-to-access-revocation after last shift (target: same business day)

Member rebooking rate in affected class slots within 7 days of instructor change

Class fill rate continuity: percentage of pre-departure attendance maintained 30 days post-transition

Offboarding tasks completed on time vs. overdue

Member churn rate in the 60 days following an instructor departure

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Mindbody staff management alone

Handles scheduling reassignment inside Mindbody but gives you nothing for email comms, access revocation in other systems, or any kind of checklist — you're still running the rest from memory.

Google Docs checklist + Gmail

Free and familiar, but the checklist is static, emails are written from scratch every time, and there's no task tracking or deadline enforcement — the founder is still the system.

Gusto or Rippling HR module

Great for payroll and benefits offboarding for W-2 employees, but won't touch your Mindbody schedule, member communications, or the browser-based systems your studio actually runs on.

Notion SOP template

Useful for documenting the process, but Notion doesn't draft emails, create prioritized task lists, or automate any of the actual steps — it's reference material, not execution.

On Starch RECOMMENDED

One platform — knowledge management, email agent, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Mindbody doesn't have an open API for independents. Can Starch still pull class and access data from it?

Yes. Starch automates Mindbody through your browser — no API needed. It logs in as you, navigates to the staff management and schedule pages, and captures what it needs. This is how Starch handles Mindbody, MarianaTek, Wodify, and ClassPass — platforms that don't offer API access to independent studio owners.

Will Email Agent actually know which members are in which class?

It pulls from your Gmail history — if you've corresponded with members about specific class times, Email Agent can surface those threads and use them to populate drafts. For a cleaner member list, you can paste in a CSV from your Mindbody export and tell Starch: 'These are the members in Tuesday 7am — draft them a note about the instructor change.' You review every draft before anything sends.

Is Starch SOC 2 certified? I'm sharing employee and member data.

Not yet — Starch is not currently SOC 2 Type II certified. If that's a hard requirement for your studio's data policies, it's worth knowing upfront. For most independent studio owners managing a team of under 20, the practical data involved here is class schedules and member email addresses, not medical or financial records — but you should make that call for your situation.

What if my studio uses Wodify instead of Mindbody?

Same answer: Starch automates Wodify through your browser — no API needed. You log in once, Starch handles the navigation. The prompts you type stay the same; only the platform changes.

Can I use this for a 1099 contractor instructor, not just a W-2 employee?

Absolutely — most fitness studio instructors are 1099 contractors, and the offboarding workflow applies the same way. The task list just skips the benefits and payroll steps and focuses on schedule reassignment, access revocation, and member communications.

Do I have to rebuild this checklist every time someone leaves?

No. That's exactly what Knowledge Management is for. After your first offboarding, Starch stores the SOP in your wiki. Next time, you open it, update the name and dates, and run the same task and email prompts. You're refining a real playbook, not starting over.