Guide2026-08-24·8 min read

The Six-Week Countdown: Digital Evaluation Readiness for October Exams

With October semester examinations six weeks away, Controllers of Examinations have a narrow window to audit infrastructure, train evaluators, and configure scanning centres. Here is a week-by-week operational checklist.

Why August Is the Critical Planning Month

India's university examination calendar runs two primary evaluation windows: April to June for the odd-semester or annual cycle, and November to January for the even-semester or supplementary cycle. The October examination period — covering supplementary examinations, fast-track semesters under NEP 2020, and internal assessment cycles — sits in between and is frequently underprepared precisely because it falls outside the main institutional planning calendar.

Controllers of Examinations who wait until September to audit their digital evaluation infrastructure find themselves making emergency decisions under time pressure. The six-week window starting now — the last week of August 2026 — is the correct moment to verify, train, and configure.

This checklist is designed for institutions that have already adopted or are in the process of adopting on-screen marking (OSM) systems. It covers the operational tasks that determine whether the evaluation cycle runs smoothly or produces the kind of errors that trigger revaluation floods and institutional scrutiny.

---

Week 6 (Now): Infrastructure Audit

The first week is entirely diagnostic. No procurement decisions, no vendor calls — only an honest audit of what exists and what has degraded since the April-June cycle.

Server and portal access

Verify that your OSM portal credentials are current and have not expired. Many university systems require quarterly password resets.

Confirm that the server hosting the scanning application has adequate storage for the expected examination volume. A university processing 80,000 answer books at 25 MB per scanned script requires approximately 2 TB of raw storage before compression.

Test the bandwidth at each scanning centre. High-resolution scans transferred to a central server over a congested institutional network are a common failure point.

Scanning hardware

Power on every scanner in your scanning centres and run a full-page test scan at 300 dpi.

Check for physical degradation: worn document feeder rollers, scanner glass scratches, and dirty sensor bars all produce the blurred or partial scans that generate evaluation errors.

Confirm spare ink or toner levels if your process includes any print steps.

Evaluator accounts

Pull the list of evaluators registered in the portal from the April-June cycle.

Identify evaluators who have retired, transferred, or declined to participate.

Note new subject areas added under NEP 2020 course restructuring that may require new evaluator enrolments.

Infrastructure Component	Check	Common Failure
OSM portal login	Credentials valid	Expired password, session timeout
Scanning hardware	Test scan 10 pages	Feeder jam, glass scratch
Server storage	Capacity calculation	Insufficient space mid-cycle
Network bandwidth	Speed test at scan centre	Transfer bottleneck
Evaluator roster	Active vs. registered	Stale accounts, missing subjects
Barcode/QR system	Sample scan + match	Misread codes causing misroutes

---

Week 5: Data Configuration and Mapping

Once the infrastructure audit is complete, the second week focuses on configuring the system for the specific October examination.

Course and paper mapping

Upload the examination scheme for October into the OSM portal: paper codes, maximum marks, sections, and marking schemes.

Map each paper to the evaluator pool. For double-valuation papers, confirm that the second-evaluator pool is distinct from the first.

Set moderation thresholds. The standard practice is to flag answer books where the first and second valuation differ by more than 10 percent of total marks for moderator review.

Barcode and identity configuration

Generate barcode or QR ranges for the October answer book batch.

Confirm that the barcode application process — whether pre-printed on answer books, applied at the time of inwarding, or via sticker — is aligned with your scanning centre's workflow.

Test the full loop: scan a barcoded dummy answer book, verify it routes to the correct evaluator queue, enter a mark, and confirm the mark reaches the result ledger.

Revaluation workflow

Verify that the revaluation application portal is configured with correct fees and deadlines for the October cycle.

Test the process by which a revaluation-flagged script is reassigned to the moderator queue without resetting the original first- and second-valuation marks.

---

Week 4: Evaluator Onboarding and Training

The April-June cycle revealed a consistent pattern across institutions that experienced evaluation problems: evaluators who were registered in the system but had not completed a guided practice session before live marking began.

Week 4 is for mandatory evaluator orientation. This is not optional refresher training for experienced evaluators — it is a requirement that every evaluator who will mark in October completes a minimum of one full practice session in the portal before the evaluation window opens.

