Roll a class timetable into the next term

Align the timetable and the intake period

A timetable showing April sessions is inconsistent with a form still offering March trial dates. Include course descriptions, trial availability and post-enquiry instructions in the same release scope. Existing students may need historical material, so the goal is not to erase every old date. Distinguish currently bookable information from a previous-term reference. This guide covers the recurring rollover after a classroom’s initial trial page exists. Treating the job as a date replacement misses the connected choices a prospective student makes before submitting an enquiry.

Separate term and course identifiers

Store term ID, course ID, day, start and end, intended audience, venue, instructor and intake destination. A course name can remain the same while its schedule or audience changes, so do not overwrite records by display name alone. Preserve the old term and prepare separate next-term entries to make differences reviewable. If displaying capacity or remaining places, specify the authoritative source and the time the information represents. Keep unconfirmed times or instructors awaiting review rather than filling them with last term’s values just to make the new table look complete.

Review a term-to-term difference list

List added, retired, rescheduled and relocated courses. Similarity to last term is not approval of every field. Have the course or classroom owner verify the differences and give the publisher settled values. In a CMS, preview the next term as a draft and understand how the release handles old and new entries. Webflow distinguishes saved draft changes from published content; choose a procedure that matches the project’s actual configuration. Check for unrelated pending work as well. The rollover request does not authorise publication of every change another editor has already saved.

Prepare destinations before exposing new choices

Prepare the next-term form, response message and destination register before showing new choices. Submit fictional entries and verify the correct term ID, then connect the timetable and course pages. If both terms accept requests during an overlap period, label the term in the form explicitly. Closing an old intake must not accidentally remove the contact route existing students still need. Minimise the window in which a new timetable points to an old form. If an atomic switch is not practical, provide clear interim guidance rather than leaving visitors to infer which date is valid.

Give visitors to old schedules a useful route

If retaining an old timetable, identify its term, state that its intake is closed and link to the current schedule. Instead of sending every old URL to the homepage, consider the reader’s original course-level intent. People can arrive through distributed PDFs, social links and old emails. Align downloadable document versions with the relevant term and prevent an old application form being mistaken for the new one. Attendance history is a separate record and should not be deleted merely because the public timetable rolls forward. Archive design and operational data retention need their own decisions.

Choose tools for the actual rollover workload

A few rollovers each year may need only the existing editor and a difference checklist. Many courses and several owners can justify CMS fields and an approval queue. Compare editor seats, retained-term capacity, forms and notifications as well as course count. Clear labelling of old and new intake may prevent more errors than elaborate branching in one form. If adding synchronisation, define the authoritative source and recovery process so each term does not require rebuilding the integration. The purpose of the tools is consistent public choices, not a technically impressive schedule nobody can safely update.

Verify the full enquiry path

Test arrival from an old schedule, a next-term choice, a closed session, a differently targeted course, a narrow screen and both languages if offered. A fictional enquiry must carry the correct term ID and course ID, with matching dates in the reply. Inspect the organiser’s destination list as well as the public page. Completion means the published timetable reaches the right intake and the old version still offers a useful current route. The related trial-page, registration and CMS change-management guides support those neighbouring tasks without mixing historical records into the public rollover.

• Create a trial-class request page
• Collect workshop applications with Tally
• Control content changes during a CMS migration