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.
- Placement Cell Management
- Data model and migration order
The tables behind Placement Cell Management
Placement Cell Management ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 12
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Learner and staff identity:
Learners, People and Users hold the people involved in learning and operations.
Course delivery:
Courses, Enrollments and class sessions connect a learner's place to instructor-led sessions.
Learning evidence:
Attendance, Assessments and assessment results connect teaching and graded results to the learner.
Learner finance:
Fees records the obligation, due date and paid amount for a learner.
Placement activity:
Recruitment drives links a drive to Enrollments; student applications links a learner to a drive.
Every table, by feature
- Enrollments4
- Courses and sessions5
- Learning outcomes6
- Fees3
- Recruitment drives5
- Student applications4
- Shared and settings1
- Enrollments
Learner enrollment in a course and its lifecycle state.
Linked to Learners, Courses - Learners
Learner records from applicant through completion.
- Courses
Course catalog with instructor, capacity and delivery window.
Linked to People - Class sessions
Scheduled class sessions for each course.
Linked to Courses
- Courses
Course catalog with instructor, capacity and delivery window.
Linked to People - Class sessions
Scheduled class sessions for each course.
Linked to Courses - People
Staff and faculty referenced by courses and authenticated roles.
Linked to Users - Enrollments
Learner enrollment in a course and its lifecycle state.
Linked to Learners, Courses - Attendance
Per session and learner attendance capture.
Linked to Learners, Class sessions
- Attendance
Per session and learner attendance capture.
Linked to Learners, Class sessions - Class sessions
Scheduled class sessions for each course.
Linked to Courses - Assessments
Assessments defined for a course with maximum score.
Linked to Courses - Assessment results
Learner scores against an assessment with grading state.
Linked to Assessments, Learners - Enrollments
Learner enrollment in a course and its lifecycle state.
Linked to Learners, Courses - Learners
Learner records from applicant through completion.
- Fees
Learner fee obligations, payments and status.
Linked to Learners - Learners
Learner records from applicant through completion.
- Enrollments
Learner enrollment in a course and its lifecycle state.
Linked to Learners, Courses
- Recruitment drives
Employer recruitment drives run for an enrollment cohort.
Linked to Enrollments - Enrollments
Learner enrollment in a course and its lifecycle state.
Linked to Learners, Courses - Learners
Learner records from applicant through completion.
- Courses
Course catalog with instructor, capacity and delivery window.
Linked to People - Student applications
Learner applications to recruitment drives through offer and acceptance.
Linked to Learners, Recruitment drives
- Student applications
Learner applications to recruitment drives through offer and acceptance.
Linked to Learners, Recruitment drives - Recruitment drives
Employer recruitment drives run for an enrollment cohort.
Linked to Enrollments - Learners
Learner records from applicant through completion.
- Enrollments
Learner enrollment in a course and its lifecycle state.
Linked to Learners, Courses
Keys and references
Use stable learner number and course code values when reconciling imports. Enrollments connects Learner and Course. Recruitment drives.operational record points to an Enrollments record, while student applications.Learner and student applications.Drive identify the candidate and opportunity. Assessment results.Assessment points to Assessments, and Attendance.Session points to class sessions. People.User maps a staff record to Users.
Do not treat a saved list screen as another table. Its filters select rows from the source table below. Preserve source identifiers during imports so a duplicate learner-drive application or employer-role-date drive can be investigated against the original record.
Migration order
- Load Users and People, then Learners and Courses with stable identifiers.
- Load class sessions and Assessments after their Courses references resolve.
- Load Enrollments, then Attendance, assessment results and Fees after their learner and course references resolve.
- Load recruitment drives after their Enrollments references resolve.
- Load student applications after both Learners and recruitment drives resolve; reconcile saved states and sample decisions.
Set up Placement Cell Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.