The CBSE Compliance Calendar: Every Submission, Deadline and Portal a School Office Owns in an Academic Year

It's the third week of September, and the exam coordinator is on hold with the CBSE regional office for the second time this week. A student's subject combination went into the LOC as Political Science instead of Psychology — a one-letter typo three data-entry steps upstream — and the correction window closed nine days ago. The admit card, when it eventually arrives in February, will carry the wrong subject. Fixing it now means a formal request, a covering letter from the principal, and a wait that stretches into the exam season itself.

Nobody in the office did anything unusual. They filled a form under deadline pressure, the way schools do every August. The problem isn't diligence — it's that CBSE's compliance calendar doesn't announce itself as a calendar. It arrives as a string of unconnected circulars, each with its own portal, its own login, and its own owner, and the connections between them only become visible after something breaks.

This piece maps the whole year in one place: what each portal wants, who in the office should own it, when it opens, and — most usefully — which five deadlines get missed most often, and the single habit that causes all five.

Direct Answer:

CBSE compliance runs across five interconnected systems — OASIS/UDISE+ for base student and staff data, Pariksha Sangam for everything exam-related, SARAS for affiliation, the school's own website for Mandatory Public Disclosure, and the AIM portal for APAAR ID monitoring — and nearly every deadline problem traces back to treating these as five separate annual chores instead of one continuously maintained record.

Quick-Scan Parameter - the year at a glance:

(Exact dates shift every session and are announced by circular — treat the months above as planning anchors, not fixed dates. Bookmark our Calendar & Circulars page, which we refresh as each notification lands.)

How CBSE Compliance Actually Works: The Portals, and Who Owns Each

Most school offices experience CBSE compliance as a sequence of surprises. In reality, it's five systems that hand data to each other in a fixed order, and knowing the order is most of the battle.

OASIS / UDISE+ is the foundation. It holds the base record of every student and teacher — names, qualifications, staff changes — and CBSE expects it kept current all year, not refreshed once before a deadline. Nearly every later submission pulls from this data, so an error here doesn't stay contained; it travels.

Pariksha Sangam is the portal most offices actually think of as "CBSE work." It hosts registration for Classes 9 and 11, the List of Candidates (LOC) for Classes 10 and 12, the practical and internal assessment upload window, admit cards, exam centre management, School DigiLocker, and the post-result rechecking and re-evaluation facility. It is, in effect, the operational spine of the exam year.

SARAS — the affiliation system — governs whether the school can offer CBSE curriculum and examinations at all. Fresh affiliation, upgradation and extension of affiliation all route through it, and CBSE has been explicit that extension applications depend on the accuracy of the OASIS data sitting underneath them.

The school's own website carries the Mandatory Public Disclosure page — staff details, infrastructure, results, fees — under the format CBSE prescribes (Appendix IX of the Affiliation Bye-Laws). It's the one compliance obligation that lives outside CBSE's own portals entirely, which is exactly why it's the easiest to forget.

The AIM portal monitors APAAR ID generation and coverage, the "One Nation, One Student ID" layer that CBSE has been steadily tying into registration and LOC eligibility.

In a well-run office, one person — typically a registrar or vice-principal — owns the base data in OASIS/UDISE+ and treats it as a living record. The exam coordinator owns Pariksha Sangam's exam-cycle tasks. The principal or a designated compliance officer owns SARAS and the disclosure page. When those three roles talk to each other before each window opens, the year runs smoothly. When they don't, the office finds out about a broken handoff only when a portal rejects a submission.

Term 1 — Registration, LOC, and the Data You Are Locking In Without Realising

Term 1 is where the year's foundational data gets written down — and, in practice, where it gets written down for good.

Class 9 and 11 registration typically opens once OASIS data is current, with a deadline in the October window and a short late-fee period afterward. CBSE has been consistent on one point across recent sessions: full names of students, mothers, fathers and guardians, with no abbreviations, and teacher lists on OASIS updated before registration begins — schools that skip this prerequisite step routinely find the registration portal rejecting their batch outright.

