These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Timetable Generator
- Features
- Enrollments and learners
Enrollments and learners
Keep learner records and approve each enrollment only after eligibility and course capacity are checked.
OverviewEnrollment Requests×
Timetable Generator · Enrollments and learners
New
Enrollment Requests
Approval waits for the academic administrator
| Learner | Course | Enrolled at | Status | |
|---|---|---|---|---|
| LRN-80711 | CRS-7613 | 06 Oct | Requested | |
| LRN-59311 | CRS-5525 | 12 Oct | Requested | |
| LRN-27933 | CRS-1072 | 15 Oct | Requested | |
| LRN-37043 | CRS-5895 | 05 Oct | Requested | |
| LRN-97970 | CRS-8503 | 16 Oct | Requested |
6 of 6 records
LRN-80711Enrollments · ENR-64976
RequestedCourseCRS-7613
Enrolled at06 Oct
What you can do
Admit learners only where there is room
A learner record holds the learner number, name, email, admission date and status: Applicant, Enrolled, Paused, Completed or Withdrawn. An enrollment links one learner to one course and moves from Requested to Approved, Active and Completed, or ends as Withdrawn.
The Academic Administrator approves enrollments. Before approving, the administrator checks that the learner is eligible and that the course still has room against its capacity. There is exactly one enrollment per learner and course, so a repeated request does not take a second place. On approval the learner becomes Enrolled and can see the course’s sessions.
How the work is organized
- Request. An enrollment starts as Requested for one learner and one course.
- Approve against capacity. The administrator checks eligibility and remaining places and approves. A full course cannot take another learner.
- One place per learner. Each learner holds one enrollment per course. A withdrawal keeps the history.
What to agree during setup
Agree eligibility rules for each course, such as prerequisites or admission status. Agree how learner numbers are issued. Decide what happens when a course is full: a waiting list kept outside the app, or a second course section. Agree who may withdraw a learner and what reason must be given.
Check the handoff on an actual case
Data Analysis 101 has capacity 20. Nineteen enrollments are active when two requests arrive on the same morning. The administrator approves the first: the learner meets the prerequisite, and the course now has 20. The second request cannot be approved because the course is full. The administrator tells the learner and suggests the evening section.
The first learner’s request is sent again by mistake an hour later. Because there is already one enrollment for that learner and course, no second place is taken. In April the learner pauses studies; the enrollment is withdrawn and the learner marked Paused, with the attendance history kept.
What your team sees
- Enrollment Requests — Requested enrollments waiting for the administrator’s decision.
- Active Enrollments — Approved and active enrollments by learner and course.
- Learner Register — Applicants, enrolled and paused learners with number, email and admission date.
Follow the work through
- Enrollment request to active learner: Approve the enrollment against capacity.
Check roles and permissions before go-live.
What it keeps track of
Data model- Enrollments
- Learner to course enrollment lifecycle.
- Learners
- Learners enrolled in courses.
- Courses
- Course catalog with instructor, capacity and delivery window.
Who uses it
Permissions- Academic Administrator
- Maintains learners and approves enrollments.
- Instructor
- Reads enrollments for their courses.
- Finance Officer
- Reads enrollments when issuing fees.
- Admin
- Corrects records and access.
Set up Timetable Generator your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.