Going live is easy. Staying credible after going live is harder. This guide covers how to publish classes so families see accurate details and your team is not fixing avoidable errors all week. It is written for studios that are juggling term setup, staff cover, and parent questions at the same time. The focus is controlled visibility, not maximum visibility.
Open with one realistic go-live plan
If you run 18 classes, do not publish all 18 first. Publish the classes you can support operationally this week.
A practical launch pattern for a busy studio:
- Publish 4 to 6 core classes first.
- Confirm request handling rhythm for three days.
- Publish additional groups once queue turnaround is stable.
This keeps trust high and avoids a growing backlog.
Visibility depends on both account and class settings
Class links only work when both layers are configured.
Account layer
In Settings > Profile, public enrolment must be enabled (Allow Public Enrollment, shown in UK wording as public enrolment). If this is off, public links do not behave as live enrolment pages.
Class layer
In class publishing settings:
Statusmust bePublished.Make this class publicly visiblemust be on.- The class must not be archived.
Missing any one of these means the public route will not serve that class as enrolment-ready.
Public copy quality affects queue quality
Families decide quickly based on what they read on the class page. Poor copy creates poor requests.
Before publishing, check:
Public descriptionclearly states who the class is for.Booking notesare current and specific.- Age range and schedule details reflect this term, not last term.
If the wording is vague, staff will spend time clarifying basics that could have been clear upfront.
Example: outdated booking note creates duplicate enquiries
A dance school left a note from last spring saying "trial-only intake". Parents submitted requests expecting one-off sessions while the class was now full-term intake. The queue filled with avoidable follow-up.
Payment setup must match what the public form can offer
Public step 4 only shows payment plans that pass class and enrolment-type checks.
For a plan to appear:
- it must be assigned to the class,
- it must be active,
- it must support the selected enrolment type.
For single-class enrolments, direct-debit-only plans are not available. That is expected behaviour.
For UK teams, publish with payment language ready:
- say when Direct Debit collections are expected,
- explain when card is the immediate route,
- avoid promising instant status updates where collection timing applies.
Example: plan mismatch blocks submissions
A studio published a one-off workshop and attached only a direct-debit-only profile. Parents could reach attendance selection but could not complete a valid payment-plan choice for single class. Requests stalled until a compatible plan was added.
Teacher and venue details: visible by design, not accident
Class pages include schedule, venue, level, ages, pricing, and class type where available. Teacher details are shown publicly only when the teacher profile is publicly visible.
Use this deliberately:
- hide teacher profile when privacy or staffing reasons require it,
- keep venue and time accurate to reduce pre-class questions,
- verify capacity field if you rely on capacity decisions in the queue.
Example: teacher visibility handled intentionally
A martial arts studio used cover staff for six weeks and kept teacher profiles private until permanent assignments were final. Class links stayed useful without overpromising named instructors.
The 20-minute pre-launch check
Before sharing links on WhatsApp or email, run one self-check in a private browser window.
- Open the studio public page and confirm class appears.
- Open the class link and verify class details section.
- Complete one self-enrolment path (adult).
- Complete one parent/guardian path (child).
- Confirm both create pending requests in the queue.
If either path fails, fix now. Do not launch and patch later.
Safeguarding checks before promotion
Publishing is not only a marketing step. It is a safeguarding step whenever children are involved.
Check these before go-live:
- under-18 classes have clear guardian expectations in booking notes,
- age ranges are correct,
- child enrolment flows do not rely on staff "manual interpretation",
- internal team knows who handles sensitive corrections.
This reduces risky ad-hoc decisions once requests start arriving.
Pitfalls to avoid
- Setting class status to published but forgetting public visibility toggle.
- Turning public enrolment on at account level before class details are updated.
- Publishing with payment plans that do not support selected enrolment types.
- Reusing last-term booking notes without age or schedule checks.
- Launching every class in one batch without queue capacity.