Guide2026-09-02·7 min read

The Odd-Semester Exam Clock: What University Controllers Need to Do in September

With the new academic year underway and November-December exams roughly ten weeks away, this is the critical preparation window for exam offices that want to avoid the failures of the 2026 crisis season.

The Window Most Exam Offices Miss

Every year, the preparation failure is the same. Universities start the odd semester in July or August, run classes through September and October, and only begin thinking seriously about examination logistics in late October — four to six weeks before the first paper is scheduled. By then, the decisions that matter have already been made by default. Scanning infrastructure is whatever it was last year. Evaluator training is a circular sent in the last week of October. Vendor contracts are rolled over without review.

In a normal year, this works just well enough. In 2026, it does not.

Between May and August 2026, India's examination system went through its most disruptive period in decades. The CBSE on-screen marking controversy produced 1.6 lakh revaluation requests, two leadership changes at the board, a parliamentary inquiry, and Supreme Court rulings that now set implicit legal standards for any examination body running digital evaluation. The NEET-UG paper leak forced a retest of 2.27 million candidates and produced a student protest movement that reshaped the government's examination policy posture.

For university examination controllers, September 2026 is not just the start of another odd semester. It is the first examination cycle under a fundamentally changed regulatory and legal environment. The decisions made in September determine whether November looks like PSEB Punjab — smooth, auditable, trusted — or like CBSE in May.

What the Supreme Court's August 21 Order Requires

The Supreme Court's August 21 direction on the CBSE OSM revaluation portal produced binding language that applies beyond CBSE. The court's specific observations — that the absence of documented evaluator training constitutes prima facie institutional negligence, that students have a right to access scanned copies of their answer scripts within a defined period, and that institutions must maintain timestamped audit logs of every evaluation decision — establish the floor for digital examination due diligence across examination bodies.

Practically, this means three things for university exam offices running on-screen marking:

Training must be documented. Not a circular. Not an attendance sheet. A verifiable record of what training was provided, when, to which evaluators, and what competency it covered. The court was specific: training records must be available for production if a student challenges marks.

Answer script access must have a defined mechanism. The court directed that students must be able to obtain scanned copies of their evaluated answer sheets. Universities running OSM need a functioning mechanism for this — whether through a portal, a formal application process, or integration with the institution's revaluation workflow.

Audit logs must be complete and accessible. If the institution cannot produce, for any given answer sheet, a log showing who evaluated it, when each mark was entered, and what moderator review occurred, the evaluation record may not survive legal challenge.

The Ten-Week Preparation Checklist

With November-December exams roughly ten weeks from the start of September, here is the preparation sequence that matters.

Weeks 1-3 (September): Infrastructure Audit

The first task is a complete audit of the examination infrastructure, not an assumption that last year's setup still works.

Scanning capacity: Can your current scanning setup handle the volume of your November exam without creating a bottleneck? The CBSE failure was partly caused by scanning quality problems — blurred images, page-level mismatches, incorrect orientation. Verify that your scanners produce images at 300 DPI minimum, that your page-ordering software handles multi-page booklets correctly, and that your QR or barcode system can track at the individual page level, not just the booklet level.

Evaluator pool validation: Cross-check your evaluator database against the November exam schedule. Identify courses where evaluator coverage is thin and begin recruitment now — not in October.

Vendor review: If you use a third-party OSM platform, review your contract and the vendor's track record. The Radha Chauhan inquiry into CBSE's procurement found that the lowest-bid contract process, without reference checks on prior deployments, produced a vendor with a documented history of evaluation failures. Due diligence on vendor capability is not optional in 2026.

Weeks 4-6 (October): Training and Dry Run

The second phase is evaluator preparation. The CBSE crisis demonstrated that deploying digital evaluation without formal, documented evaluator training produces exactly the kind of errors that generate revaluation requests and litigation.

Run a formal evaluator orientation session — not an optional one. Cover: how to navigate the marking interface, how to enter question-wise marks, what to do when a scan is unclear or a page appears missing, and how to use the annotation tools.

Document attendance, the agenda, and the competency points covered. These records are what the court requires.

Conduct a dry run with a sample set of scripts — real answer sheets from internal assessments, if your institution runs them. Identify interface problems, slow-loading scripts, or evaluator confusion points before the live cycle.

Weeks 7-10 (November): Live Evaluation with Quality Gates

The third phase is the live evaluation cycle itself, which should include quality gates that did not exist in most university OSM deployments before 2026.

Pre-result verification: Before marks are uploaded to the result system, run a verification pass. Check that every question in every booklet has a mark entry. Automated zero-mark detection (flagging unanswered questions that received no mark) should run as a pre-result gate, not a post-complaint investigation.

Discrepancy resolution protocol: Define in advance what happens when an evaluator marks a booklet significantly below or above the cohort average for that question. Manual double-valuation? Automatic escalation to the chief examiner? The protocol should exist before the first script is evaluated.

Student communication: Publish the evaluation timeline, the revaluation window, and the answer script access mechanism before results are declared. Surprise is the enemy of trust.

Why September Is the Decision Point

The preparation steps above are not difficult individually. Scanning audits are routine. Evaluator training is manageable. Vendor reviews are a normal procurement step. The problem is sequencing — these steps must happen in September and early October to be useful by November.

A scanning audit started in October, when the semester is nearly over, cannot fix a hardware problem before exams begin. Evaluator training scheduled for the last week of October compresses the competency development that the court requires into a token exercise. A vendor review started after the exam season is underway has no effect on November.

Institutions that ran their last few exam seasons on paper, or on a minimal digital setup, face a specific decision point: do they upgrade for the November cycle, or do they wait for the following year? Given the legal environment after August 21, waiting carries its own risk. A revaluation challenge that reaches a High Court after November 2026 will be evaluated against the standards the Supreme Court has established. Institutions that cannot produce training records, scan quality logs, and complete audit trails will be in a weaker position than they were before the CBSE controversy.

The argument for beginning the transition in September — even a partial one, covering the highest-volume courses in a pilot — is that the regulatory clock is already running.

What PSEB Punjab Got Right That You Can Replicate

Punjab's state board conducted its first OSM cycle for board examinations in 2026 without a crisis. The design choices that made the difference are all replicable at the university level.

Page-level QR codes: Every page of every answer booklet carries a unique QR code. If a scan is missed, the system detects it before the evaluator receives the booklet. If pages are out of order, they are identified before evaluation begins. This is not expensive — it is a design choice in the answer booklet and scanning workflow.

Phased subject rollout: PSEB did not digitise all subjects simultaneously. It began with one subject in a pilot cohort, reviewed the outcomes, and expanded. Universities with a large number of courses can apply the same logic — prioritise two or three high-volume courses for November, use the season to build internal capacity, and expand in the subsequent cycle.

Pre-announcement of the mechanism: PSEB told students how they could access their scanned scripts before the evaluation began. This reduced post-result anxiety and pre-empted complaints. Universities can do the same by publishing the revaluation and script access policy in the exam schedule.