Put your class timetable online as readable text, with a clear date range, venue and action for each bookable session. Keep one authoritative schedule and assign someone to maintain it. A timetable is only useful if a visitor can tell which programme is current and what happens when they choose a class.
A poster can remain a useful download, but it should not be the only way to find the dates. For adult classes in Formby or Freshfield, a visitor on a phone may need to check the next session and its location while making plans away from home.
Decide which system holds the real schedule
If the booking service holds dates, capacities and reservations, treat it as the source for those facts. The website can explain the class and display or link to the relevant schedule. Check whether an embedded timetable genuinely stays in step with the account; do not assume an attractive calendar is connected to live bookings.
If you accept enquiries manually and keep the schedule in WordPress, identify the person who approves changes and the place where confirmed updates are recorded. Avoid a separate spreadsheet, poster and web page all being treated as equally current.
Write down which details are copied and which are connected. For example, a class description might stay on the website while a “Choose a date” link opens the booking service. The organiser still needs to check that the link points to the intended activity after the next programme is created.
Use a list for a small programme and a table for real comparisons
A short list of dated sessions often works better than a weekly grid. Each entry can show the class name, full date, time, venue and booking action without forcing a reader to scan several empty days. Add a heading for the period covered, including the year when dates could otherwise be ambiguous.
A table is useful when readers need to compare several regular sessions by day or time. Keep the columns short. This fictional example shows the information to supply; the actual timetable would link each session to its current class or booking page.
| Session | When and where |
|---|---|
| Watercolour introduction | Tuesday 10am–12 noon, during the published course dates. Studio A. Whole-course booking. |
| Open pottery practice | Thursday 6–8pm, on listed dates only. Studio B. Reserve an individual session. |
The W3C table tutorial explains how captions and marked-up header cells help communicate a table’s relationships. Ask the designer to keep those relationships when the layout narrows, rather than turning a data table into an unlabelled collection of numbers.
Keep the timetable readable without opening a picture
Text inside a poster does not behave like ordinary page text when someone changes its size or appearance. W3C recommends using text rather than images of text when the same presentation can be achieved that way. Publish the essential schedule in the page, then offer the poster as an optional download if people use it.
Do not try to fit an entire busy week into a tiny phone screen. Use a simpler list, an appropriate filtered view or a table contained within its own scrolling area. Keep the class identity visible enough that the reader does not lose track of which time belongs to which activity.
Check more than the appearance. Can a keyboard user reach each class link? Do links such as “View Tuesday watercolour dates” make sense when read separately? Our accessibility first-pass checklist gives a practical starting route; it is not a full accessibility assessment.
Show breaks and changes at the affected session
“Every Tuesday” is misleading if the class pauses during part of the term. List the actual course dates or provide an explicit date range and clearly stated exceptions. Put a venue change alongside the affected date, not only in a general news post that timetable visitors may never see.
Give a cancelled session an understandable state and remove its joining action. Where someone has already booked, use the organiser’s agreed notification process as well; editing the public page does not establish that attendees have received the change.
For a sold-out session, offer only the actions you actually support: view another date, join a real waiting list or ask about a future programme. Explain what a waiting-list request means. It should not look like a confirmed reservation.
Make the button match what the participant reserves
A link labelled “Book this session” should not open a general programme containing several similar activities without explanation. If a direct link is available, use it. Otherwise tell the visitor which course or date to select and check that the provider’s page uses matching names.
A course, a drop-in place and a class pass make different promises. Buying credits may leave the participant needing to reserve dates separately. Our guide to course places, drop-ins and passes explains the distinction and the mixed-capacity checks to ask a supplier to demonstrate.
Keep availability claims within the system that maintains them. A static “only two places left” message can outlive the bookings it describes. A current booking page is a better place to show a live count if the provider supports it.
Use event pages only where they serve the programme
A one-off public workshop may deserve its own page with a specific date, venue and description. A recurring weekly timetable serves a different browsing task. Do not create dozens of near-identical pages just to repeat a place name.
If event structured data is proposed, Google’s event guidance requires an individual event URL and focuses on pages about one event, rather than a page listing a whole schedule. Eligibility has further conditions. Adding markup does not guarantee a special search appearance or more bookings.
Rehearse an update before handing over the site
Ask the person maintaining the programme to try four changes in an agreed test environment: move one date, change one room, mark a session unavailable and publish the next programme. Check the class page, timetable, booking destination and any downloadable version after each change.
Keep a small update record with the affected session, approved change, person responsible and date checked. Schedule reminders in your own working process for expiring programmes; a “last updated” label is only helpful when it reflects an actual review.
If your timetable needs a wider rebuild, the class and workshop website brief shows how to connect it to useful class descriptions. For help planning the website work, send Formby Web Design your existing timetable and explain where dates are maintained and how people join.
