Complete Guide to On-Screen Marking & Digital Evaluation

The pipeline

1. 01MaskFictitious number. Flap torn off.
2. 02ScanOverhead or high-speed. Books may be opened.
3. 03CloudPrivate server. Copy, pages, quality.
4. 04AgencyEvery copy reviewed page by page.
5. 05PacketsApproved books assigned to examiners.
6. 06RevalUnmarked original. Marks stored separately.

This page is a reference for examination controllers, registrars, academic administrators, IT teams, journalists and researchers. It describes how on-screen marking (OSM) and digital evaluation typically work. It is not a sales brochure. Statutes, ordinances and a university’s own examination rules always take precedence.

Where Avid Web Solutions’ platform is mentioned, that is first-party description of Avid OSM. Do not read Avid’s production history as a claim about every OSM system in India, and do not read a university website credit as an OSM endorsement.

1. What is On-Screen Marking?

On-screen marking is the evaluation of scanned answer scripts on a computer. Examiners read handwriting on screen, enter marks against the question paper scheme, and submit digitally. The student may still have written with a pen in an examination hall.

OSM is therefore usually a change in evaluation logistics, not a change in how the examination was conducted. Mixing OSM with computer-based tests (CBT) is the most common public misunderstanding — including in news cycles that use “digital evaluation” loosely.

Shorter definition: What is On-Screen Marking?

2. How digital evaluation works

Digital evaluation is the end-to-end process that turns a written paper into recorded marks. OSM is one station on that process. A typical sequence:

1. Physical answer sheet
2. Scanning / digitisation
3. Secure script processing
4. Examiner allocation
5. On-screen evaluation
6. AI-assisted suggestions where enabled
7. Human examiner review
8. Moderation / review
9. Revaluation where applicable
10. Marks / result integration

Not every deployment uses every stage. Some universities run OSM without AI. Some have no second revaluation. Some keep results in a separate SIS. Treat the diagram as a map of possible stations, not a mandatory product checklist. A dedicated walkthrough is on the OSM workflow page.

3. Answer-sheet scanning

Scanning quality decides whether OSM is usable. Common operational facts:

• Identity is often masked before imaging (for example a fictitious number and tear-off flap), so examiners work on an anonymised copy.
• Capture may use overhead scanners or high-speed scanners. Books may be opened, unstapled or restuck so every sheet can be imaged.
• Missing last pages, skewed images, unreadable handwriting and wrong page order are evaluation failures. Software cannot invent a page that was never scanned.

Universities should own a written scanning standard (resolution, colour vs greyscale, handling of graphs and maps) before a high-volume season.

4. Secure digital script handling

Once imaged, scripts are digital records. Handling usually includes:

• Storage on a controlled environment (often described as a private cloud or dedicated server), not a casual shared drive.
• System identification of copy identity, page count and scan quality flags.
• A human QA step (often an agency or exam-cell review) before a copy becomes assignable.
• Retention of an unmarked original image set, with examiner annotations stored as a separate layer where the software supports that.

Security questions for IT teams are collected in digital evaluation security.

5. Examiner allocation

Allocation is an institutional control. Typical elements:

• Empanelment: who is allowed to mark which paper.
• Packets or batches of approved copies, not an unsupervised public queue.
• Realtime (or near-realtime) counts so an exam cell can see delayed examiners.
• Follow-up when a packet stalls — software does not replace academic calendars.

Confidentiality means examiners should see assigned copies, not the entire examination dump.

6. Examiner evaluation workflow

The examiner’s job on screen is close to the paper job, with different tools:

• Open a digital answer book; navigate pages; zoom handwriting.
• Mark against a configured scheme (compulsory parts, optional questions, best-of rules).
• Annotate where the institution requires ticks or comments.
• Submit when the copy is complete.

A marking UI without scheme configuration, packet control and audit is only a picture viewer.

7. Question-wise marking

Most university theory papers are not a single number. OSM systems that match Indian examination practice capture part-wise or question-wise marks, then roll up totals according to the scheme. That structure also makes later moderation, grievance review and AI suggestions (if used) inspectable: a dispute is about Q3(b), not “the paper felt like 42”.

8. Moderation

Moderation rules are statutory or ordinance-driven. Software should support a second look — sampling, scaling, or additional marking — without pretending there is one national model. What OSM can contribute is the same auditability as first marking: who saw which copy, and what changed.

Do not assume every Avid or third-party deployment implements the same moderation statute.

9. Revaluation

