Seeing a student twice in an entry list does not immediately prove that the system repeated one operation. The student may have re-entered, while reporting views or staff actions can also affect the result. Start by identifying the events represented by the two rows.
1. Inspect the event, not only the name
A repeated name alone does not establish duplication. Compare student identity, date, event type, time and device information when available. An entry and an exit appearing together can be expected. Two students with the same name should also remain separate. Describe the specific example clearly when asking for support.
2. Consider genuine re-entry
A student leaving the doorway and returning can explain a second event. Review authorised institutional records and staff observations. Ask the software team how repeated recognition is distinguished from a genuine new visit, including any repeat interval or event rule. Different installations may implement this differently.
3. Check devices and manual actions
More than one kiosk may have observed the student. A staff-added event may also appear alongside an automatic entry. Verify device roles, clock settings and how manual records are presented. Assuming the camera caused the issue can hide a configuration or workflow problem.
4. Separate records from messages
Two notifications do not necessarily mean two entry events. Resending and message-processing repetition require their own investigation. Compare the attendance list first, then notification statuses. Use controlled test recipients so diagnostic actions do not generate repeated messages to actual guardians.
5. Establish the cause before correction
Rather than deleting rows indiscriminately, identify which event is valid. Follow the institution’s authorised correction process and preserve the explanation. A useful support report includes the time window, affected device and steps taken. Avoid sharing unnecessary student photographs or complete lists.
Investigate repetition systematically
Work with BE Soft support to review the record and notification rules in your installation, identify the source of repetition and agree the appropriate correction.