A follow-up log should make it clear what support was agreed, who will act and when the result will be reviewed. Keep sensitive details within the approved private record.
A practical starting point
A teacher raises a learning concern in conversation, but no one knows whether the promised follow-up happened. A concise action record can close that gap.
Turn the idea into a working routine
- Record the specific support action, responsible person and intended review date in an approved location.
- Describe observable needs and avoid speculative diagnoses or labels outside staff expertise.
- At review, note what happened and decide whether to continue, adapt or close the action.
Measure what matters
Check overdue review dates and actions without an owner. These indicate where a useful conversation has not become a working routine.
Recording extensive sensitive background in a general class log can expose information to people who do not need it.
What should the team agree before putting this into practice?
Agree access boundaries and escalation contacts before using the log. Follow the institution’s established support procedures.
MAKE IT PRACTICAL
Your planning checklist
Use this checklist during a team discussion. It tracks your planning progress, not a score of your institution’s quality. Selections stay in this page and are not submitted.
A support record should make the next responsible action visible.
About this archive: 10 June 2024 is the collection’s reference date. This article was prepared and published on 7 November 2026. It is AI-assisted editorial content; examples are illustrative and do not describe a specific customer deployment.
