# Mark rechecks

Use mark rechecks in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards.

Category: Academics
Guide: https://avkul.in/docs/guides/screen-school-mark-rechecks/
Guided sample demo: https://avkul.in/docs/demo/screen-school-mark-rechecks/
Snapshot: 11 October 2026

## Features

- Published-mark query
- Review acknowledgement
- Uphold/revise/reject decision

## Access and setup

Intended access: Assigned account with the required permissions
- A school account with the permissions shown below.
- Choose the relevant school, academic session or child before working.

Permission keys: exam:view, exam:manage

## Workflow

1. Locate the published mark query.
2. Acknowledge review of the paper.
3. Record the permitted decision and review its result.

## Fields and controls

- examScheduleId (string, declared required)
- studentId (string, declared required)
- reason (string, declared required)
- outcome ('UPHELD' | 'REVISED' | 'REJECTED', declared required)
- revisedMarks (number, optional)
- notes (string, optional)

## Current limits

- Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows.

## Actual application access

- https://avkul.in/en/school/mark-rechecks

## API reference

- GET /api/v1/mark-rechecks — List; exam:view
- POST /api/v1/mark-rechecks — Query a published mark; Authenticated scope
- POST /api/v1/mark-rechecks/:id/review — Acknowledge that the paper is being re-read; exam:manage
- POST /api/v1/mark-rechecks/:id/decision — Uphold, revise or reject a recheck; exam:manage

## Demo access

No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links.

Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow.