A robust safeguarding culture is not just about responding to serious incidents. It is built on vigilance, professional curiosity, and the confidence to address behaviour that does not feel right. Managing low-level concerns effectively is a critical component of this, demonstrating a proactive approach to keeping learners and apprentices safe, which is central to Ofsted's evaluation of safeguarding.
Ignoring or mishandling these concerns can allow concerning behaviours to escalate. A clear, well-understood process shows that your organisation takes every potential risk seriously and acts in the best interests of learners and apprentices.
What is a Low-Level Concern?
A low-level concern is any behaviour by a staff member, volunteer, or contractor that is inconsistent with your code of conduct but does not meet the threshold for a formal safeguarding allegation. It's about professional boundaries, not necessarily harm. Recognising these is the first step in preventative safeguarding.
Examples in an FE and Skills context could include:
- An assessor making sarcastic or professionally inappropriate comments to an apprentice.
- A tutor showing favouritism or having 'private jokes' with specific learners.
- Engaging with learners or apprentices on personal social media accounts.
- Giving a learner a lift home without prior approval or a clear business need.
- A staff member failing to maintain professional dress code or language.
Creating a Culture of Openness
Staff will only report low-level concerns if they feel psychologically safe to do so. The goal is not to create a blame culture, but one of professional accountability and shared responsibility for keeping everyone safe. Without this, vital information will be missed.
To foster this culture:
- Ensure clarity: Your Staff Code of Conduct must be explicit about professional boundaries and expected behaviours. This isn't just a document for induction-it needs to be a live reference point.
- Provide regular training: Train all staff on what a low-level concern is, why it matters, and precisely how to report it. Emphasise that reporting is a professional responsibility.
- Define clear reporting routes: Staff should know who to talk to. While this may be the DSL, having alternative named staff can be helpful. The process should be simple and accessible.
- Normalise reporting: Leadership should consistently message that all concerns will be taken seriously and handled with discretion. It is better to have a concern reported that turns out to be nothing than for it to go unreported.
The Need for Centralised Recording
An informal chat might seem like the easiest way to resolve a minor issue, but without a record, you lose crucial intelligence. A centralised, secure system for logging low-level concerns is non-negotiable for effective safeguarding.
Robust recording allows you to:
- Identify patterns: A single concern may seem minor, but a pattern of similar concerns about an individual, a group of learners, or even a specific workshop location can reveal a more significant problem.
- Inform proactive support: Analysis might highlight a need for targeted CPD for a staff member on professional boundaries or a review of a specific policy.
- Provide evidence of vigilance: A well-maintained log demonstrates to governors and inspectors that you have a proactive, systematic approach to managing behaviour and preventing escalation.
Analysing and Responding to Concerns
Once a concern is logged, a designated senior leader (often the DSL or Head of Centre) must review it promptly. The purpose is not necessarily punitive; it is to understand the context and determine the appropriate next step.
Key actions include:
- Timely review: Look at the concern in the context of any previous concerns about the same individual.
- Determine the response: This could range from a reflective conversation with the staff member to reinforce expectations, to providing additional training or supervision.
- Informal vs. Formal: Decide if the concern, even if low-level, warrants a more formal discussion or review under HR procedures.
- Escalation: If the concern meets the threshold of an allegation (posing a risk of harm), it must be escalated immediately according to your safeguarding and managing allegations procedures, including referral to the LADO.
Where this fits in QualityHero
Demonstrating a systematic approach to managing concerns is vital for leadership and governance. The QualityHero Safeguarding module provides a secure, centralised platform for logging, managing, and analysing all safeguarding intelligence, including low-level concerns. It allows DSLs and leaders to identify patterns, track actions, and generate reports that provide assurance to governors and external bodies that your safeguarding culture is vigilant and effective.
Want this in your workspace?
QualityHero turns insights like this into actions, evidence and governance-ready reports.
