At the start of an after-school session, an incomplete register can mean several different things. A student might have an approved absence, a room change might have sent the group elsewhere, or someone might genuinely need follow-up. A useful attendance process helps staff tell those situations apart while there is still time to act.
Agree on the list before the session
Give the session lead access to the current roster, the meeting point and any approved changes that are relevant to them. Assign one person to keep that roster current. If a class teacher, office team or provider keeps a separate copy, agree how changes get back to the shared record.
Separate an unchecked register from an unexplained absence
Use distinct statuses for a student who is present, an approved absence, and an absence that needs checking. Keep a separate indicator for a register that has yet to be completed. Otherwise, a missing mark can look like a confirmed absence, especially when an administrator is reviewing several groups at once.
Give each exception an owner
Follow your school’s existing safeguarding procedures for who to contact and when. Agree in advance which staff member checks the register, who investigates exceptions, and who communicates with families if required. Record the action taken and the time it was resolved so the next person can see the current state without piecing together a message thread.
Review the handoff after the first week
Pick two sessions and walk through a real exception with the people involved. Check where they looked first, whether they knew who owned the next step, and what information they had to request again. Fix the handoff that caused the longest delay before expanding the process to every activity.
Explore how ASAMAN Attendance fits into activity operations.
