Publish next week's classes and take sign-ups against each one. Describe your timetable and Taskade Genesis builds an app with a class per session, a capacity number, a sign-up form that attaches the person to the class they chose, and a places-remaining count your team can see at a glance.
The Class Booking Portal is a live Taskade Genesis app running on this page. Sign up for a session, see how a real class record behaves, then press "Use this app" to clone it in about ten seconds and shape the timetable, capacity, and weekly roll-forward described here around your own week.
Studios, gyms, community centres, and language schools all run the same shape: a repeating weekly grid, a cap per session, and a handful of people who sign up late. The failure mode is never the software, it is the gap between the timetable you published on Sunday and the reality on Wednesday when an instructor is ill. Keeping the schedule and the sign-ups in one app closes that gap, because cancelling a class and messaging everyone booked into it is the same action.
What the build gives you: a record per class with day, time, instructor, room, and capacity, a sign-up form where the attendee picks a class, a linked list of attendees per class, a running count of places taken and places left, waitlist overflow when a class is full, and a one-click message to everyone in a single class.
The same timetable renders in the layouts you need:
- Calendar view for the published week, which is the view you screenshot and post
- Table view for capacity, sign-ups, and places remaining across every session
- Board view to group classes by instructor or by room
- Plus List, Mind Map, Gantt, and Org Chart across the rest of the 7 project views
Automations keep the grid honest. The Form Submitted trigger adds the attendee and increments the count. A filter closes sign-ups when capacity is reached and diverts the next person to the waitlist. A scheduled trigger rolls next week's grid into place every Sunday evening and emails the timetable out. Across 100+ bidirectional integrations, forms and Stripe pull sign-ups and payments in while Gmail, Slack, and SMS push the timetable and cancellations out. Automations run on paid plans; the Free plan includes 10 flow runs in total.
The AI agents in the app carry 34 built-in tools including persistent memory and multi-agent collaboration. The Timetable agent drafts the weekly announcement, writes the class descriptions, and produces a short note for any session that is filling unusually fast or unusually slowly.
The number worth watching once this is running is fill rate per class, not total sign-ups. Total sign-ups tell you the week was busy. Fill rate tells you which sessions to keep, which to move an hour later, and which to quietly retire before an instructor spends another term teaching four people. Because capacity and sign-ups sit on the same record, that ratio is a column rather than a spreadsheet exercise.
Clone the app, invite your instructors, and the timetable is yours. Add a class, move a class, cancel a class, all in the same place your attendees are tracked.
Learn the calendar layout in Learn, recurring automation runs in Learn, and payment links in Learn. Browse live builds in the Community Gallery and start from a base in the templates library. Pair this with the paid workshop seat prompt when sessions are sold rather than free, and the waitlist backfill app so a drop-out is replaced the same day.
Frequently Asked Questions
Does this handle repeating classes automatically?
A scheduled automation can roll your standard weekly grid forward, creating next week's class records from your template on a set day. You then adjust the exceptions by hand, which is almost always faster than describing every exception as a rule.
How does capacity work?
Each class record carries a capacity number and a sign-up count. When the count reaches capacity the automation stops accepting sign-ups for that class and sends the next person to the waitlist instead, with a message that says so plainly.
Can attendees see how many places are left?
You can publish a view that shows the count. Many operators deliberately show it only when a class is nearly full, since a low number is a good nudge and a high number of empty places is not.
What if I have to cancel a class at short notice?
Change the class status to Cancelled and the automation messages everyone attached to that class in one step. That single action is the strongest argument for keeping the timetable and the sign-ups in the same app.
Can I charge per class or sell a block?
Both. Attach the Stripe Checkout Session action to a single sign-up for pay-as-you-go, or track a purchased block of credits on the attendee record and decrement it per class, which is covered in the session package prompt.
Can each instructor manage their own classes?
Yes. Invite them to the workspace and filter their view to their own sessions. Roles run from Owner through Viewer, so an instructor can mark attendance without being able to change your pricing.
Does it work for one-off events as well as weekly classes?
Yes. A one-off is just a class record that no weekly roll-forward touches. Many timetables are a mix, and mixing them in the same app is what makes the Calendar view genuinely useful.
Can I track attendance, not just sign-ups?
Yes. Add an Attended flag per attendee and mark it on the day. The gap between signed up and attended is the number that tells you whether your classes need reminders, a deposit, or a different time slot.
