When a student changes classes, distinguish their current class from the class they belonged to on a previous date. Record when the change takes effect and make the grouping used by historical and current reports clear.
Suppose a student belongs to Group A on Monday and moves to Group B on Wednesday. If every earlier event appears under Group B at month-end, the report may display records without describing the institution's arrangement at the time. The issue is how group membership is represented over time.
Make three decisions before editing
- Effective date: When does the new membership begin, including a time if needed?
- Reporting: Are earlier events grouped by membership at the event date or by the student's current class?
- Schedule: Does the new group have a different arrival time or teaching calendar?
Do not assume the current software preserves historical membership. If it does not, keep an authorized institutional change record and define any required development separately.
Avoid creating a second student identity
Creating another student record just for a class change can split attendance history and confuse notification recipients. Prefer a process that preserves the identity while updating membership. If your system does not support that operation, agree on the method with support before making a duplicate.
Test the transition on both sides of the date
CheckExpected resultBefore the moveThe old group's dated report remains understandable.Transfer dayThe applicable schedule is explicit.Following dayThe student appears in the new expected list.Parent detailsThe recipient relationship has not changed accidentally.Use a test record or a small institution-approved example first. Plan notifications so tests do not send unnecessary messages to real parents.
Separate arrival from lesson attendance
An entrance event does not prove participation in every lesson of the new class. Preserve the distinction between entering the building and attending a lesson. This is especially useful when a student joins two programmes on the same day.
Review the month-end totals
Look for unexpected reductions in the old class, historical increases in the new class and students counted twice. Record the date and reason for corrections so that later changes to totals can be explained.
When discussing your attendance workflow with BE Soft, provide a sample class transfer and the reports you expect before and after it. This defines a concrete requirement without assuming a particular feature already exists.
