Before a request
Treat a correction as a new accountable event—not a replacement memory.
Print or copy these registers before processing an exception. Keep the original mark, request, decision, applied change and final review distinct so a later reviewer can reconstruct what happened.
| Request field | Complete before review |
|---|---|
| Request identity | Request ID: __________ · received date/time: __________ · review due: __________ |
| Attendance context | Learner reference: __________ · academic date: __________ · class/section: __________ · period/unit: __________ |
| Original submitted state | Status: __________ · marker/role: __________ · submitted at: __________ · source reference: __________ |
| Requested change | Requested status: __________ · reason category: ______________________________ |
| Requester | Name/role: ____________________ · requested at: __________ · approved request route: __________ |
| Evidence reference | Minimum permitted reference or authorised N/A: ____________________ · do not copy sensitive detail here |
| Triage and routing | Assigned reviewer: __________ · normal / urgent / restricted: __________ · protected route if required: __________ |
Keep the same Request ID in both parts.
Open the linked decision and closure register| Decision field | Complete before closure |
|---|---|
| Request link | Request ID: __________ · original record rechecked by: __________ · checked at: __________ |
| Decision | Approve / reject / return for clarification / route elsewhere: __________ |
| Decision authority | Reviewer/role: ____________________ · policy or authority version: __________ · decision date/time: __________ |
| Accepted current state | Accepted status or no change: __________ · concise reason/reference: ______________________________ |
| Apply | Applied by: __________ · applied at: __________ · original-state reference preserved: __________ |
| Refresh and verify | Affected view/summary: __________ · refreshed by/at: __________ · verified by/at: __________ |
| Communicate | Recipient/role: __________ · approved channel: __________ · sent by/at: __________ |
| Closure | Closed / carried forward / restricted follow-up: __________ · closer/date: __________ · next review: __________ |
Keep the same Request ID in both parts.
Return to the original request register| Action | Primary and backup role | Permission and hand-off |
|---|---|---|
| Request | Primary: __________ · backup: __________ | May propose: __________ · approved route and receiving role: __________ |
| View | Primary: __________ · restricted-view owner: __________ | Minimum record scope: __________ · evidence/restricted hand-off: __________ |
| Decide | Reviewer: __________ · backup/escalation: __________ | May approve/reject/return: __________ · conflict or exception route: __________ |
| Apply | Authorised role: __________ · backup: __________ | May update accepted view after decision: __________ · history retained at: __________ |
| Review | Daily reviewer: __________ · policy owner: __________ | Checks closure/aging/patterns: __________ · next review or escalation: __________ |
Request to closure
Use one visible path from the first report to the final accepted record.
A short, consistent path is easier for teachers, administrators and families to understand than a collection of direct messages, verbal approvals and late spreadsheet edits.
Capture the exact attendance context.
Select the learner, academic date, class or section and period where applicable. Display the original status and submission context before accepting a request.
Record who is requesting what.
Capture the requester’s authorised identity, requested status, reason category and request time. A parent message or teacher note begins a review; it does not approve its own change.
Check proportionate evidence.
Verify the roster, timetable, arrival or leave context and any permitted supporting record. Collect only what the school needs for the decision.
Approve, reject or return for clarification.
A named reviewer applies the school’s rule. The outcome and reviewer should remain visible even when no correction is made.
Append the accepted change.
Show the corrected status in the current operational view while retaining the original value, request and decision history under the school’s access and retention rules.
Notify the relevant people and close the exception.
Confirm the outcome through an approved channel, avoid exposing unrelated learner details, and include the completed item in the next attendance review.
Route by cause
Resolve different attendance exceptions without pretending they are the same problem.
A correction, a late entry, a leave record, a roster defect and a disputed absence may all change what a reviewer sees, but they require different evidence and ownership.
| Scenario | Verify | Possible disposition |
|---|---|---|
| Teacher notices a marking mistake before submission | Correct learner and class context | Edit within the open marking task; no post-submission request needed |
| Teacher notices a mistake after submission | Original entry, intended status and authorised requester | Create a correction request and route it to the school’s reviewer |
| Learner arrived after the first mark | Arrival context and the school’s late-arrival rule | Apply the approved late or present status without rewriting the arrival time |
| Leave information arrives after an absence was recorded | Permitted leave request and the rule for authorised absence | Link or reference the leave decision; do not assume it automatically changes attendance |
| Learner was missing from the expected roster | Admission, section, timetable and effective-date records | Correct the source relationship first, then reconcile affected attendance |
| Connectivity interrupted class submission | Affected class, time window and any preserved local or manual record | Restore through the approved contingency path and flag possible duplicates |
| Parent or learner disputes an absence | Submitted record, authorised communication and school evidence | Open a review; do not let a message directly overwrite the school record |
Close the school day
Review incomplete classes and open corrections before interpreting attendance totals.
A percentage can look precise while the underlying day still contains missing classes, pending corrections or unresolved roster problems. Close completeness first; interpret patterns second.
Use a compact end-of-day close.
- Confirm which expected classes or periods were submitted and which remain incomplete.
- Review new correction requests, their age, reason category and assigned reviewer.
- Separate source-data defects from genuine attendance questions so each reaches the right owner.
- Check whether a corrected record changed a family-facing or school summary that needs a refreshed view.
- Escalate safeguarding or welfare concerns through the school’s protected process—not through the general correction queue.
- Record the close time, reviewer and unresolved exceptions carried forward.
| Cadence | Review | Decision |
|---|---|---|
| During the school day | New requests, missing context and urgent factual mistakes | Correct, reject, return or route to the right owner |
| End of day | Incomplete submissions, open corrections and roster defects | Close the day or carry named exceptions forward |
| Weekly | Repeated causes, aging items and high-volume classes or workflows | Fix guidance, training, source data or access—not just individual records |
| Term or policy review | Reason categories, approval authority, retention and communication rules | Update the documented process and role training |
Protect the record
Give each role the minimum action it needs, then document what the software does not decide.
Attendance records relate to identifiable learners. Correction access should be role-scoped, reviewable and separated from informal support channels or unrestricted exports.
Design the school process around
- an authorised marking role for the assigned attendance context
- a named reviewer for post-submission requests
- a protected route for sensitive welfare or safeguarding matters
Confirm in school policy
- when a submitted record becomes locked
- which reasons require supporting evidence
- who may view, approve, export and retain correction history
Do not assume
- a parent or learner request can directly edit the school record
- the original value should be deleted after approval
- one board threshold or retention period applies to every attendance purpose
Fix the workflow
Use correction patterns to improve the process—not to rank or blame people automatically.
Correction data can expose unclear status definitions, late rosters, confusing access, unstable connectivity or training gaps. It cannot establish intent or performance by itself.
Completeness
Were expected records submitted?
A low correction count means little when classes or periods are still missing.
Volume
How many submitted records were questioned?
Compare like-for-like periods and keep the denominator visible.
Aging
How long do requests remain open?
Use service bands and named owners instead of one misleading average.
Cause
Which reasons repeat?
Separate marking mistakes, late arrival, leave context, roster defects and technical interruption.
| Signal | Question before acting | Possible improvement |
|---|---|---|
| Requests cluster after the first period | Is the marking window, late-arrival rule or roster refresh unclear? | Clarify timing and test the morning handoff |
| One class has many roster-related requests | Did section changes reach the attendance source with the correct effective date? | Repair source ownership and reconciliation |
| Requests wait on one reviewer | Is authority too narrow or is evidence repeatedly incomplete? | Define cover, service targets and required fields |
| Corrections happen outside the recorded path | Is the request route inaccessible, slow or poorly understood? | Simplify the route and retrain the affected roles |
Frequently asked questions
Clarify the decision and its boundaries.
Use these answers as a starting point, then verify the relevant source, rule and school process.
Should a teacher be able to change attendance after submission?
The school should define when marking remains open and when a separate correction request is required. After submission or a daily close, separating the requester from the final reviewer can preserve accountability. The exact product workflow and school authority must be confirmed.
Should the original attendance status be deleted after a correction?
Not silently. The current operational view can show the accepted corrected status, but the school should preserve the original value, request, decision and responsible people according to its access, retention and applicable requirements.
Can a parent message directly change the attendance record?
A parent message can provide a reason or start a review, but it should not approve its own change. The school should verify the attendance context and apply its documented decision process before updating the accepted record.
Does CBSE prescribe this exact attendance-correction workflow?
No. CBSE sources require attendance records within their stated scope and say entries should be checked and signed, but the six-step correction workflow in this article is a practical editorial model. Schools must verify the current board, state and institutional procedure that applies to them.
How long should a school keep attendance-correction history?
Do not infer one universal period from this article. The school should map each record purpose to the current board, state, legal, contractual and institutional retention requirements, restrict access during retention and document secure disposal when authorised.
Primary sources and further reading
Read the official material behind the context.
Sources were reviewed when this explainer was updated on 2 September 2026. Always verify the current official version before relying on a rule or requirement.
Central Board of Secondary Education
Affiliation Bye-LawsOfficial source stating that attendance records are maintained and entries are checked and signed by the Principal or a nominated teacher. It does not prescribe this article’s full correction workflow.
Central Board of Secondary Education
Strict compliance with attendance requirements — 4 August 2025Dated circular for affiliated schools and Class X/XII Board-examination eligibility in the 2025–26 session. Verify current-session directions before acting.
Central Board of Secondary Education
Examination circularsOfficial index for checking later examination notices and attendance-related directions rather than relying on an older summary.
Ministry of Electronics and Information Technology
Digital Personal Data Protection Act, 2023Primary statutory source for further reading. This explainer does not provide a legal applicability or compliance decision.
Ministry of Electronics and Information Technology
Digital Personal Data Protection Rules, 2025Official Gazette notification with phased commencement. Verify later notifications and obtain qualified advice where required.