The rule for multi-course students: one permanent ID, multiple memberships. The student is a person; course memberships are relationships. Creating a new “student” per course splits the file — attendance, marks and fees scatter across three places, and none of the questions (“which batches, total dues, total courses”) has an answer.
What to verify: one identity with multiple enrolments; avoiding duplicates
The structure:
| Level | Example | Rule |
|---|---|---|
| Student (ID) | student-31 | a person exists once |
| Membership 1 | SSC Maths, 7 PM | batch + fee structure |
| Membership 2 | SSC Physics, 8:30 PM | separate batch, separate fee |
Verification rule: at enrolment into a new course, the system should search for an existing student by name+number and offer to add a membership instead of creating a duplicate. No match: verify spelling, then a new ID.
A usable sample: the synthetic student-course map
Student-31’s map:
| Membership | Batch | Slot | Fees | Attendance |
|---|---|---|---|---|
| Maths | SSC-M | 7 PM | paid | 92% |
| Physics | SSC-P | 8:30 PM | partial | 85% |
From this view, one-shot answers: how many batches, total dues, slot conflicts (via the matrix), and whether a student is strong in one batch but weak in another — possibly a teaching-method issue.
Multi-course records: workflow steps and limitations
- Write the duplicate-catching rule: name + guardian number matched → treat as same student and ask.
- Show the student-level total bill (all courses) to guardians — per-batch separate bills confuse.
- Dropping a course closes the membership, not the student file.
- Limitation: different name + different phone defeats duplicate detection 100% — keep a month-end duplicate check running.
Course records: questions to ask before your demo
- One student in multiple batches — have them demo it.
- Does a student-level total dues figure (across batches) exist?
- Is there a duplicate warning?
See the coaching page for the multi-course structure; student management features for profile structure and the attendance module for conflicts.
Course records FAQ
Should both courses be billed together or separately?
One total bill for the guardian is clearest; course-level tags stay inside the accounts.
Can both courses’ attendance be seen in one place?
It should be — a student-level view; ask in the demo.
A duplicate got created — how do we remove it?
Export data from the wrong ID first, then merge into the correct one — do not delete outright; sales records should survive.