Academics & Admissions

Academic structure

Set up once per session: academic sessions, terms, classes, arms (e.g. “JSS 1 Gold”), subjects, and wings (sector groupings like Nursery, Primary, Secondary, Tahfeez — see Multi-Campus for how these interact with campuses). Everything downstream — attendance, exams, timetabling — is scoped to this structure.

Admissions pipeline

A full applicant lifecycle: a public application form (no login required), document upload, entrance exam scheduling, screening/scoring, and offer/enrollment. Staff work the pipeline from the Admissions Pipeline sidebar view — see every applicant’s stage, review submitted documents, and move them forward.

Document OCR

When an applicant uploads an identity document (birth certificate, ID card, passport photo), iSchool can automatically extract the name, date of birth and document number as a suggestion attached to the file for staff to review — never auto-verified. Document verification (pending/verified/rejected) always stays a deliberate human action. This requires a configured vision provider — see Getting Your API Keys.

Entrance exams

Schedule entrance exams, generate applicant-specific access, and record results — all feeding into the same pipeline the screening team already works from.

Student roster

The single source of truth for enrolled students: admission number, class/arm placement, guardian contacts, and enrollment history across sessions. Every other module — attendance, exams, finance, discipline — references the roster rather than keeping its own copy of student identity data.