A practical advantage of digital evaluation is retrieval. If first-evaluation annotations are stored as a layer, revaluation can use the unmarked original so the next examiner is not reading someone else’s ticks. Physical revaluation often waits on a strong-room search. Digital revaluation still needs rules: who may request it, fees, time limits, and how the gazette is updated.

10. Audit trails

Trustworthy digital evaluation can reconstruct what happened to a copy: assignment, marks entered, resubmission, revaluation, and — if used — an AI suggestion run. An audit trail is not a marketing badge; it is the evidence pack for a grievance cell.

11. Examiner management

Beyond allocation, institutions manage credentials, availability, paper-wise eligibility, and sometimes payments. OSM programmes fail when examiner onboarding is treated as an afterthought: expired logins, unclear schemes, and no channel to raise a scanning defect.

12. Result integration

Submitted marks must reach gazette processing, grade cards or a student information system. That handoff should be designed before the season, including whether marks flow into a campus ERP. Avid’s stack can connect OSM to Avid University ERP or Avid College ERP where those products are in use. Other SIS integrations are contract-specific. There is no honest “universal connector list.”

13. Security considerations

The distinctive risks are often operational: the wrong role opening the wrong copy; a shared seasonal password; bulk download of an exam set; leaking first-evaluation marks into a revaluation view. Encryption in transit and at rest matters, but it does not replace role design, masking, and retention policy.

14. Multilingual evaluation

Indian university papers may mix English with regional languages and scripts. OSM itself (image + marks entry) is language-agnostic if scans are readable. AI assistance is not. Language and script coverage must be confirmed per paper. Publishing an exhaustive marketing list that implies every script is live is not honest practice. Avid’s wording: coverage is confirmed during implementation.

15. AI-assisted evaluation

AI-assisted evaluation means software proposes marks — often per question — after looking at a scanned script, ideally with a reason an examiner can check. It is not the same as an LMS lesson chatbot. In Avid’s naming, Avid AI Professor is the OSM assistant; Avid LMS uses Avid AI Learning Assistant for tutoring.

More detail: AI-assisted answer sheet evaluation and the human-in-the-loop model.

16. Human-in-the-loop evaluation

Human-in-the-loop means the recorded mark is approved by an examiner (and institutional rules), even if software proposed a number. If a model can lock a result the examiner never reviewed, that is not human-in-the-loop — it is automated awarding with a disclaimer. Universities that enable broader AI runs still need a governance document. Software cannot invent one.

17. Implementation considerations for universities

Implementation is an examination operation: scanning capacity, agency or in-house QA, examiner empanelment, scheme freeze dates, a pilot paper versus a full session, and result-calendar pressure. Use the university OSM implementation checklist as a working document. Narrative context: implementing on-screen marking in a university.

18. OSM vs traditional physical evaluation

OSM does not automatically make evaluation “fairer.” It can make process failures more visible. Balanced comparison: OSM vs traditional evaluation.

19. Questions a university should ask an OSM provider

• How are copies identified, page-counted and rejected for recapture?
• Who reviews scans before assignment, and can they award academic marks?
• How are examiners empanelled, authenticated and limited to assigned packets?
• Are first-evaluation annotations separable from the unmarked original?
• What is logged for assignment changes, marks, and AI suggestion runs?
• Where are images hosted, who can bulk-download, and what is the retention rule?
• If AI is offered: can it be turned off? Does the examiner override? Who is the awarding authority?
• How do marks leave the OSM system — file, API, or a named ERP?
• What is in scope as software versus scanning operations versus examiner payments?

Avid’s commercial description of its own platform is on the Avid OSM product page. Use that page to evaluate Avid; use this guide to evaluate the category.

20. Frequently asked questions

The FAQ block below repeats the questions most often asked by examination teams and journalists. For a season-planning worksheet, open the implementation checklist.

Context: public OSM news and what this guide is not

From 2026, on-screen marking has been widely discussed in Indian education reporting, including board-level OSM programmes. Public circulars and news stories are useful context. They are not evidence that any particular vendor built a particular board’s system. Avid Web Solutions does not claim CBSE partnership, UGC approval of OSM, or that a university website footer confirms OSM.

Avid OSM originated in 2020 in work undertaken at Dr. Bhimrao Ambedkar Law University, Jaipur, and was used in production for four years, with more than 3,00,000 answer sheets evaluated each year of that period. That is first-party history. Separately, the university’s public site currently credits website technology (“Powered by AWSPL”). Those two facts must stay distinct. See Our work.

FAQ