Exam Management for Multi-Campus Institutions

The platform separates the academic layer from the regulator layer. A group running CBSE campuses in India, IB campuses in Dubai, and a UK sixth-form site keeps three distinct curriculum tracks with the appropriate regulator template attached to each. Result documents render in CBSE mark-sheet format for Indian campuses, IB predicted-grade format for Dubai, and JCQ result-slip format for UK, all from the same group instance. UGC AISHE and KHDA inspection reports generate from their respective campuses only.

Every question paper download is watermarked with the campus name, user ID, and timestamp. When a leak surfaces, the watermark identifies the download event that produced it. Access logs are immutable and audit-logged. Group policy typically restricts question paper access to two named campus roles (exam controller and deputy) with a mandatory disclosure log for every open, print, or share event. Leak forensics is traceable within minutes, not days.

Benchmarking is curriculum-cohort-scoped. A group running CBSE in Delhi, IGCSE in Bengaluru, and A-Level in Dubai sees within-CBSE benchmarking across CBSE campuses, within-IGCSE across IGCSE campuses, and within-A-Level across A-Level campuses. Cross-curriculum score comparison is explicitly blocked because the exam boards, grade boundaries, and standards are different. The group dashboard separates each curriculum into its own view with the option to see programme-outcome parallels where they exist.

Yes. Per-campus exam operations is a core design principle. Each campus exam controller has a view scoped to their campus and only their campus. They schedule exam sessions on the campus calendar, roster campus invigilators, assign campus halls, and distribute answer sheets from the campus store. Group HQ sees the group-level schedule as observation-only. If a campus needs to reschedule because of local flooding, teacher strike, or public holiday, the change is local and does not require group-level approval.

Group policy chooses one of two patterns. Pattern A: results release simultaneously at a group-fixed UTC timestamp so no campus sees results before another. Pattern B: results release per campus timezone at a locally-configured time. Universities on Pattern A prevent screenshot leaks across timezones; K-12 groups often prefer Pattern B so the local-morning result declaration ceremony works at each campus. Both are configurable per exam cycle.

Cross-campus transfer is a one-click workflow. Source campus initiates the transfer, target campus accepts, and the student record moves with full academic history, internal-assessment marks, subject choices, predicted grades, and pastoral notes. The target campus can view the source campus grade-boundary policy if it differs from theirs. Transfer preserves the exam registration for external boards (CBSE, IB, A-Level) with the appropriate change-of-centre notification generated for the board.

Group-level grade boundaries are enforced at result-processing time. When a campus attempts to process results with campus-set boundaries that deviate from group-approved boundaries, the platform flags the deviation and requires group academic council approval to proceed. Common use case: Campus A wants to award more A grades to prop up admissions marketing; group academic council refuses; the platform enforces group boundaries automatically. Board-approved policy is not negotiable at campus level.

Standard reports include UGC AISHE annual return for Indian university groups, NAAC institutional accreditation dataset, NIRF ranking data submission, CBSE affiliation report for K-12 chains, KHDA inspection data for UAE school groups, ADEK inspection data for Abu Dhabi, Ofsted MIS export for UK academy trusts, and CIS accreditation evidence for international school groups. Reports pull from group-consolidated data with campus-level drill-down for any inspector query.