Define the record
Set the attendance policy before configuring software.
A percentage is only meaningful when the school can explain who was expected, which days counted, what each status means and how a disputed entry is corrected.Attendance is not one universal calculation. A school may maintain daily class registers, subject or period records, board-examination eligibility evidence, transport handoffs or other operational records. These purposes can use different calendars, responsible roles and rules. Write down the purpose of each record instead of asking one percentage to answer every question.
Policy test
Can a new teacher mark one class without guessing?
Give the teacher the expected roster, attendance date, permitted statuses, marking deadline and correction route. If any of those depends on informal knowledge, the operating rule is not ready to configure.
01 · Purpose
Name what the record supports.
Separate daily school operations, family visibility, internal review and board-specific evidence instead of combining them by assumption.02 · Calendar
Define when attendance is expected.
Record teaching days, holidays, closures, timetable exceptions, late admissions and student-specific start or exit dates.03 · Vocabulary
Give every status one meaning.
Document whether a status contributes to the numerator, denominator or neither, and who may use or change it.04 · Ownership
Assign marking and review roles.
Name who marks, who checks missing registers, who corrects errors and who communicates with a family.05 · Evidence
Retain the right supporting record.
Define when leave requests, correction reasons, approvals or communications are required and where authorised staff keep them.| Decision | What to write down | Owner |
|---|---|---|
| Expected attendance | Which learners, classes, dates or periods require a record | Academic or school operations owner |
| Status definitions | Permitted values, meaning and calculation treatment | Policy owner with record administrators |
| Daily deadline | When a register becomes due and when it is treated as missing | Attendance coordinator or administrator |
| Correction path | Who can request, approve, enter and verify a change | Named authorised school roles |
| Follow-up | Which pattern prompts verification, conversation or escalation | School leader, pastoral or safeguarding owner |
| Retention and access | Who needs the record, which copies exist and when they are reviewed or removed | School leadership with qualified advice where required |
Board-rule boundary
Do not turn 75% into a universal school rule.
CBSE circular CBSE/COORD/Shortage-Attend./2025, dated 4 August 2025, expressly reiterated Rules 13 and 14 for academic session and Examination 2025–26. When this guide was rechecked on 2 September 2026, no corresponding 2026–27 attendance circular appeared in CBSE’s official Examination Circulars index. The 2025 document is retained only as dated context; read the current CBSE Examination Bye-Laws, the official Shortage of Attendance guidance and any later applicable communication before applying a current-session workflow.
Make the routine complete
Design the handoff from expected roster to verified record.
The fastest marking screen cannot repair an incorrect roster, a missing calendar day or an unclear responsibility. Treat attendance as a short chain with a visible owner at every handoff.Prepare the roster and calendar.
Confirm the class, section, active learners, joiners, leavers, teaching date and any authorised timetable exception before marking begins.
Open the assigned attendance context.
The responsible teacher should reach the relevant class or period without browsing an unrestricted school-wide register.
Record one defined status per expected learner.
Use only the school’s approved vocabulary. Keep not-yet-marked separate from an actual absence.
Validate before submission.
Check the date, roster count, unmarked rows and any exceptional status that needs supporting context.
Confirm completion and surface gaps.
Give the responsible reviewer a way to distinguish complete registers from missing, incomplete or disputed records.
Correct through an accountable path.
Preserve the original context, reason, authorised actor and verification point instead of silently overwriting a disputed record.
Build a status dictionary before building a report.
| Possible status | Question the school must answer | Common reporting risk |
|---|---|---|
| Present | Does this mean present for the full day, class or selected period? | Mixing daily and period-level records |
| Absent | Was attendance expected and has the status been verified? | Treating an unmarked row as a confirmed absence |
| Late | Does late count as present, partial attendance or a separate operational event? | Changing the numerator without a written rule |
| Half-day or partial | Which part of the day counts and how is it represented? | Using inconsistent fractions across classes |
| Approved leave | Is it reported separately, and does it remain in the denominator? | Assuming approved automatically means excluded |
| Not scheduled | Was the learner genuinely not expected for this record? | Reducing the denominator without evidence |
| Not marked | Who must complete or reconcile the missing record? | Publishing an absence before the source exists |
Configuration warning
An example status is not a Schylva capability claim.
The dictionary above is a planning tool. Confirm the exact statuses, corrections and calculation behaviour available in the product release your school evaluates. Schylva’s current attendance scope is listed separately later in this guide.
Trust the denominator
Verify completeness before interpreting a percentage.
A precise-looking attendance rate can still be wrong when the expected days, roster, submitted registers or status treatment are incomplete.A basic attendance rate is attended opportunities divided by expected attendance opportunities, multiplied by 100. The difficult part is not the arithmetic; it is defining both sides consistently. A late admission, school closure, timetable change, missing register or disputed status can alter the denominator or make the rate premature.
| Check | Question | Action before reporting |
|---|---|---|
| Calendar | Was attendance expected on this date for this class? | Resolve closures, holidays and timetable exceptions |
| Roster | Were all active learners included with correct start and exit dates? | Correct membership before calculating |
| Completion | Did every expected register receive an authorised submission? | Keep missing registers visibly incomplete |
| Status | Does every value follow the approved dictionary? | Separate unmarked, disputed and confirmed states |
| Correction | Were later changes authorised and explainable? | Retain change reason, actor and verification |
| Calculation | Are numerator, denominator, exclusions and rounding visible? | Publish the definition with the result |
Review rhythm
Run two reviews: completion first, patterns second.
A same-day operational review asks which expected registers are missing or incomplete. A periodic support review asks what verified patterns deserve context and conversation. Combining the two can turn a recording gap into a false learner concern.
Treat a pattern as a prompt, not a diagnosis.
- Check the underlying dates and statuses before contacting anyone.
- Compare like periods only after accounting for calendar and timetable differences.
- Ask whether a late admission, transfer, approved activity or recording error explains the pattern.
- Use the smallest amount of learner detail needed for the authorised review.
- Give a responsible school professional the context and discretion to decide the next step.
- Record the follow-up outcome without adding speculative labels to the attendance record.
The official UDISE+ 2024–25 report describes school-level data collection with validation checks and administrative verification. UDISE+ is not a school ERP workflow, but the methodological lesson transfers: a maintained record needs validation before it becomes credible information.
Respond with context
Use attendance records to support participation, not automate conclusions.
Absence can reflect many academic, health, family, transport, accessibility or safeguarding circumstances. The record shows what was entered; it rarely explains why on its own.India’s National Education Policy 2020 frames careful tracking of enrolment and attendance alongside opportunities to catch up and re-enter school. That is a useful operating principle: detect a verified gap early, understand the learner’s context and connect the family with the appropriate school support. The policy does not make a software-generated risk label sufficient evidence for action.
01 · Verify
Confirm the source record.
Check the date, expected roster, submitted status and any correction or leave context before a message is prepared.02 · Understand
Ask before assuming.
Use an authorised school role and an appropriate channel to understand the situation without exposing unnecessary details.03 · Support
Choose a proportionate next step.
The response may be a record correction, family conversation, academic support or a school safeguarding process—not one automatic escalation.04 · Review
Record the outcome and return date.
Name who follows up, what was agreed and when the school will review the verified attendance record again.| Record | Minimum context | Avoid |
|---|---|---|
| Trigger | Verified dates, status and applicable school rule | A vague alert with no reviewable source |
| Recipient | Current authorised guardian or school contact path | Assuming every stored number is current or appropriate |
| Message | Plain description, school contact and next step | Sensitive details, blame or an automated diagnosis |
| Delivery | Approved channel, date, sender and delivery outcome | Treating send as proof the family received or understood it |
| Follow-up | Named school owner, agreed action and review date | An unresolved alert with no accountable next step |
Dated CBSE context
Keep board communications tied to the applicable instruction.
For 2025–26, CBSE’s 4 August 2025 circular instructed affiliated schools to maintain correct daily attendance records and communicate attendance shortages to parents in writing. Do not present those session-specific directions as a verified 2026–27 checklist: no corresponding successor was listed on the official Examination Circulars index when checked on 2 September 2026. Verify the current session’s requirements before designing a workflow or message.
Protect learner context
Limit access, copies and detail to the attendance purpose.
Attendance records concern identifiable learners and can reveal sensitive context when combined with leave documents, communications or repeated patterns.- State the purpose before collecting, opening, exporting or sharing learner-level attendance data.
- Give staff the minimum class, date and learner access needed for their assigned task.
- Use aggregate or class-level views when individual detail is unnecessary.
- Keep leave documents and sensitive explanations out of broad attendance summaries.
- Use fictional, redacted or approved sample data in vendor demonstrations and support conversations.
- Document correction, retention, deletion, export and incident responsibilities with the school and provider.
- Review active accounts and role assignments when staff responsibilities change.
| Role | Likely minimum need | Question to verify |
|---|---|---|
| Assigned teacher | Relevant roster, date and permitted marking action | Can the teacher browse unrelated classes or change historical records? |
| Attendance administrator | Completion, authorised detail and correction context | Which school-wide views and change actions are genuinely required? |
| School leader or support role | Verified pattern and enough context for a responsible follow-up | Can aggregate review replace learner-level access until follow-up is necessary? |
| Parent or guardian | Attendance for the correctly linked child | How is the relationship verified and updated? |
| Student | Personal attendance information available to the account | Which detail and correction route should the learner see? |
| Vendor or support team | Minimum approved diagnostic context | Can the issue be reproduced with sample or redacted data? |
Legal transition
Verify commencement and applicability; do not rely on a summary.
India’s Digital Personal Data Protection Act, 2023 and notified Digital Personal Data Protection Rules, 2025 establish a framework with phased commencement. The Rules state that Rules 3, 5–16, 22 and 23 come into force eighteen months after Gazette publication. This guide does not determine which provisions, child-data conditions, exemptions or other laws apply to a school. Verify current notifications and obtain qualified advice.
Separate guidance from product
Evaluate the current Schylva workflow against the school’s policy.
The school should bring its representative class, marking responsibility, review needs and correction process to the demonstration. The product walkthrough should then prove fit or record the gap.Supported today
- Daily class attendance submission through the appropriate Teacher workflow
- Administrator review of supported school or class status, attendance detail and available analysis
- Role-specific Parent and Student attendance views
- Connection to configured student, teacher, class and section context
Confirm for your school
- Teacher ownership, class and section responsibilities, and the expected marking time
- The exact administrator status, filter, detail and analysis views the school needs
- The attendance information Parents and Students should review
- The school’s operating process for a late entry or correction
Not currently claimed
- Biometric, facial-recognition, GPS, geofencing or attendance-hardware integration
- Staff-attendance workflows
- A dedicated attendance-correction approval workflow
- Non-login SMS absence alerts
- Predictive attendance risk or automated intervention
Demonstration brief
Use one representative class and three school decisions.
Bring a fictional or approved sample roster, the role and time that attendance should be marked, the administrator and family views required, and the school’s correction route. Do not send real student records through the public demo form.
Pilot the policy and workflow before wider activation.
Week 1: approve definitions.
Sign off the attendance purposes, calendar rules, status vocabulary, roles, deadline, correction route and family communication owner.
Week 2: configure and validate context.
Check representative students, teachers, classes, sections, account relationships and the views each authorised role can open.
Week 3: run a controlled pilot.
Mark real operating days for a limited approved cohort, reconcile completion and test a documented correction without changing the policy mid-pilot.
Week 4: review evidence and decide.
Inspect gaps, support questions, access, family visibility and calculation definitions; record fixes, owners and a wider activation decision.
- A representative roster matches the approved school record.
- Every marking role can reach only the attendance context it needs.
- Missing and incomplete registers remain distinguishable from absence.
- The authorised reviewer can verify the source behind a summary.
- The school has a documented path for a late entry or correction.
- Parent and Student views show only the relevant linked record.
- Training, support, retention, export and exit responsibilities are recorded in writing.
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 is school attendance management?
It is the school-owned process for defining expected attendance, recording an authorised status, checking daily completion, correcting errors, calculating summaries and using verified records for proportionate follow-up. Software supports the process; it does not replace the policy or professional judgement.
How should a school calculate an attendance percentage?
Define the relevant period and learner, count attended opportunities in the numerator and expected attendance opportunities in the denominator, then multiply by 100. Publish the status treatment, exclusions and rounding rule with the result. Do not calculate from missing or unreconciled registers as if they were complete.
Is 75% a universal attendance requirement for every Indian school student?
No. The CBSE material cited in this guide concerns specified classes, board-examination eligibility and a dated session. Board, state, class, school and purpose can change the applicable rule. Verify current official directions and obtain qualified advice where required.
How should an attendance correction be handled?
The school should define who may request, authorise, enter and verify a correction. Preserve the affected learner, date, original context, reason, responsible actor and verification point. Do not silently overwrite a disputed record. Schylva does not currently claim a dedicated correction-approval workflow.
Should software automatically label a learner as at risk?
A verified pattern can prompt a human review, but attendance alone rarely explains the cause. Check the source, calendar and learner context, then let an authorised school professional choose the appropriate support or safeguarding process. Schylva does not currently claim predictive attendance risk or automated intervention.
Does Schylva support biometric attendance or SMS absence alerts?
No current claim is made for biometric devices, facial recognition, GPS, geofencing, staff attendance or non-login SMS absence alerts. Evaluate the supported Teacher, administrator, Parent and Student attendance views against the separately listed scope.
What attendance data should a school share in a software demonstration?
Use fictional, redacted or formally approved sample data. A representative class structure and status scenario are usually enough to test the workflow. Do not submit student records, leave documents, family contact details, login credentials or confidential school information through a public enquiry form.
Primary sources and further reading
Read the official material behind the context.
Sources were reviewed when this guide was updated on 2 September 2026. Always verify the current official version before relying on a rule or requirement.Central Board of Secondary Education
Examination Bye-Laws Official index for the Bye-Laws and amendments. Verify the current rule and any later circular that applies to the school and session.Central Board of Secondary Education
Strict compliance with attendance requirements — 4 August 2025 Session-specific circular for 2025–26. No 2026–27 successor was listed on the official Examination Circulars index when checked on 2 September 2026; recheck before operational reliance.Central Board of Secondary Education
Examination Circulars index Official index checked on 2 September 2026 for a later attendance-specific circular or revision.Central Board of Secondary Education
Shortage of Attendance guidance Live official guidance referencing Rules 13 and 14. It is not treated as a session-specific 2026–27 circular.Ministry of Education
National Education Policy 2020 Primary policy source for the participation, tracking, support and education-technology context discussed in this guide.Ministry of Education
UDISE+ Report 2024–25 — Existing Structure Official statistical report describing school-level collection, validation and verification. UDISE+ is not equated with a school ERP.Ministry of Electronics and Information Technology
Digital Personal Data Protection Act, 2023 Primary statutory source for further reading. This guide does not provide a legal interpretation or applicability decision.Ministry of Electronics and Information Technology
Digital Personal Data Protection Rules, 2025 Official Gazette notification with phased commencement. Verify later notifications and obtain qualified advice where required.