1. Timetable Generator
  2. Implementation and migration
Reference

How a Timetable Generator rollout works

Start with one site or department and one term your coordinator, instructors and administrators can check together.

  1. Agree the operating boundary

    The app runs courses, rooms, timetable slots, sessions, enrollments, attendance, assessments and fees. Learning content, payment collection and external room booking remain connected systems. Your coordinator approves slots and your administrators approve enrollments; Proto prepares information and configuration for review.

  2. Map the source data

    Gather rooms with capacity, equipment and unavailable times, instructors, courses with capacity and dates, learners and current enrollments.

  3. Configure a bounded pilot

    Pilot one site or department for one term. Propose, approve and publish every slot, enroll learners and record attendance.

  4. Rehearse the exceptions

    A room clash must be refused. An instructor double-booking must be refused. A full course must not take another enrollment. A score above the maximum must be refused.

  5. Reconcile and release

    Compare the published timetable, enrollments and fees with your current records. Obtain sign-off from the Timetable Coordinator and the Academic Administrator, keep an export of the source and agree the rollback window before the term starts.

What the customer provides

  • Rooms with capacity, equipment and unavailable times.
  • Instructors and staff with their user emails.
  • Courses with codes, capacity, dates and instructors.
  • Learners, current enrollments and the fee schedule.

Changing it afterwards

Use Proto to prepare changes on a branch. Review the changed fields, affected permissions, import mappings and reports with their owners. Replay the pilot’s exception cases before release. Published timetables of past terms keep their original slots.

Prepare your first configuration.

Set up Timetable Generator your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started