Entry events help track when students reach the institution. Departures need their own rules. Lesson end time, the time a student leaves the entrance and a parent message are not identical information. Keeping these distinct supports clearer communication.
1. Define what an exit event means
An individual exit event represents an action completed for a particular student in the system. Check the identity and recorded time. It does not show that the student reached home or describe their journey outside the institution; avoid implying this in messages.
2. Manage early departures separately
Apply the institution’s permission and staff-check process when a student leaves before lessons finish. A recognition event does not replace an exit authorization decision. Specify who checks the departure and what parents are told. Record explanations through the appropriate institutional process.
3. Distinguish bulk messages from individual events
An end-of-day bulk update does not provide the same evidence as individually verified camera events. BE Soft offers a bulk exit message option. Review the recipient list and the situation described before using it. Do not state a precise individual departure time when it is unknown.
4. Review missing and repeated events
Students may leave without completing checkout or repeat an interaction at the kiosk. Staff should review contradictory records during closing checks. Apply the institution’s notification rules for early departures and already verified students before sending bulk updates.
5. Match message wording to the event
An individual message may include the student, institution and recorded time. A general end-of-day update should clearly describe its general nature. Separate test messages from real notifications. If a record is corrected, consider whether parents need an update.
6. Perform a daily closing check
Review the last departures, students still shown on site and unresolved events. An authorized member of staff should complete the check; sending a message alone does not prove every student has left. This routine can reduce errors carried into the next day’s reports.
Clarify your departure workflow
Discuss individual events, bulk updates and staff checks with BE Soft. Ensure the information parents receive matches what the recorded event actually establishes.