Academic Setup
Configure sessions, classes, subjects, calendar, timetable, chapters, and academic planning.
Overview
Configure sessions, classes, subjects, calendar, timetable, chapters, and academic planning.
Before you start
- School setup completed
- Academic permissions assigned
Main screens
Step-by-step workflows
Prepare academic structure
- Create or verify the active academic session.
- Configure classes and A-Z sections.
- Add subjects and assign them to classes.
- Configure optional subjects where needed.
Plan calendar and timetable
- Add calendar events and holiday ranges.
- Create academic periods.
- Assign class timetable rows.
- Review teacher timetable conflicts and dashboard summaries.
Operational detail
Academic session
Keep one current session active for normal operations. Historical sessions should be selected only when reviewing previous-year records.
Classes and sections
Create classes first, then add simple A-Z sections. Unsupported section names are rejected to keep attendance and exam placement stable.
Subjects
Define subject name, code, type, optional status, and class assignment before timetable, homework, and exams use the subject.
Chapters
Chapters organize teaching plans, question bank records, homework, and paper templates. Keep chapter labels clear and syllabus-friendly.
Calendar
Use calendar events for holidays, exams, and school events. Weekly off-days remain controlled by attendance settings.
Timetable
Assign periods, subjects, and teachers carefully so teacher timetable and conflict reviews stay meaningful.
- Current session should be selected by default in session dropdowns.
- Class-section relationships are validated before dependent records are saved.
- Calendar date ranges must be valid and school scoped.
- Timetable rows should reference configured periods, classes, sections, subjects, and teachers.
- Creating duplicate or non-standard section names.
- Adding homework or exam records before assigning subjects to the class.
- Using calendar holidays to replace weekly-off settings.
- Changing core academic setup after attendance or exam records already depend on it without reviewing impact.
Safe use
These guides explain normal user workflows only. Do not share passwords, OTPs, tokens, cookies, private student identifiers, payment details, raw internal IDs, provider configuration, or stack traces in support messages or screenshots.
- Creating duplicate or non-standard section names.
- Adding homework or exam records before assigning subjects to the class.
- Using calendar holidays to replace weekly-off settings.
- Changing core academic setup after attendance or exam records already depend on it without reviewing impact.