Safeguarding policy basics are a duty before a document
- 7 days ago
- 3 min read
Updated: 13 hours ago
Introduction
A small organisation downloads a safeguarding policy template, adapts the name, files it, and lists it on the website. The box is ticked and nobody has read it since.
That is a document, not safeguarding. If a volunteer noticed something concerning next week, would they know what to do, who to tell, and how quickly? In many small organisations the honest answer is no, and the policy on the shelf makes no difference to that. Getting this right is a duty to the people you work with before it is a compliance exercise.
1. Safeguarding policy basics begin with knowing what applies to you
Requirements vary and they are not optional.
The rules depend on your country, who you work with, and whether children or adults at risk are involved. Find out what is legally required of an organisation like yours rather than adopting another charity's policy and assuming it fits.
2. Name a person with responsibility
The most practical thing you can do.
Somebody designated, trained and known to everyone as the person to tell. Without a name, concerns get raised to whoever happens to be nearby, or more often to nobody at all.
3. Make the policy short enough to be read
Length defeats the purpose here.
Volunteers need to know what to look out for, what to do, who to tell, and how fast. A concise document people actually read protects far better than a comprehensive one that nobody opens.
4. Train everyone, including occasional volunteers
Coverage matters more than depth.
A short induction for every person who has contact with the people you serve, repeated periodically. The person most likely to witness something is often a casual volunteer nobody thought to brief.
5. Have a clear reporting route with a deadline
Ambiguity causes delay, and delay causes harm.
Who to tell, in what timeframe, what to write down, and what happens next. Concerns raised on a Friday should not wait because nobody knew whether it could.
6. Be explicit that concerns go outside the organisation when required
The point where small organisations most often fail.
Serious concerns must be referred to the appropriate statutory authority, and that duty is not overridden by loyalty or by fear of reputational damage. Say this in the policy and mean it.
7. Get the recruitment checks right
A legal requirement in most jurisdictions for relevant roles.
Background checks where required, references taken up properly, and a role description clarifying who has contact with whom. Doing this after somebody has started is a common and serious shortcut.
8. Keep safeguarding records securely and separately
These are highly sensitive personal data.
Restricted access, secure storage, a defined retention period, and separation from general records. Getting this wrong compounds the original harm and creates a further breach.
9. Review it and test whether it works
A policy is only current if it has been checked.
Review annually at board level, after any incident, and whenever the law or your activities change. Ask a volunteer what they would do if they were worried about someone, because their answer tells you what the policy is actually worth.
If something is disclosed to you, listen, do not promise confidentiality you cannot keep, write down what was said in the person's own words as soon as possible, and follow the reporting route. Do not investigate it yourself.
Conclusion
Treat safeguarding as practice rather than paperwork, because a filed policy protects nobody.
Establish what the law requires of an organisation like yours, name a trained person everyone knows to tell, keep the policy short enough that volunteers actually read it, brief every person with contact including occasional helpers, set a reporting route with a timeframe, state plainly that serious concerns go to the statutory authority regardless of reputational concern, complete the required recruitment checks before anyone starts, store safeguarding records securely and separately, and review annually while testing whether people know what to do.
.png)



Comments