What a practice session must include

Navigation of the OSM portal interface, including switching between answer pages, zooming, and rotating scanned images.

Entering marks section by section, with an automatic check that section totals do not exceed the maximum.

Using the annotation or comment tools where available.

Submitting a completed answer book and confirming it exits the queue.

Training logistics

Conduct practice sessions in batches of 20 to 30 evaluators per session.

Use real past examination answer books, anonymised and scanned, not artificially clear sample scripts.

Record attendance. Evaluators who do not complete practice should not be assigned live scripts.

Common evaluator issues to resolve during week 4

Inconsistent screen resolution settings that distort the aspect ratio of scanned pages

Browser compatibility problems (ensure evaluators use the portal-specified browser version)

Home internet bandwidth too low to load high-resolution scans — arrange for institution-provided access or session slots at campus labs

---

Week 3: Scanning Centre Dry Run

With evaluators trained and the system configured, week 3 is for a full dry run of the scanning process using actual answer books from the supplementary examination or a recent internal assessment cycle.

Dry run objectives

Measure throughput: how many answer books can your scanning centre process per hour with current staffing?

Identify bottlenecks: is the limit the scanner speed, the barcode application step, or the QC review of scans?

Calculate the scanning window required for your October examination volume.

A university processing 50,000 answer books with two scanners capable of 800 pages per hour, assuming an average answer book length of 32 pages, requires approximately 50 hours of scanning time across both machines — roughly 6 full working days at 8 hours each. If the examination window closes on October 15, scanning must begin no later than October 9.

QC standards to verify

Zero scanned pages with a legibility score below your portal's minimum threshold

Zero misrouted answer books (barcode matched to wrong paper code)

All scanned sets complete — no missing pages

---

Week 2: Final System Checks and Contingency Planning

Two weeks before examinations begin, shift from configuration to verification.

Checklist for week 2

Confirm server backup is running and tested. A system failure during evaluation without a recent backup has no clean recovery path.

Verify the helpdesk or support escalation contact for your OSM vendor. Confirm response time SLAs for critical issues.

Test the result export pipeline: run a dummy result set through the system and export to the format required by your university examination management system.

Review the revaluation timeline and publish it to students before results are declared. Ambiguity in revaluation deadlines generates administrative pressure after declaration.

Contingency protocols

Define the conditions under which you revert to manual evaluation for a specific paper (e.g., server downtime exceeding 12 hours, scanning centre failure at a remote exam centre).

Identify the manual evaluation coordinator and confirm their authority to make that call.

Maintain offline backup copies of all scanned answer books for 90 days after result declaration.

---

Week 1: Launch

The final week before evaluation begins should be operationally quiet — a sign that the preceding five weeks were used well.

Day 1 of evaluation window

Open evaluator portal access at the configured time.

Monitor the evaluator login dashboard for the first two hours: confirm that the expected proportion of evaluators have logged in and accessed their queues.

Check that the automatic mark-entry validation is flagging out-of-range entries.

Daily monitoring during evaluation window

Track percentage of scripts evaluated per day against the target completion timeline.

Flag evaluators who have not accessed their queue within 48 hours of assignment.

Monitor the moderation queue: scripts flagged for large valuation discrepancies should be cleared within 3 working days.

---

Why the Checklist Matters Beyond Operational Efficiency

Institutions that complete this checklist before their October examination cycle begin accumulating something more durable than a smooth evaluation run: documentation.

The NAAC Binary Accreditation Framework, introduced in 2025, requires verifiable YES responses to examination quality and automation indicators under Criterion 2. The data generated by a well-configured digital evaluation cycle — evaluator assignment logs, scan quality reports, mark-entry audit trails, revaluation rates — constitutes the primary evidence for Metric 2.5.3 (Examination Automation) and Metric 2.5.1 (Continuous Internal Evaluation).

NIRF rankings under Teaching, Learning, and Resources (TLR) weight graduate outcome data, which depends on accurate and timely result declaration. Institutions that routinely declare results within 30 days of examination closure build a quantifiable advantage in this parameter over academic years.

Starting the six-week process now is not an operational nicety. It is the difference between an October cycle that produces clean accreditation evidence and one that produces revaluation applications and student grievances.

---