Managing Low-Level Concerns in FE

A proactive safeguarding culture is built on vigilance and trust. It requires staff to feel confident reporting any concern, no matter how small it seems. Managing 'low-level concerns' systematically is a critical part of this, moving your provider from a reactive stance to one that identifies and addresses potential risks early. It is a cornerstone of demonstrating that safeguarding is effective and that the whole-provider culture is one where everyone takes responsibility for keeping learners and apprentices safe.

A clear process shows you are serious about professional boundaries and helps prevent behaviours from escalating into more serious safeguarding incidents. It’s a key indicator for inspectors of a healthy safeguarding CULLture, contributing to a 'Met' judgement at a whole-provider level.

What Qualifies as a Low-Level Concern?

A low-level concern is any behaviour by a staff member, volunteer, or contractor that is inconsistent with your provider’s code of conduct but does not meet the threshold for a formal safeguarding referral. It is about the behaviour itself, not a judgement of intent.

Examples in a further education and skills context could include:

• An instructor being overly familiar with learners or apprentices on social media.
• A staff member making unprofessional or sarcastic comments that single out a learner.
• Giving lifts to learners or apprentices in a personal vehicle, contrary to policy.
• A pattern of one-to-one meetings with a learner in private spaces without a clear educational reason.
• Using nicknames or terms of endearment that cross professional boundaries.

Establishing a Clear Reporting Process

For staff to report concerns, the process must be simple, well-communicated, and trusted. Ambiguity creates hesitation, which is the enemy of effective safeguarding. Your process should be a core part of staff induction and regular training.

Key elements of a robust process include:

• A designated person: All concerns should be shared with a named, impartial individual, typically the Designated Safeguarding Lead (DSL) or a nominated deputy.
• Multiple reporting channels: Offer flexibility. Staff should be able to report in person, via a dedicated confidential email address, or through a simple online form.
• Absolute clarity on confidentiality: Explain who will have access to the information and what the next steps will be. This builds trust in the process.
• Regular promotion: Do not assume staff remember the process from their induction. Remind them in team meetings, internal communications, and annual training updates.

Recording and Analysing Concerns

Effective management is impossible without effective recording. A fragmented system - using spreadsheets, emails, and paper notes - makes it impossible to spot patterns. A centralised, secure system is essential.

Your recording should capture:

• The date the concern was reported and the date of the incident(s).
• The person reporting the concern.
• The staff member or individual the concern is about.
• A factual description of the behaviour or concern.
• Initial actions taken and any subsequent information gathered.

Crucially, your system must allow you to connect multiple low-level concerns over time. A single instance of unprofessional language might warrant a simple conversation. Three such instances reported by different people over six months, however, indicate a pattern that requires a more formal response. Regular analysis by the DSL is key to identifying these trends.

Taking Appropriate and Timely Action

Once a concern is recorded, the response must be managed professionally and proportionately. The goal is to address the behaviour and reinforce professional standards, creating an opportunity for learning and development.

Possible actions could be:

• A professional conversation: A manager or the DSL can speak with the individual to understand the context and reiterate expectations around the staff code of conduct.
• Directed training: The concern might highlight a gap in understanding about professional boundaries or online safety, which can be addressed through targeted CPD.
• Policy review: A pattern of concerns could indicate that a specific provider policy is unclear or not fit for purpose.
• Escalation: The review might conclude that the concern is more serious than it first appeared, or a pattern of behaviour has crossed the threshold into a formal disciplinary or safeguarding allegation. At this point, you must follow your formal allegation management procedures.

Where this fits in QualityHero

The QualityHero Safeguarding module provides a secure, centralised system for logging and managing all safeguarding concerns, including low-level concerns. It enables DSLs to track actions, link related events to a single individual, and analyse trends across the whole provider. This provides leadership with a clear overview of potential risks and creates a robust evidence trail demonstrating a proactive and vigilant safeguarding culture.