Worksheet 1 of 5
Complete the authority register before defining a status.
Write the exact source, version or circular date, scope, verification date and decision owner for every layer. A school can have daily operational rules, board-examination eligibility requirements, state directions and case-specific approved exceptions at the same time; keep them separate.
| Policy layer | Write the exact source and verification date | Write the scope and owner |
|---|---|---|
| Jurisdiction / state | Source/version/date: __________________ · Verified: __________ | Scope: __________ · Verification owner: ________________ |
| Board affiliation | Board rule/circular and verification date: ________________ | Board/classes: __________ · Owner: ______________________ |
| Examination eligibility | Current exam rule/SOP: __________________ · Verified: ______ | Exam/class: __________ · Decision authority: ____________ |
| School daily operations | Policy/version/effective date: __________ · Verified: ______ | Principal/policy owner: _________________________________ |
| Leave or authorised exception | Approved evidence/route: ______________ · Verified: ______ | Decision owner/restricted location: _____________________ |
| Safeguarding or wellbeing follow-up | Protocol/version/verification date: ______________________ | Restricted owner/escalation: ____________________________ |
Worksheet 2 of 5
Write the attendance status dictionary before choosing a formula.
Complete every row used by the school. A label is not a definition: state the observable condition, minimum necessary evidence, calculation treatment and authorised role. Add a locally approved row rather than forcing an edge case into the wrong status.
| Status label | Write the definition and evidence | Write numerator, denominator, weight and owner |
|---|---|---|
| Present | Observable condition: ___________________________________ | Num: ____ · Den: ____ · Weight: ____ · Marker: ____ |
| Late | Cut-off, evidence and late-arrival route: _________________ | Num: ____ · Den: ____ · Weight: ____ · Corrector: ____ |
| Absent | Condition after marking/review: __________________________ | Num: ____ · Den: ____ · Weight: ____ · Follow-up: ____ |
| Leave / authorised absence | Approval, evidence and restricted detail: ________________ | Num: ____ · Den: ____ · Weight: ____ · Approver: ____ |
| Partial / early departure | Unit and treatment: ______________________________________ | Num: ____ · Den: ____ · Weight: ____ · Reviewer: ____ |
| Not marked / incomplete | Expected record missing because: ________________________ | Treatment: completeness exception · Owner: __________ |
| Other approved status | Label and definition: ____________________________________ | Num: ____ · Den: ____ · Weight: ____ · Authority: ____ |
- Status names use language staff and families can understand without revealing restricted context.
- Medical, disability, safeguarding and family details remain outside the general attendance mark.
- Evidence requirements are proportionate and do not invite sensitive documents into public channels.
- The policy distinguishes a teacher’s observation from an administrator’s approval decision.
- Every calculated status has a reproducible numerator and denominator treatment.
Worksheet 3 of 5
Define the formula, then work fictional edge cases.
Write the school’s approved numerator, denominator, period, population and rounding rule before calculating anything. The completed examples should reproduce a descriptive result; they must not create an automatic eligibility, condonation, exemption, discipline or safeguarding decision.
Define the calendar and attendance unit before the formula.
| Definition field | School decision | Edge case to test |
|---|---|---|
| Academic session and term | Session/term: ___________________________________________ | Mid-year admission, withdrawal or status change |
| Attendance unit | Daily / session / period / activity / other: ____________ | One day with incomplete periods or multiple shifts |
| Expected calendar | Source and version: ______________________________________ | Holiday, closure, exam day, event or timetable change |
| Included population | Campus/classes/statuses: _________________________________ | Inactive, transferred, newly admitted or temporarily exempt record |
| Marking cut-off | Normal deadline and authorised late route: ______________ | Teacher submits after cut-off or class was unassigned |
| Not marked treatment | Operational rule: ________________________________________ | Never silently count missing data as absence |
| Partial attendance | Late/early/half-day rule: ________________________________ | Status display and calculation may need different treatment |
| Definition | Write the school rule | Action boundary |
|---|---|---|
| Purpose and displayed result | Purpose/label: ___________________________________________ | Descriptive record; not cause, diagnosis or automatic decision |
| Reporting period and population | Period/campus/classes/statuses: __________________________ | Use the approved effective dates and included population |
| Numerator | Included statuses and weights: ___________________________ | Use the completed status dictionary; do not rely on label intuition |
| Denominator | Expected units, exclusions and calendar version: _________ | Reconcile closures, admission, transfer and withdrawal dates |
| Completeness treatment | Expected versus marked rule: ____________________________ | Route calendar, roster or marker gaps to correction first |
| Rounding and display | Decimal precision/display rule: __________________________ | Keep the unrounded source result for any authorised rule review |
| Operational review cue | School-defined cue and review frequency: _________________ | Human review; not a universal risk label or punishment trigger |
| Family communication point | When, by whom and approved route: ________________________ | Fact-based, supportive and minimum necessary |
| Formal eligibility threshold | Exact current authority, scope and period: _______________ | Apply only through the authorised decision process |
| Condonation / exemption / exception | Current source, evidence and authority: __________________ | Restricted case review; never automated from the percentage |
| Fictional case | Calculation or result to record | Verification boundary |
|---|---|---|
| Arithmetic check only | 18 ÷ 20 × 100 = 90.0% | Checks arithmetic only; it defines no status treatment or action threshold |
| School formula reproduction | Numerator ____ ÷ denominator ____ × 100 = ____% · displayed ____% | Matches the approved status weights, period, population and rounding rule |
| One unmarked expected unit | Expected ____ · marked ____ · unresolved ____ · displayed/held as __________ | Completeness exception; no silent conversion to absence |
| Admission after term begins | Approved start ____ · expected units from start ____ · result ____% | Denominator follows the approved effective date |
| Late or other status corrected | Original ____% · approved correction __________ · recalculated ____% | Original state and authorised decision are retained |
| Closure, transfer or withdrawal | Calendar/population version ____ · old denominator ____ · approved denominator ____ | Effective dates and the affected summary are reconciled |
| Near a formal threshold | Unrounded result ____% · displayed ____% · exact current rule __________ | An authorised person applies the applicable rule; the percentage does not decide |
Worksheet 4 of 5
Assign each correction responsibility before testing the hand-off.
Write a named role and backup for each responsibility. A changed status should remain explainable: preserve the original mark, request, minimum necessary evidence, reviewer, authorised decision, timestamp and recalculated result.
| Responsibility | Named role and backup | Required control or record |
|---|---|---|
| Maintain calendar and roster | Owner: __________ · Backup: __________ | Approved version/effective date: ________________________ |
| Submit the original attendance mark | Assigned role: __________ · Backup: __________ | Correct class, unit, date, status and submission timestamp |
| Review not marked or late submission | Reviewer: __________ · Escalation: __________ | Queue frequency/deadline: ________________________________ |
| Receive a correction request | Request owner: __________ · Backup: __________ | Approved route and record identifier: ___________________ |
| Verify authority and evidence | Reviewer: __________ · Restricted owner: __________ | Applicable policy version/minimum evidence: _____________ |
| Approve or reject correction / leave | Authorised role: __________ · Backup: __________ | Decision, reason, timestamp and original state retained |
| Recalculate affected summaries | Owner: __________ · Verifier: __________ | Affected reports/reconciliation evidence: ______________ |
| Communicate with family | Contact owner: __________ · Backup: __________ | Minimum necessary context and approved non-public route |
| Formal eligibility / condonation decision | Authority under current rule: ___________________________ | Separate from a routine software cue or daily correction |
Create the expected record.
Use the approved calendar, roster, unit and assigned marker for the correct date or period.
Record the original state.
Keep the submitted status, timestamp and responsible account available to the authorised review process.
Raise a correction request.
Identify the record and reason through the approved school route without overwriting the original explanation.
Verify authority and evidence.
The authorised reviewer checks the applicable school rule and minimum necessary evidence.
Record the decision.
Approve, reject or request more information with the decision owner, timestamp and policy version.
Recalculate and communicate.
Update affected summaries through the supported process and notify only the appropriate audience.
Review recurring causes.
Repair calendar, roster, assignment, timing, training or process defects instead of judging a person from correction volume.
Worksheet 5 of 5
Record approval only after the definitions and hand-offs pass.
The approval record should identify exactly which authority register, status dictionary, calculation version and correction map were reviewed. Re-test after a board update, academic-calendar change, status change or configuration change.
| Approval control | Record or evidence | Owner, signature and date |
|---|---|---|
| Approved policy version | Version/effective date: _________________________________ | Approver/date: ______________________________ |
| Official sources verified | Authority, link, version and verification date: __________ | Reviewer/date: ______________________________ |
| Status dictionary approved | Dictionary version/date: ________________________________ | Policy owner/date: __________________________ |
| Representative calculations passed | Fictional test-case pack/version: ________________________ | Verifier/date: ______________________________ |
| Correction hand-offs passed | Marker, reviewer, approver, family and administrator tests | Verifier/date: ______________________________ |
| Staff and family guidance approved | Guide/message versions and alternative routes: __________ | Owner/date: _________________________________ |
| Open exceptions | Issue, control, owner, due date and expiry: ______________ | Authority/date: _____________________________ |
| Final approval | Approved / approved with controls / not approved: _______ | Name/signature/date: ________________________ |
| Next scheduled review | Date or trigger: _________________________________________ | Policy owner: _______________________________ |
Supporting privacy check
Use the minimum attendance context needed for the next school action.
Attendance patterns can be signals for supportive review, but they do not establish cause. Keep health, disability, safety, transport, family, discipline and financial context in the appropriate restricted process.
General attendance record
- Approved status, date or period and class context
- Submission and authorised correction state
- Descriptive calculation and completeness context
- School-owned follow-up status where appropriate
Restricted school process
- Medical, disability or accommodation details
- Safeguarding, counselling or family circumstances
- Formal evidence for leave, exemption or condonation
- Discipline or legal correspondence
Do not infer
- A learner’s motivation, ability or family support
- A diagnosis, risk score or likely outcome
- Misconduct from one absence or pattern alone
- Formal ineligibility from a dashboard cue alone
- Family communication states the maintained record, applicable school process and route to respond.
- The recipient list is limited to people authorised for the purpose.
- The general message does not disclose diagnoses, allegations or confidential family context.
- A learner has a safe school route to raise a marking or access concern.
- Repeated patterns prompt supportive human review rather than automatic sanction.
Configuration boundary
Map the approved policy to current Schylva attendance scope.
Some policy elements may remain school procedures outside the product. Confirm the written configuration and do not convert unsupported requirements into marketing claims.
Supported current web scope
- Daily class attendance submission through the appropriate Teacher workflow
- Supported Present, Late, Absent, Leave and Not marked context
- Administrator oversight of maintained attendance records
- Parent and Student access to their supported personal attendance context
- Descriptive administrator attendance summaries in supported Analytics scope
Confirm during implementation
- School calendar, classes, sections and assigned Teacher context
- Approved status meaning, timing and school follow-up
- Historical or migration scope and reconciliation
- Role preparation, training and authorised corrections
- Any school rule that remains outside product configuration
Not currently claimed
- Biometric, facial-recognition, GPS, geofencing or attendance hardware integration
- Staff attendance, HR, payroll or workforce management
- Dedicated attendance-correction approval workflow
- Non-login SMS absence alerts or WhatsApp messaging
- Predictive attendance risk, automatic intervention or universal policy enforcement
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.
What should a school attendance policy define?
Define authority, scope, calendar, attendance unit, expected population, statuses, evidence, marking deadline, not-marked treatment, calculation, corrections, operational prompts, formal thresholds, exceptions, family communication, access, retention, approval and review.
Is 75% attendance a universal requirement for every Indian school student?
No. Attendance requirements depend on the current applicable authority, board, class, examination, period and circumstance. CBSE sources contain defined references, but schools must verify their exact scope and later circulars rather than generalising one number.
Should an unmarked attendance record count as absent?
Not automatically. It first indicates an expected record is incomplete. The school should resolve calendar, roster, assignment or submission context through the approved process before an authorised person records the correct status.
Who should be allowed to correct attendance?
The school policy should name the authorised role and evidence for each correction type. Preserve the original mark, request, reviewer, decision, timestamp and affected summary rather than silently overwriting history.
Can software decide whether a student is eligible for an examination?
Software can present maintained records and transparent calculations within scope. Formal eligibility, condonation, exemption or exception decisions belong to the applicable authority and authorised school process; a dashboard cue should not make them automatically.
Should medical or safeguarding details be stored in the attendance status?
Keep the general attendance record limited to the approved status and necessary operational context. Place detailed medical, disability, safeguarding, counselling or family information only in the appropriate restricted school process.
Does Schylva provide a dedicated attendance-correction approval workflow?
No dedicated attendance-correction approval workflow is currently claimed. Confirm the school’s authorised process during implementation and use the supported attendance scope without inventing an approval capability.
Does this worksheet make an attendance policy legally or board compliant?
No. It helps expose definitions, sources, roles and test cases. The school must verify current official requirements and obtain qualified legal, regulatory, safeguarding, academic or board advice where needed.
Primary sources and further reading
Read the official material behind the context.
Sources were reviewed when this checklist 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 starting point for CBSE-affiliated-school responsibilities and defined attendance contexts. Verify the current exact provision and scope.
Central Board of Secondary Education
Circulars related to studentsOfficial index containing current and historical student circular links, including attendance-related material. Use the exact applicable source and date.
Central Board of Secondary Education
Handbook for TeachersOfficial CBSE handbook context on attendance record maintenance and checking responsibilities; not a universal policy for every school.
Central Board of Secondary Education
School Quality Assessment and Assurance FrameworkOfficial quality-framework context connecting school policy, attendance records, family communication and follow-up. It does not replace current rules.
Ministry of Education, Government of India
UDISE+ Report 2024–25 — Existing StructureOfficial education-data context used for the general importance of current, validated records. No UDISE+ integration or compliance claim is made.
Ministry of Electronics and Information Technology
Digital Personal Data Protection Act, 2023Primary statutory source for qualified review. This worksheet does not determine applicability or provide legal advice.
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.