Student Lifecycle › Rooms & Exams
Rooms & Timetabling
Rooms that cannot be double-booked, and a timetable built to keep it that way.
In Student Lifecycle → Rooms & Exams · 9 screens
WorkspaceTimetableThe timetable as a calendar — week, day or month — for you, a section, a teacher, a room, a student or a programme; each class opens its register. The weekly pattern, with the clashes marked, is one press away.OpenRecordsRoomsEvery room that can be timetabled or examined in: seats, exam seats, type, equipment, step-free access and opening hours. A room is booked by the timetable, never typed.OpenRecordsBuildingsThe buildings rooms are in, each on a campus.OpenRecordsRoom BookingsOne-off events asked for a room: a guest lecture, a society, an interview day. Approved, a booking holds the room like a class does; a clash is refused when it is approved.OpenRecordsRoom ClosuresDates a room cannot be used: refurbishment, an open day, a fault. The timetable and bookings are refused over them.OpenRecordsMeeting PatternsWhat the timetable builder is asked to place for a section: hours a week, session length, preferred days, room type and equipment. A section without one keeps the shape of the meetings it has.OpenRecordsTimetable RunsThe automatic builder: build a conflict-free timetable for a term as a preview, see what it could not place and why, then apply it or throw it away. Exam scheduling runs land here too.OpenReportTimetable ClashesEvery clash on file: a room or an instructor in two places, students in two sections at once, a room with fewer seats than the section. Empty is the goal.OpenRecordsScheduling SettingsWhether an over-full room warns or is refused, whether student clashes are checked, the teaching day the builder works in, and the exam rules.Open
Columns, fields and actions
| Screen | Kind | What it is | Columns | Fields | Actions |
|---|---|---|---|---|---|
| Timetable | Workspace | The timetable as a calendar — week, day or month — for you, a section, a teacher, a room, a student or a programme; each class opens its register. The weekly pattern, with the clashes marked, is one press away. | 0 | 0 | 0 |
| Rooms | List | Every room that can be timetabled or examined in: seats, exam seats, type, equipment, step-free access and opening hours. A room is booked by the timetable, never typed. | 10 | 17 | 0 |
| Buildings | List | The buildings rooms are in, each on a campus. | 7 | 7 | 0 |
| Room Bookings | List | One-off events asked for a room: a guest lecture, a society, an interview day. Approved, a booking holds the room like a class does; a clash is refused when it is approved. | 9 | 8 | 3 |
| Room Closures | List | Dates a room cannot be used: refurbishment, an open day, a fault. The timetable and bookings are refused over them. | 5 | 4 | 0 |
| Meeting Patterns | List | What the timetable builder is asked to place for a section: hours a week, session length, preferred days, room type and equipment. A section without one keeps the shape of the meetings it has. | 9 | 13 | 0 |
| Timetable Runs | List | The automatic builder: build a conflict-free timetable for a term as a preview, see what it could not place and why, then apply it or throw it away. Exam scheduling runs land here too. | 10 | 0 | 5 |
| Timetable Clashes | Report | Every clash on file: a room or an instructor in two places, students in two sections at once, a room with fewer seats than the section. Empty is the goal. | 0 | 0 | 0 |
| Scheduling Settings | List | Whether an over-full room warns or is refused, whether student clashes are checked, the teaching day the builder works in, and the exam rules. | 7 | 10 | 0 |