Trainer Scheduling and Payroll: One System or Two?

Most small studios start the same way: class schedule in their booking platform, trainer pay worked out in a spreadsheet, then manually entered into Xero or MYOB at the end of the fortnight. It works until it doesn't — and the moment it stops working is always the same. A trainer subs a class at the last minute, the sub isn't logged anywhere official, and you're either overpaying the original instructor or underpaying the one who actually showed up.\n\nThis is not an edge case. Sub and swap is the norm in group fitness. A busy 20-class-per-week studio can easily run 5–8 substitutions in a fortnight. If your payroll process requires a human to catch every one of those, your payroll process has a structural flaw.\n\n## Why the Two-System Problem Gets Worse as You Grow\n\nWith three trainers and 15 fixed classes per week, the manual reconciliation is annoying but manageable — maybe 45 minutes per pay run. Add a second location, a mix of employed and contracted instructors, variable rates by class type (reformer Pilates pays differently to a spin session at many studios), and that 45 minutes becomes three hours. At some point an operations manager is doing almost nothing but chasing timesheets.\n\nThe underlying issue is that the schedule is the source of truth for what happened, but payroll is calculated in a completely separate system that has no direct access to it. Someone bridges them manually. That bridge is where errors live.\n\nCommon failure modes:\n- A last-minute cancellation isn't reflected in the pay run because the class was still showing on the original schedule\n- A casual instructor picks up extra classes in the same week and crosses a threshold that changes their tax treatment — but nobody noticed because hours aren't tracked cumulatively anywhere visible\n- A trainer switches from employed to contractor mid-month and the rate change only gets applied from the next full pay period because payroll wasn't told promptly\n\nNone of these are catastrophic individually. Collectively they erode trainer trust, create Fair Work or Fair Trading compliance exposure (in Australia, underpayment of casual employees is taken seriously), and make your ops manager's life miserable.\n\n## What an Integrated System Actually Does\n\nA proper connected setup means the schedule — including subs, cancellations and additions — feeds directly into a timesheet or hours ledger that payroll reads from. No one is copying numbers between systems. When a trainer is marked as having delivered a class, that delivery is the payroll trigger.\n\nThis sounds simple. The reason most studios don't have it is that the main fitness booking platforms (Mindbody, TeamUp, Pike13 and their equivalents) have scheduling built for member-facing booking, not for staff payroll. They'll tell you who taught what, but the payroll engine — rate cards by class type, employed vs contractor treatment, superannuation calculations in Australia, PAYE in the UK — isn't their strength. So most studios end up with a scheduling tool that does 80% of the job and a payroll tool that covers the other 80%, with a 60% overlap in the middle that nobody owns cleanly.\n\nThe build-vs-buy decision here is real. If your rate structure is simple — flat rate per class, same for everyone — you can probably make a Zapier connection between your booking platform and Xero work reliably enough. But the moment you have:\n\n- Multiple rates per instructor (based on experience, class type or time of day)\n- Salaried staff who also teach classes (so hours matter for overtime, not just for pay)\n- Contractors who invoice you vs employees on payroll\n- More than one location pulling from a shared instructor pool\n\n…a Zapier zap is not going to hold. You need something that models your rate structure properly and handles exceptions without human intervention.\n\n## The Case for Custom Logic Over a Generic Platform\n\nOff-the-shelf platforms make a lot of assumptions about how studios pay their trainers. Many assume a flat per-class rate. Some handle tiered rates but only along a single axis (seniority, say). Very few handle the combination of: base rate + attendee bonus after a threshold + different rates for different class formats + super on some payments but not others.\n\nIf your rate structure is genuinely simple, the off-the-shelf path is probably right. Pick a platform with native payroll export or a clean integration with your accounting software, run it for a quarter, and see how many manual corrections you make. If the answer is fewer than five per pay run, you're probably fine.\n\nIf you're making more corrections than that — or if your business model requires rate complexity because you're competing for quality instructors with revenue-sharing arrangements — the economics of a custom-built scheduling and payroll module start to look different. You're already paying someone to reconcile. That cost is just hidden in a salary rather than a software licence.\n\nFor context on how this decision sits alongside your broader software stack, the framework in Build vs Buy a Gym Membership Platform applies directly here: the question is never whether you can make the off-the-shelf tool work, it's whether the workarounds cost more than the alternative over three years.\n\n## What to Actually Look For in a Scheduling-Payroll Setup\n\nWhether you're evaluating platforms or scoping a build, these are the things that actually matter operationally:\n\nRate card flexibility. Can you set different rates per instructor, per class type, and per location — and can those rates change over time without affecting historical pay runs?\n\nSub and swap handling. When a sub is logged, does payroll automatically reassign the hours? Or does someone have to manually update both systems?\n\nContractor vs employee treatment. Australia and the UK handle this differently, but both require the system to know which category a worker falls into and apply the right tax and super/NI treatment. This should not be a manual step.\n\nCancellation rules. If a class is cancelled with less than 24 hours' notice, does the instructor still get paid? Your policy should be codified in the system, not enforced by whoever does the pay run that fortnight.\n\nAudit trail. When a trainer queries their pay — and they will — you need to show them exactly which classes contributed to which payment, with timestamps. A PDF timesheet is not enough; the underlying schedule records need to be accessible.\n\nIf you're also thinking about front-desk admin being a drag on your operations, note that scheduler-payroll reconciliation often eats more back-office hours than front-of-house tasks. The visible problem at the desk is easier to spot; the payroll spreadsheet runs quietly in the background until it explodes.\n\n## How Multi-Location Changes the Calculation\n\nA single studio can sometimes absorb manual payroll reconciliation. Three locations sharing a pool of 25–30 instructors — many of whom teach across sites in the same week — cannot.\n\nThe multi-location case is where custom software earns its keep clearly. You need a system that treats your instructor pool as shared infrastructure: one rate card per instructor (or per role), applied consistently regardless of which site they taught at, with location-level reporting so site managers can see their own labour costs without seeing the whole group's payroll.\n\nOff-the-shelf platforms tend to treat each location as a semi-independent entity. That's fine for member booking. It's a headache for payroll when the same instructor worked at three sites in one week.\n\nIf you're at the stage of asking when to replace your gym management software entirely, the scheduling-payroll gap is one of the clearest signals: if your current platform can't model your instructor workforce without spreadsheet support, you've outgrown it.\n\n## The Minimum Viable Fix Before a Full Build\n\nIf a full custom build isn't on the cards this quarter, there's a practical middle step: build the rate card logic in your existing payroll software and use your scheduling platform only as a timesheet source. Export a structured hours report from the scheduling tool each pay period — class name, instructor, duration, date — and import it into payroll rather than rekeying it. It's still two systems, but you've removed the human transcription step that causes most errors.\n\nThis only works if your scheduling platform can export clean, consistent data. If the export format changes with every platform update, or if sub logs aren't captured in the export, you're back to manual. Test it for one full pay cycle before committing.\n\nThe longer-term question is whether your instructor count and rate complexity justify purpose-built logic. If you're paying 20+ instructors across multiple rate types, the answer is almost always yes — the reconciliation cost alone justifies the build inside 18 months.