A recorded departure does not prove that a student had permission to leave. An early-departure process needs two distinct pieces of information: the event itself and the institution's authorised approval.
When a parent's request remains only in one employee's memory, a shift change can break the process. A concise shared record makes the next action and its owner clear.
Define the minimum record
- Student and applicable date
- Requested departure time
- Verified relationship of the requester
- Staff member responsible for checking and approval
- Decision and actual departure time
- Notification status
Collect only information needed for the process. Avoid placing sensitive reasons in comments visible to all employees. The institution should decide who may approve requests and which communication routes are accepted.
Separate each stage
- Receive and match the request to the student.
- Verify authority using the institution's procedure.
- Record the approval decision.
- Record the actual departure independently.
- Check the required parent notification.
If the approved time is 14:00 and the actual departure is 14:12, retain both. These illustrative times show why a plan and an event should not be reduced to one field.
Clarify what the attendance system covers
BE Soft supports entry and exit events and parent notifications following recognition. That does not establish that every installation includes a dedicated permission workflow. During the demo, agree whether approval belongs in the panel or in a separate institutional record.
If the student returns, review the new entry without deleting a genuine earlier departure. Corrections should follow an authorised process, with an explanation where required.
Check group departure messages
An end-of-day message saying a student has just left may confuse a parent whose child departed earlier. Check how prior events and early departures are handled before sending a group notification. A bulk message should not be treated as independent proof of physical departure.
Review exceptions before drawing conclusions
Check approved requests without matching exits, exits without matching approvals and later returns separately. A missing record can be an operational issue. Staff should verify it before using the report to make a consequential decision.
Common questions
Does a parent message prove permission?
No. Notification and approval are separate facts.
Should a return overwrite the earlier exit?
No. Preserve genuine movements and record the new event.
Discuss your early-departure scenario with BE Soft through the English website and test the complete workflow in a demo.
