Bring real studio questions to the demo

Follow a class pass from purchase to attendance

Imagine a fictional student, Maya, buys a 10-class pass that expires on June 30. Ask where Maya and the studio team can see the expiry date and remaining balance. Then book her into a class. Does the system reserve a visit at booking, or does the balance change only when she attends?

Cancel that booking and check whether the visit is restored. Mark a later booking as attended and see whether one visit is consumed. Ask what happens after the expiry date, after a late cancellation, and when no visits remain. The exact rules matter when a student asks, “How many classes do I have left?” Ask to see the visit history that explains the balance.

Fill a class and examine the waitlist

Choose a fictional popular evening class and fill every place. What does the next student see when trying to book? If a waitlist is offered, follow the path from joining the list through a cancellation opening a place. Does the student need to accept an offer? Is a booking made automatically? What deadline applies, and what do the student and front desk see at each step?

Ask the presenter to demonstrate that the class cannot accidentally accept more students than the room's stated capacity. A waitlist label alone does not tell you how places are offered or confirmed, so test the behavior your studio would rely on.

Distinguish a pass, billing, and membership access

A class pack sets a number of visits, perhaps with an expiry date. Recurring billing describes a repeating charge. A membership entitlement describes the access or benefits a member receives. A system may connect these concepts, but one does not prove the others are handled as your studio expects.

Describe a concrete example, such as a monthly membership that includes four classes and a separate 10-class pack that lasts several months. Ask how each is represented, what happens at renewal or expiry, and what happens when a student has more than one eligible purchase. Use a payment test only after the vendor explains its sandbox setup; do not enter a real card or create a live charge.

Test the schedule and the team's view

Use a real type of schedule change, such as moving Tuesday morning flow by thirty minutes or replacing an instructor. Ask what happens to existing bookings and what the student is told. Then have the presenter show the relevant views for an instructor and a front-desk teammate. An administrator screen alone does not establish what each person can see or change.

Use your Pilates format and check messages

For mat Pilates, test a mat-class example. For equipment-based Pilates, explain your equipment count and booking rules, then ask for a direct demonstration of that specific need. A class capacity is not the same thing as reserving an identified reformer or station.

Before testing bookings, cancellations, waitlist movement, or purchases, ask whether email and SMS are disabled, captured, or routed to controlled test contacts. Confirm no unexpected messages will reach real students. After the demo, write down what you saw, what was only described, and what remains unanswered.

Explore YogaFitPro's product direction

To see how scheduling, capacity, client records, attendance, class-pass balances, and waitlists fit together for a yoga studio, visit the YogaFitPro product overview.