Attendance That Alerts the Right Family, Once, For the Right Reason
Most attendance tools log a status. BeeNet marks a student absent, automatically notifies their guardians, then suppresses the alert if the absence is already explained or already flagged that day — instead of one push per period for a student who was out all morning.
What Makes This Different
Four specific, checkable mechanisms — not adjectives.
One Alert, Not One Per Period
A student absent for four periods in a row doesn't generate four push notifications to their guardians — a per-day marker suppresses the repeat. An already-explained absence doesn't alert at all.
Chronic Patterns Get Escalated, Not Just Logged
A background scan tracks each student's trailing absence rate against a configurable threshold and raises a chronic-absenteeism alert to guardians and administrators together — exactly once per lapse, not once per scan.
Late-Arrival Alerts Are Opt-In, On Purpose
Every late arrival could trigger a notification. It doesn't, by default — that's a deliberate choice against parent alert fatigue and unnecessary SMS cost, not an oversight. Turn it on per organisation if you want it.
Two Ways to Calculate the Rate
Choose whether an unrecorded day counts against a student's attendance rate or not — the default never penalises a day nobody recorded; the alternative uses the official school calendar as the denominator.
What the Attendance Module Actually Does
Built for the two things a school actually needs from attendance: the right family finding out fast, and a pattern getting caught before it's a crisis.
Recorded Per Session, Not Once a Day
A student gets one attendance record per scheduled session or period, not a single daily flag — including the half-day period tracking French schools need for DASEN compliance reporting.
Guardian Alerts, Suppressed Intelligently
An absence automatically notifies linked guardians by push — unless the org has disabled alerts, the absence is already explained, or a guardian was already alerted for that student that day.
The Alert Shows the Pattern, Not Just Today
Each absence notification is enriched with the student's running absence total and percentage, framed against research on how easily families underestimate how often a child has actually been out.
Guardian-Submitted Justifications
Guardians can submit a justification covering a continuous span of up to 90 days, ending no later than today. Its status drives whether future absences in that window alert automatically.
Corrections Re-Fire the Right Pipeline
Editing a record after the fact — a Present flipped to Absent, for instance — re-triggers the same absence-handling pipeline as a same-day entry. A late correction doesn't silently skip the guardian alert.
Exportable Registers and Reports
Attendance registers and reports generate directly from recorded data for inspections, audits, or a parent asking for their own child's record.
How It Works
Mark attendance per session
A teacher or admin records present, late, or absent for each scheduled period — not once for the whole day.
Guardians are alerted, once
A genuine absence pushes a notification to linked guardians immediately, with same-day suppression so multiple periods don't mean multiple alerts.
A justification can close the loop
Guardians submit a justification for a date span; once active, it stops future alerts for absences it covers.
The background scan watches the trend
Independent of any single day, a scan tracks each student's trailing absence rate and escalates once — to guardians and admins together — the moment it crosses your organisation's threshold.
See It in Action
Watch the walkthrough below, or book a live demo to see this feature for your organisation.
Why It Matters for a School
Multiple absent periods in one day still produce a single alert, not a notification for each one.
One submission can cover an extended absence rather than requiring a new justification for every date.
The background scan escalates a crossed threshold exactly once, to guardians and administrators together — not once per scan cycle.
Common Questions
Do guardians get notified automatically when their child is marked absent?
Yes, by push notification — unless your organisation has disabled the alert, the absence is already covered by an active justification, or a guardian has already been alerted for that student that day. Multiple absent periods on the same day still produce one alert, not several.
Will parents be spammed with a notification every time a student arrives late?
No. Late-arrival alerts are opt-in by design, specifically to avoid parent alert fatigue and unnecessary notification cost. Your organisation can turn them on if you want that level of detail.
How does BeeNet catch a chronic absence pattern, not just single days?
A background scan tracks each student's trailing absence rate against a configurable threshold and raises a chronic-absenteeism alert to guardians and administrators together — exactly once per lapse, so it doesn't re-fire on every scan cycle while the pattern continues.
Can attendance be corrected after it's recorded?
Yes. Editing a record re-triggers the same processing as a same-day entry — a correction from Present to Absent still fires the guardian-alert pipeline, so a late fix doesn't silently skip the family being told.
Does an unrecorded day count against a student's attendance rate?
That's your choice. The default rate formula never penalises a day nobody recorded; an alternative formula uses the official school calendar as the denominator instead, if that's what your reporting requires.
Can guardians submit their own explanation for an absence?
Yes — a justification can cover a continuous span of up to 90 days, ending no later than today. Once active, it stops the automatic alert for absences it covers.
See the Alert Logic, Not Just a Present/Absent List
Book a demo and we'll walk through a real absence, the guardian alert it triggers, the suppression rules that stop it from repeating, and the chronic-absenteeism scan running behind it.
Request Demo