How to analyze student attendance and identify persistent absence
Analyze attendance using eligible scheduled sessions for each enrolled student, not a universal calendar denominator. Separate present, late, authorized absence, unauthorized absence, and missing-register states, and calculate persistent-absence flags only after enrollment and data completeness checks.
Why the obvious method fails
A student who joined mid-term can appear to have low attendance if pre-enrollment sessions are counted. Missing registers and timetable changes can also become absences when status codes are flattened.
Attendance rates depend on opportunity to attend
The denominator should contain only sessions a student was expected and able to attend under the approved policy. Accurate flags support intervention; distorted denominators can send attention to the wrong students.
Where this usually goes wrong
Attendance data is sensitive and context-rich. The spreadsheet identifies patterns but should not automate disciplinary, safeguarding, or welfare decisions.
A useful mental model
- Join enrollment, timetable, closure, and student status to define eligible sessions.
- Preserve present, late, authorized, unauthorized, not-required, and missing-register codes.
- Use approved sessions and threshold policy with visible numerator and denominator.
- Investigate data gaps and student circumstances in restricted systems before action.
Choose the approach that matches the evidence and repetition
| Approach | When it works | What to verify |
|---|---|---|
| Calendar-day rate | Not appropriate for session attendance | Weekends, closures, and enrollment |
| Scheduled-session rate | Student attendance monitoring | Timetable and code quality |
| Secure case review | Support decisions | Context beyond the dataset |
From the field · School attendance administrator
Find persistent absence without penalizing mid-term arrivals
The term has closures, timetable changes, three students who joined late, and one week with incomplete registers. Leadership needs a support list, not a public ranking.
Columns used in the example
student_id · session_date · scheduled_flag · attendance_code · enrollment_start · enrollment_end · register_complete
Follow it with your own file
- Create eligible sessions between each student's enrollment dates.
- Exclude closures and distinguish incomplete registers from absence.
- Calculate approved attended and absent session measures with denominators.
- Review flagged students securely and aggregate only for wider reporting.
Check: Eligible sessions must reconcile to timetable and enrollment records, missing registers must remain visible, and sample student calculations should reproduce the system of record.
Patterns that need context
- Every student receives the same denominator despite different enrollment dates.
- Missing register values are treated as unauthorized absence.
- Attendance rates are shared for very small or identifiable groups.
A method you can follow
- Build eligibility: Join enrollment, timetable, closure, and student status to define eligible sessions.
- Map attendance states: Preserve present, late, authorized, unauthorized, not-required, and missing-register codes.
- Calculate rates and flags: Use approved sessions and threshold policy with visible numerator and denominator.
- Review context securely: Investigate data gaps and student circumstances in restricted systems before action.
Doing these steps in Prepyr
Prepyr accepts CSV files only. Export the worksheet or table you need as a UTF-8 CSV first; workbook formulas, formatting, macros, charts, and other sheets will not be included. Describe the result you need: Analyze school attendance and identify persistent absence accurately. Check the columns selected, preview any proposed changes, and compare the output with the source before applying or exporting it.
Prepyr steps used here: Data profiling · Natural Language analysis · Charts · Privacy controls
What to verify before acting
- Enrollment windows applied
- Session eligibility reconciled
- Codes preserved
- Missing registers disclosed
- Student-level output restricted
A trustworthy attendance view that identifies students who may need support while explaining eligibility, data gaps, and privacy boundaries.
Questions readers usually ask next
What denominator should attendance use?
Use eligible scheduled sessions under the school's policy, adjusted for enrollment, closures, and sessions not required.
Should missing registers count as absence?
No. Keep them as data-quality exceptions until the attendance status is confirmed.