LOC submission for Classes 10 and 12 — the List of Candidates — runs on a parallel late-August-to-September timeline, submitted through Pariksha Sangam using the same credentials as registration. This is the step that formally nominates a school's own bona fide students for the board exam; CBSE has repeatedly flagged that only regular, attending students of the sponsoring school may be listed.

Both processes increasingly depend on APAAR ID — the 12-digit student identifier under NEP 2020's "One Nation, One Student ID" framework. CBSE has signalled that APAAR linkage will become mandatory for LOC and registration from the 2026–27 session onward, after finding that under half of students in affiliated schools had one by 2025–26. In the interim, schools have been permitted to mark entries "REFUSED" (parental consent withheld) or "NOGEN" (technical failure to generate) rather than block submission entirely — a relief valve, not a long-term substitute for getting APAAR IDs generated.

The detail that catches offices out every year: a short correction window, typically a couple of weeks in November for Class 9/11 data, after which CBSE has stated plainly that no further corrections will be entertained outside specific transfer cases. A misspelled name or wrong subject code that isn't caught inside that window becomes the student's — and the school's — problem for the rest of the year.

The Practical, Project and Internal Assessment Upload Window

Somewhere between mid-January and mid-February, a much quieter but equally unforgiving window opens: uploading practical, project and internal assessment marks for Classes 10 and 12 through Pariksha Sangam's Exam Activities section.

The mechanics are specific. For Class 12, the school creates a "batch" per subject, enters details of the external and internal examiners CBSE has appointed, and uploads marks for groups of up to thirty students at a time. For Class 10, practicals are conducted and assessed at the school level, with no external examiner involved.

The detail that matters most for planning: there is no facility to edit marks after upload. CBSE has said this outright in circular after circular — schools are responsible for verifying accuracy before submission, because the portal will not let them fix it afterward. That reframes the real deadline. It isn't the date the upload window closes; it's the date subject heads finish internal moderation, before anyone touches the portal. Offices that treat the upload date as the working deadline are, structurally, one keystroke away from a permanent error on a student's transcript.

Term 2 — Board Exam Logistics, Admit Cards and Marks Submission

By mid-February, the office moves from data entry into logistics. Admit cards are released through Pariksha Sangam a few weeks ahead of the exam start, and this is the last practical checkpoint to catch any LOC-stage error before it appears on an official document a student carries into an exam hall.

Board theory exams for Class 10 typically run from mid-February to mid-March, and for Class 12 from mid-February into early April — a longer window because of the larger subject spread. Through this period, the exam coordinator's job shifts to centre-level coordination: confirming observer and invigilation arrangements, managing attendance records, and handling the inevitable stream of exemption and correction queries that surface once students are actually sitting exams.

This is also the stretch where any unresolved Term 1 data problem tends to resurface — a wrong subject on an admit card, a name mismatch between the LOC and the school ID card — precisely because it's the first time anyone outside the office looks closely at the record.

Post-Result — Scanned Copies, Verification, Re-Evaluation, Compartment

Results are typically declared in May, and from that date the post-result window runs on a genuinely tight sequence, staged in days rather than weeks.

CBSE's process has three distinct stages, and they are not interchangeable:

1. Verification of marks checks that every answer was evaluated and totalled correctly — it does not involve a different examiner re-marking the paper.
2. Obtaining a scanned copy of the evaluated answer book lets the student actually see what the examiner marked.
3. Re-evaluation, charged per question, is the only stage where marks for a specific answer can be reconsidered.

Each stage has run on its own short window in recent cycles — often just a handful of days per stage — and a change from one stage can affect eligibility for the next. A student sitting on the edge of a compartment result, for instance, is often better served applying for verification immediately rather than waiting, since an upward revision can clear the compartment requirement outright.

Compartment exams for students who fail one or two subjects typically follow in July–August, run to the same difficulty as the main exam, and carry their own subsequent verification and re-evaluation cycle once compartment results are out. Office-side, this means the "board exam season" for a school doesn't actually close in April — it has a second, smaller peak in mid-summer that's easy to under-resource because most of the school's attention has already moved to admissions.

Year-Round — Affiliation Renewal, Mandatory Disclosure, Ministry Campaign Reporting

