Fictional studio example / annotated wireframe
An inspectable design specimen, not a client screenshot, completed provider integration or measured result. Interface choices illustrate the task described in this guide.
Show the class state before the booking action
Beginner print session
Who it suits → new participants
Materials → listed beside the session
Date and venue → shown before selection
The action retains the selected class.
No places available
Keep the date and class description visible. Explain whether a separate waiting list exists.
A waitlist request must not look like a booked place.
This session will not run
Identify the affected class and point existing attendees to the organizer's confirmed next step.
Do not invent refunds or replacement dates.
Show session dates, seat availability and booking states
Keep the class identity and session date together, then show available, full, request-only and conflict states accurately. Explain level, preparation and commercial conditions only from approved facts. The schedule is useful when a customer can choose the intended session and distinguish a confirmed seat from a request or waitlist.
Worked example — illustrative data.
| Session | Specimen state | Action |
|---|---|---|
| Beginner print session; Saturday 10:00 | Seats available in concept | Choose the actual session |
| Advanced print workshop; Sunday 14:00 | Fully booked | Use an approved waitlist if implemented |
| Private group session | Request only | Send group requirements for review |
| Selected seat no longer available | Conflict at confirmation | Choose another supported session |
Use the actual session identifier and time zone where it matters, not just a class title that repeats across dates. Show duration, level, venue, materials and age or access requirements only after the owner confirms them. Keep preparation instructions available after booking. Test the normal path and an exhausted-seat state with synthetic sessions. Verify that the confirmation matches the scheduler rather than assuming the page’s earlier availability remains current.
State whether a seat buys one session or a series
For the fictional print course, show all required dates before selection if the purchase covers a recurring series. Name the venue, level and preparation requirements beside that choice. Rehearse a fully booked session and an unavailable seat at confirmation. Keep waitlist membership distinct from a reserved place, with only the follow-up the provider actually supports.
A recurring series may require several attendance dates
A recurring class series may require attendance at several dates. Make the commitment explicit instead of letting the customer assume they purchased a single session.
Accept the page when the buyer can choose the intended session and distinguish confirmed, requested and waitlisted states. The fictional schedule establishes no actual availability or booking capability.
What should happen when a session is cancelled?
Show the actual cancellation state and a verified next step for existing attendees. Remove misleading purchase actions and preserve a useful destination for saved links. The business owner must supply the applicable change or refund policy; the page should not invent it.
Continue with Guides for stores, software teams and local businesses, Website design for local businesses and Plan an appointment business website.