Sign in
Use your institutional account to continue.
Initial bootstrap admin:
admin@university.edu
Use your institutional account to continue.
admin@university.edu
| Name | Email (Identity) | On Campus | Address | Actions |
|---|
Courses encode canonical teaching demand. L-T-P workload values and room-type preferences are converted into session requirements during scheduling preparation.
Field semantics: L-T-P represents lecture/tutorial/practical weekly hours; Credits is derived from workload; optional room preferences shape placement feasibility.
CSV columns: code, name, department, lecture_hours, tutorial_hours, practical_hours, course_category, optional expected_enrollment, required_consecutive_slots, preferred_room_type, description.
Uniqueness: code is unique. Missing or duplicate codes are rejected or skipped.
Downstream effect: course definitions drive session creation, faculty-course eligibility, and course-room eligibility.
| Code | Name | Department | L-T-P | Credits | Actions |
|---|
Batches represent formal learner cohorts (program + year + size). They provide the demand side of timetable allocation and cohort-level workload balancing.
Downstream effect: planner filtering, course assignment scope, and session audience targeting depend on batch definitions.
Relationship to Student Groups: student groups can represent full batches or derived sub-cohorts used by session-centric modeling.
| Name | Program | Year | Total Students | Actions |
|---|---|---|---|---|
| No batches yet | ||||
| S No | Number | Capacity | Location | Primary School | Type | Projector | Actions |
|---|
Planner compiles institutional intent into session mappings by linking course demand, eligible cohorts, and faculty assignment decisions.
Each step narrows the feasible scheduling domain: cohort selection defines demand scope, and faculty mapping defines candidate instructors.
Program and year identify the institutional cohort receiving the planned sessions.
Define your school's weekly rhythm: working days, start/end windows, and lunch breaks.
Build a reusable school schedule template first, then apply or adjust day-level blocks.
CSV columns: day, slot_index, start_time, end_time, is_lunch.
Each (day, slot_index) should be unique within a template.
| Day | Slot | Start | End | Lunch |
|---|
Sessions are the primary scheduling units. A session represents one recurring instructional activity with course identity, delivery type, student audience, and eligible instructors.
Downstream effect: generator feasibility, workload distribution, and room-time placement all operate on these session definitions.
Student groups encode who attends a session. Use batch for formal cohorts, cohort for grouped populations, and derived for split or synthetic subsets.
Groups CSV columns: code, label, group_type, program, year, size.
Uniqueness: code is unique. Existing group codes are skipped in bulk upload.
| Code | Label | Type | Program | Year | Size | Actions |
|---|
Session field semantics: Type is L/T/P modality, Duration is hours per occurrence, Occ/Wk is weekly repetition, and Consecutive slots is a hard continuity requirement.
Sessions CSV columns: name, course_code, session_type, duration_hours, occurrences_per_week, required_consecutive_slots, preferred_room_type, group_codes, eligible_faculty_emails.
Multi-value columns use | separators for group_codes and eligible_faculty_emails.
Uniqueness assumption: no strict unique key is enforced for session rows; avoid duplicate logical definitions in the same planning cycle.
Downstream effect: this dataset becomes the direct input domain for scheduling allocation.
| Name | Course | Type | Duration | Occ/Wk | Consecutive | Preferred Room | Groups | Eligible Faculty | Actions |
|---|
Eligibility matrices encode institutional permission boundaries. They prevent invalid assignments before optimization scoring is attempted.
Faculty-course matrix semantics: each allowed pair means a faculty member is permitted to teach that course.
Faculty-course CSV columns: faculty_email, course_code. Faculty identity is resolved by canonical faculty email.
Course-room matrix semantics: each allowed pair means a course may be timetabled in that room.
Course-room CSV columns: course_code, room_number. Uniqueness assumption: each pair should appear at most once.
Downstream effect: both matrices prune infeasible faculty and room candidates during generation.
A chronological library of scheduling workspaces.
| Name | Actions |
|---|
Manage Locations is the canonical campus geography editor. Coordinates are optional during transition, but they enable map rendering and automatic walking-time estimates.
| Short Name | Full Name | Latitude | Longitude | Actions |
|---|
The values below represent approximate walking time in minutes between locations.
This page is for administrator controls only. It manages global display, access, PDF, and recovery settings.
Bootstrap administrator email: Loading...
Loading authentication settings...
This image appears on the login screen and inside the app.
Choose which modules are visible to faculty users.
Required room capacity equals effective activity demand multiplied by this percent. Default 100 requires the full demand.
Faculty Dashboard
Loading your faculty dashboard…
Workspace
Workspace access for your account.
My Preferences
Share scheduling guidance for your selected planning workspace, and review it after publication.
Loading your preferences…
Faculty Settings
Update your residence details and password for your own faculty account.