Yoga & Fitness Instructors
Daily or weekly sessions with a cap per date, and a ten-visit card for the regulars who cannot make every one.
Write the term once - the night it meets, the weeks you are off, the session it finishes on - and take every registration for it from a single link, with zero platform fees.
Online class scheduling with free registration and a seat cap counted per session date, multi-session class cards, recurring terms that end themselves, and payments through your own Stripe or PayPal account.
Conversational Spanish, Level 1
Recurrence
Ends after 12 sessions.
Thirteen Tuesdays, twelve sessions. The hollow week is Nov 24, taken out as a date exception.
One recurring event. Change the start time once and all twelve sessions follow.
The thing you actually teach is a term. Twelve sessions, one topic, the same students each week, and a last night.
The term
Same course, same students, thirteen weeks. Entering it as twelve separate events is twelve chances to mistype a time.
The setup
A repeat pattern, exceptions for the weeks you are off, and an end. Move the class an hour later once and every session moves.
The close
A term ends on a closing date or after a set number of sessions, so it is not still taking sign-ups for week nineteen in March.
The term, drawn
Thirteen weeks, twelve filled. The hollow one is a date exception, not a cancelled event. Write one
All three are on the free plan. None of them are a spreadsheet.
Pick the days of the week and the start time. Repeats can be daily, weekly, every few weeks, or monthly by date or by weekday, so a fortnightly workshop is one setting rather than a second calendar.
Date exceptions take single dates out, so a holiday week or a week you are travelling disappears from the schedule without rebuilding the term. You can add one-off dates back in the same way.
End the recurrence after a set number of sessions, or on a closing date, or never. This is the setting that makes a term a term instead of a weekly slot that runs forever.
Worth knowing
A recurring event carries one name and one description, so week four is not separately titled "the past tense". If the weeks really are different topics with different prices, make them separate events - cloning one is a click - and keep them together in a sub-schedule. If they are one course, the term is the right shape, and the week-by-week breakdown belongs in the description, because the agenda you set runs the same way in every session.
The cap is set once on the course and counted separately for every session, so week three filling up does not close week four. Free registration, free plan.
| Session | Date | Taken | Seats left |
|---|---|---|---|
| 01 | Sep 15 |
|
full |
| 02 | Sep 22 |
|
2 / 14 |
| 03 | Sep 29 |
|
5 / 14 |
| 04 | Oct 6 |
|
9 / 14 |
| 05 | Oct 13 |
|
11 / 14 |
| 06 | Oct 20 |
|
14 / 14 |
| 07 | Oct 27 |
|
12 / 14 |
| 08 | Nov 3 |
|
8 / 14 |
| 09 | Nov 10 |
|
6 / 14 |
| 10 | Nov 17 |
|
4 / 14 |
| off | Nov 24 | No class this week | date exception |
| 11 | Dec 1 |
|
3 / 14 |
| 12 | Dec 8 |
|
1 / 14 |
Week one is full and week six is empty, on the same course, at the same time. That is the point: the count lives on the date, not on the course. Students see the seats left for the date they are looking at, and a full date stops taking sign-ups without touching the others.
A name and an email gets somebody a seat on a specific date, with an optional cap. No card, no checkout, and no plan to upgrade to first.
Once a registration date is full, the sign-up button on it becomes a waitlist. When somebody drops, the first person waiting for that date is emailed and has twenty-four hours to claim the seat before it moves to the next in line. Set the cap you can actually teach to and let the list do the rest. On a sold-out paid date the same waitlist is Pro.
They want one card that covers the term. A pass counts the way your course actually sells: a fixed number of visits, or unlimited visits until it runs out of days.
10 visits
Any Tuesday in the term.
4 used · 6 left
Ten cells against twelve sessions: two Tuesdays can slip. Valid 120 days from purchase. Admits 1.
Unlimited
Every session, until it expires.
Same strip, no cells
Valid 90 days. Scoped to the Beginner sub-schedule.
Class cards are Pro, at R199 a month, along with anything that carries a price. Publishing the term and taking free registrations are not. See what ticketing includes.
Cards are sold next to single seats, not instead of them. Both need the Pro plan, because both carry a price; a free trial session does not. Payments run through your own Stripe or PayPal account, or Invoice Ninja, a payment link or cash, and Event Schedule takes zero platform fees at every plan level.
Paste one meeting link on the course and every session in the term joins through it, the way a recurring meeting room already works. Zoom, Google Meet, Microsoft Teams, YouTube Live, your own setup: it is a link field, so all of them work and none of them own you.
Your schedule lives at its own address. Put it in a bio, a signature, a course page, and it keeps being right when the term rolls over.
Embed the calendar in a page on your own site with an iframe. A list layout suits a term better than a month grid, and that is a setting.
The registration form can be embedded too, free. The ticket purchase form is the Pro version of that widget.
It is not a video platform and does not pretend to be. Event Schedule does not create the meeting, count who is in the room, take attendance from it, or hold recordings. It publishes the sessions, takes the registrations, and hands over your link. One link, for the whole term: if week four genuinely needs its own room, week four is a separate event.
Marked Free or Pro, honestly. Six of these eight cost nothing.
Students follow your schedule so you can write to them. Materials before, a recording link after, next term when it opens. Ten emails a month free, a hundred on Pro and a thousand on Enterprise, each recipient counting as one, with open and click rates.
Google, Outlook and CalDAV, both directions, so your teaching hours and the rest of your week sit in one calendar. A recurring term syncs across as its next session rather than as a repeating series; to see all twelve dates in a calendar app, subscribe to your schedule's calendar feed instead. Students can subscribe to the same live feed from your schedule page, with no email address, and it updates itself when a date changes.
Views, devices and where the traffic came from, per schedule. Enough to know whether the term filled from your newsletter or from somebody else linking you.
Break a class into named parts with their own times: warm-up, teaching, questions. It is the running order of a session, and on a term every session runs it.
Beginner, intermediate and advanced as separate strands of the same link, each with its own colour. They organise and filter; they do not hide anything, and a pass can be scoped to one of them.
Custom fields on the form collect what the course needs at the point of signing up: the level they think they are, dietary notes for a cooking class, a parent contact.
Save a term as a template and start next term from it, or clone last term outright. A template keeps the pattern and the twelve-session end; the holiday dates it deliberately does not keep, because those belong to the calendar and not to the course. A clone keeps them.
Every schedule has a QR code that points at it. Put it on the last slide of the deck and the people who liked the class can follow you before they close the tab.
Which list is which
Worth being precise about which list is which. Somebody who left an email address and confirmed it hears when you publish new classes, as one digest rather than a message per class. Somebody who pressed Follow from their own account is on the other list, and that one is reached only by a newsletter you write. There is no automation builder here either way: no branching sequence, no drip.
A term is a term whether it is verbs or knife skills. Also see Event Schedule for Webinars and Virtual Conferences.
Daily or weekly sessions with a cap per date, and a ten-visit card for the regulars who cannot make every one.
Newsletter the ingredient list to the people who signed up for the course, teach live, then write once more with the recipe.
A drawing term and a guitar term as separate sub-schedules on one link, each ending on its own last session.
Learn moreA twelve-week conversation class that stops after twelve, with holiday weeks taken out as date exceptions.
Learn moreBootcamps, workshops and study groups, kept in beginner and advanced strands so a card for one does not open the other.
A cohort that meets fortnightly, sold as a term membership, with the intake question asked at checkout.
Learn moreCreate the course as a recurring event, pick the night it meets, and end the recurrence after a set number of sessions or on a closing date.
Add date exceptions for the holiday weeks, and paste your class link on the course so students join from the schedule.
Set a seat cap counted per date, then take free registrations, or sell single seats and class cards with nothing taken off the top.
Free registration for as many people as you like. When you start charging, zero platform fees on every plan - the only deduction is your payment processor's own.
Everything you need to publish a schedule and fill the room, for as long as you like.
No expiry, and no card asked for.
Start charging, and the rest of the selling kit arrives with it.
7-day free trial, cancel any time.
For a room with a seating chart, a team, and a domain of its own.
Included free on every selfhosted install.
What instructors ask before they move a term across.
Yes. Setting a course up as a term, skipping holiday weeks, ending the recurrence after a set number of sessions, taking free registrations with a seat cap per session date, publishing one link, embedding your schedule, syncing two ways with Google, Outlook or CalDAV, sending newsletters to the students who follow you and reading your analytics are all on the free plan. Charging for a seat is not: paid ticket types, plus class cards and custom checkout questions, are the Pro plan at R199 a month, and Event Schedule charges zero platform fees on payments at any plan level.
Create the course once as a recurring event, pick the night it meets, and give the recurrence an end: after a set number of sessions, or on a closing date. A term that ends after twelve sessions stops on its own instead of repeating until somebody remembers to switch it off. Add date exceptions for the weeks you are off. Repeats can be daily, weekly, every few weeks, or monthly by date or by weekday.
Any platform that gives you a link. Zoom, Google Meet, Microsoft Teams, YouTube Live, or your own streaming setup. Being straight with you: this is one link field on the course, not an integration, and because the term is one recurring event that link is the same for all twelve sessions, the way a recurring meeting room already is. Event Schedule does not create the meeting, count who is in the room, or record anything. It publishes the sessions, takes the registrations, and puts your link in front of the people who signed up. If each week genuinely needs a different room, those weeks are separate events.
Yes, on the free plan. Set a seat cap on the course and it is counted per session date, so week three filling up does not close week four. When a session is full the register shows no seats left for that date and the sign-up button on that date becomes a waitlist instead. When somebody cancels, the first person waiting for that date is emailed and has twenty-four hours to take the seat before it passes to the next in line. The registration waitlist is free; the same waitlist on a sold-out paid date is a Pro feature.
Yes, on the Pro plan. A class card is a pass, and you choose how it counts: a fixed number of visits, like a ten-visit card, or a membership with unlimited visits until it expires. Set how many days it is valid for from purchase, how many people it admits at each session, whether holders reserve a date in advance or just turn up, and a cancellation deadline with a policy for late cancels. A pass can also be scoped to one sub-schedule, so a beginner card does not open the advanced track.
Yes, on the Pro plan, which is what lets a seat carry a price. Create as many named ticket types as the course needs, each with its own price and quantity: a drop-in seat, a concession rate, a free trial session that stays free on any plan. Payments run through your own Stripe or PayPal account, or through Invoice Ninja, a payment link or cash, so you keep everything except the provider's own processing fee. Event Schedule takes nothing.
Some do. A student who left an email address in the sign-up panel on your schedule page and confirmed it gets a digest of the new classes you publish, at most one every 72 hours, outside your newsletter allowance. Pressing Follow on its own sends nothing to an account follower automatically, so a student who did only that hears about a new class through a newsletter you write and send yourself: ten emails a month on the free plan, a hundred on Pro, a thousand on Enterprise, each recipient counting as one. Changes are a separate email. Change the class link and saving asks whether to tell everyone holding a seat on an upcoming session, and cancelling the course tells them as part of cancelling; those reach anyone who left an address on a session's page to hear about it, and registered students too, on eventschedule.com when your schedule sends through its own email settings. A new start time on a term does not trigger that question, because a term is one recurring event, so say it in a newsletter.
Yes, on every plan. Switch on the "Notify me" card, publish the course before you add its tickets, and its page offers "Tell me when tickets go on sale": a student leaves an email address, with no account and no name, and gets one email when seats for that session date go on sale, a reminder 48 hours before it, word if it is cancelled, and any change notice you choose to send. Each session date keeps its own list, unsubscribing deletes the address, and the Tickets panel on the course shows how many people are waiting. To hear about every new course instead, a student signs up in the panel on your schedule page and gets the digest.
Yes, from the Sales page, on Pro. A payment taken through Stripe or PayPal goes back through the provider, in full or in part. A partial refund leaves their seat or class card valid, and only a full refund cancels it and puts the seat back on sale. Payments taken by Invoice Ninja, a payment link or cash are marked as refunded instead, which records the refund without moving any money.
Free forever
Publishing your term, capping the seats and taking free registrations are free forever, with no monthly ceiling on any of them. Charging for a seat, and class cards, are R199 a month, and nothing is taken off what you charge.
No credit card required
Related
Announce classes, sell spots, and build multi-session series.
Read moreRegistration, ticketing, and a join link on any platform.
Read moreEvent scheduling for musicians, venues, restaurants and theaters.
Read moreSee what is included on Free, Pro, and Enterprise plans.
Read moreWe'd like to use optional cookies for analytics and for marketing, including maps and videos from other sites. Nothing optional is set until you choose. The organizer of a schedule page you visit also sees visits to it, without your name. Learn more