Incident follow-up notes for charity programmes: template
A practical follow-up template for charity programme teams: assign actions, record handovers and check completion after a session incident.
Incident follow-up notes for charity programmes should show what still needs to happen, who owns each action, when it will be reviewed and what confirms completion. After the initial incident record, use a short action note to prevent tasks being lost between session staff, volunteers and the programme coordinator.
This template is for follow-up administration once immediate safety needs have been addressed. Adapt it to your charity’s procedures. It does not replace an incident report, safeguarding referral or professional judgement.
Act on urgent concerns before completing paperwork
Do not wait for the session to finish or for a form to be complete before taking necessary safety action. Follow your emergency and safeguarding procedures promptly. If the safeguarding lead is unavailable, use the alternative escalation route in your policy; an unanswered message is not a completed handover.
The Charity Commission’s safeguarding guidance for England and Wales expects charities to act quickly, record concerns securely and report to relevant agencies or regulators when required. The routine review dates below are organisational choices, not statutory deadlines.
Incident follow-up notes for charity programmes: a template
Add this structure to the approved record or link it by incident reference. Avoid copying sensitive details into a general task list. Record only what each authorised person needs for their role.
Incident reference and context: [record reference], [session and date], [location]. Keep the original factual account in the authorised incident record.
Update written by: [name and role], [date and time]. Distinguish what happened during the session from information received later.
Outstanding action: [one specific task]. Split separate tasks into separate entries so completion is unambiguous.
Owner and handover: [named person], [date and time responsibility accepted], [agreed cover if unavailable].
Review point: [date and time], [person who will check progress], [escalation route if overdue]. Choose timing according to risk and policy.
Communication decision: [who needs an update], [decision-maker and reason], [approved content and channel], [time sent and response, if relevant].
Completion evidence: [what was done], [date and time], [record or confirmation checked], [reviewer]. Record any remaining action separately.
Current status: [open / awaiting response / completed / transferred], [next review date if still open]. A transfer should name the receiving owner and confirm acceptance.
A fictional example: following up an equipment incident
The example below is invented and contains no real personal information. It illustrates routine operational follow-up, not the assessment or closure of a safeguarding concern.
Reference: DEMO-014, fictional Tuesday craft session. An unstable table was removed from use during the session; the original incident record contains the factual account.
Action: keep the table out of use and arrange a facilities assessment. Owner: the fictional programme coordinator, who accepted the handover at 17:15.
Review: Wednesday at 10:00. If no assessment is available, the coordinator will confirm an alternative room layout before the next session.
Update: the next session leader receives the equipment restriction through the approved staff channel. No participant details are included in that message.
Completion: the coordinator records the facilities decision and checks the agreed room layout. A separate replacement task remains open with its own owner and review date.
“Emailed facilities” records an attempt. “Facilities confirmed the table remains withdrawn; next session layout checked” records an outcome. The distinction helps the next team understand what is safe to use and what remains unresolved.
Decide family updates through the right person
For routine incidents, follow the agreed parent or carer communication process. Where a safeguarding concern is involved, the safeguarding lead or authorised deputy should decide what to share with the family and when, in line with local procedures and relevant agency advice. Do not send the full internal record automatically.
For programmes in England, consult the Department for Education’s information-sharing guidance when reviewing your process. Use the applicable national and local guidance elsewhere. Record the communication decision and its reason in the restricted record, including when an update is deferred.
Keep access on a need-to-know basis. An operational instruction for tomorrow’s team may be necessary without giving every volunteer access to the underlying concern. Equally, access controls must support appropriate safeguarding information sharing through authorised routes.
Check completion before closing an action
At the agreed review point, the owner or reviewer should be able to answer three questions: was the action carried out, what evidence confirms that, and does anything still need a named owner? If a response has not arrived, keep the item open, record the next step and follow the escalation route.
Closing an equipment or communication task does not close a safeguarding concern. Decisions about a concern remain with the responsible safeguarding professional under the charity’s procedures. Preserve the original note and add dated updates instead of silently replacing the earlier account.
Match your software to the follow-up process
Nexsteps safeguarding features support record keeping with role-based access and auditability. Its family communication features connect updates to programme activity. Check who can record, read and send information, and confirm the available communication history during a demonstration.
Use a fictional record to test the handover from session staff to reviewer before adopting a workflow. A useful follow-up note leaves the next responsible person with a clear action and a clear review point.