Digital attendance exceptions must be tied to the relevant date and student group. A missing entrance event on a day when attendance was not expected is not evidence of absence. Start by defining who was expected to attend, and at what time.
A common operational failure begins with a schedule change that never reaches the person maintaining attendance rules. Restarting a kiosk will not correct an outdated timetable. The workflow below is a planning recommendation; confirm which controls your installation actually supports.
Separate the weekly timetable from temporary changes
Keep the normal schedule, a date-specific exception and an individual student's status distinct. A cancelled lesson for one group does not cancel every lesson in the building. Identify the date, affected group, expected entrance time, approving person and return to the regular schedule.
- Record the effective date and the exact group.
- State whether attendance is expected at all.
- Assign responsibility for applying and reviewing the change.
- Define the message that families should receive.
- Check how the exception ends.
Review the expected participant list before sending alerts
In a fictional example, the regular entrance time is 09:00 and a replacement lesson starts at 10:00. Applying the earlier time creates a misleading late alert. If only two groups attend that day, missing entrance events for other groups should not be treated as unexplained absence.
Review the timetable, active enrolment and actual entrance records together. Do not delete a valid entrance event simply to make a report look consistent with an incorrect rule.
Test the exception without contacting real families
- Have a second staff member verify the date and group.
- Confirm that unrelated groups remain unchanged.
- Use an authorised test account or suitable sample record.
- Inspect event time separately from notification time.
- Verify the return to normal scheduling.
Keep test recipients controlled. If the product does not support the exception automatically, agree on a temporary staff procedure rather than assuming a feature exists.
Investigate a wrong alert at the rule level
Record the date, affected group, applied time and message type. An authorised correction and one accurate explanation to the family are more useful than repeated messages. If the issue recurs, review how approved timetable changes reach the operator.
Bring an exception to the demo
BE Soft offers day-based entrance times. Ask how your particular date and group exception would be handled. Review related guides and bring one real workflow, using fictional student details, to a demo discussion.
Frequently asked questions
Does no entrance record always mean absence?
No. First confirm that the student was expected to attend on that date.
Is changing the group time enough?
Only after checking the effective date, impact on other days and return to the normal timetable.
