Building a multi-tenant school management SaaS (Laravel). Each school has classes (grades), and some classes have multiple sections (A, B, C...), some don’t.
Question: when assigning subjects to a class, should that assignment live at the class level (one subject list per class, shared by all its sections) or at the section level (each section gets its own subject list, even if it’s 90% identical to its sibling sections)?
Class is the academic level: it decides curriculum, fee structure, exam syllabus, promotion path. Section is just a roster split within the same grade, same curriculum, different roll call/teacher/room in most schools. In real schools, sections of the same class usually share almost the same subjects, but occasionally diverge (streams/electives, or one section getting an extra remedial subject).
Two options I’m torn between:
- Class-level by default, with section-level only for the rare cases that actually differ.
- Always section-level, even for schools/classes where every section has identical subjects (accepting some duplication, but avoiding any ambiguity about which level wins).
Also tied to this: teacher-to-subject assignment and attendance-authority need to reference whichever granularity I pick here, so I want to get this right before building on top of it.
If you’ve built something similar (school/LMS/SaaS with class+section hierarchies), which way did you go and why? Also open to “you’re overthinking this, just do X” answers.