The obligations in this category share one trait: they don't have a single, dramatic deadline. They're ongoing, and CBSE audits them at any point, which is precisely why they're the easiest to let slide.

Affiliation extension is processed through the SARAS portal (School Affiliation Re-engineered Automation System). Fresh affiliation is usually granted for three or five years, after which a school must apply for extension well before expiry — CBSE circulars are explicit that schools whose affiliation is due to lapse the following year, or whose extension is "long pending," need to clear that first before applying for anything else, including upgradation. Extension applications draw directly on OASIS data, so a school with stale OASIS records is, in effect, applying for renewal on outdated information.

Mandatory Public Disclosure requires every affiliated school to maintain a functioning website carrying prescribed details — staff qualifications, infrastructure, fee structure, results — in the Appendix IX format, kept current and self-attested. CBSE has issued repeated advisories reminding schools that a stale disclosure page is treated as a bye-law violation, not a formatting oversight, with a compliance deadline typically set around mid-February each cycle for the current format.

APAAR/AIM monitoring sits alongside these as a newer, ongoing obligation — schools are expected to keep generating and updating APAAR IDs through the year via the AIM portal, not in a single push before LOC season, since coverage gaps are now visible to CBSE in real time.

None of these three carries the adrenaline of an exam-season deadline. That's exactly what makes them the most common source of an affiliation query the office didn't see coming.

The Five Deadlines Schools Miss Most Often — and the Single Cause Behind All Five

Across the calendar above, five specific failure points recur more than any others:

1. The LOC/registration correction window closes before an error is even noticed — usually because nobody cross-checks the submitted data against source records until an admit card or marksheet surfaces the mistake.
2. Mandatory Public Disclosure quietly goes stale — updated once at affiliation time and never touched again, until a CBSE advisory or an inspection flags it.
3. The practical/internal assessment upload happens in a rush, on the last permitted day, with no time to catch a transposed mark before the no-edit rule locks it in.
4. OASIS and the teacher data bank aren't current when a registration window opens, and the portal simply refuses the batch — a hard stop that costs days the office doesn't have.
5. Affiliation extension is filed too close to expiry, leaving no runway to fix a document rejection or a pending compliance flag before the deadline that actually matters — continued eligibility to hold board exams.

Look closely at all five, and they share one root cause: each is being handled as an isolated, once-a-year task, submitted reactively against its own deadline, rather than as one output of a single record the office keeps current all year. OASIS/UDISE+ data feeds registration, which feeds the LOC, which feeds admit cards and marksheets, which feeds affiliation renewal, which depends on the disclosure page being accurate. Treat any one link as a standalone chore and the error two links upstream doesn't surface until it's expensive to fix.

This is also, not coincidentally, the exact problem a centralised system is built to solve. Schools using Ocoviz's Multi-Campus Analytics to keep one live record of student and staff data across the year — rather than reconstructing it from spreadsheets every August — tend to hit these five failure points far less often, simply because the "upstream" data is already correct by the time any portal asks for it.

Practical Takeaways:

1. Assign one named owner for OASIS/UDISE+ data and review it quarterly, not once a year before registration opens.
2. Build internal moderation deadlines that sit two weeks before every CBSE portal deadline, especially for the no-edit practical marks upload.
3. Calendar the Mandatory Public Disclosure page as a recurring monthly check, not an annual task tied to affiliation renewal.
4. File affiliation extension applications the moment the SARAS window opens, not in the weeks before expiry.
5. Cross-check every LOC and registration submission against source records inside the correction window — before it closes, not after an admit card reveals the error.
6. Track APAAR ID generation through the AIM portal continuously, so the run-up to LOC season isn't also the first attempt at full coverage.

Conclusion:

None of this is a criticism of school offices — CBSE's compliance load has genuinely grown, and it now touches five systems where it once touched one. The schools that navigate it calmly aren't the ones with more staff; they're the ones that stopped treating each circular as a fresh fire and started treating the underlying data as one continuous record. Get that habit right once, and every portal on this calendar becomes a formality rather than a scramble.

The Comparison Block — the five CBSE systems, side by side: