One of the most common safeguarding questions in UK schools, churches and community organisations is:

“Is this a low-level concern, or is it a safeguarding concern?”

The distinction matters.

Getting it wrong can either:

• Overwhelm your DSL with minor issues, or

• Delay escalation of something serious

This guide explains:

• What low-level concerns mean under UK guidance

• What qualifies as a safeguarding concern

• Clear side-by-side examples

• When to escalate

• A simple decision framework for staff

What Is a Low-Level Concern? (UK Definition)

Under Keeping Children Safe in Education (KCSIE), a low-level concern refers to:

Behaviour by an adult that is inconsistent with the staff code of conduct, but does not meet the threshold for harm.

Low-level concerns usually relate to adult conduct, not child harm directly.

They may involve:

• Boundary issues

• Unprofessional behaviour

• Minor policy breaches

• Inappropriate tone or familiarity

They are not allegations of abuse.

But they still require recording.

What Is a Safeguarding Concern?

A safeguarding concern relates to:

A child or vulnerable person being at risk of harm, abuse, neglect, exploitation, or significant welfare issues.

Safeguarding concerns can involve:

• A disclosure

• Physical indicators

• Emotional distress

• Online exploitation

• Neglect

• Peer-on-peer abuse

• Concerning adult behaviour that may indicate harm

Safeguarding concerns require escalation to the DSL immediately.

Low-Level Concerns vs Safeguarding Concerns: Side-by-Side Examples (UK)

The difference is not always dramatic. It is about risk of harm and threshold.

Why Low-Level Concerns Still Matter

Low-level concerns must be:

• Logged

• Reviewed

• Pattern-monitored

• Escalated if repeated

Why? Because patterns of low-level concerns can indicate emerging safeguarding risks.

For example:

One isolated boundary slip = low-level.

Repeated boundary testing = safeguarding concern.

Ignoring low-level concerns weakens safeguarding culture.

When Does a Low-Level Concern Become a Safeguarding Concern?

Escalation is required when:

• There is risk of harm

• Behaviour escalates

• There is grooming pattern behaviour

• A child feels unsafe

• Multiple low-level concerns accumulate

• Conduct breaches safeguarding policy significantly

If unsure, escalate to the DSL for threshold assessment. Frontline staff are reporters, not investigators.

Common Misunderstandings

❌ “It’s not serious enough to report.”

If it breaches your code of conduct, it should be logged.

❌ “It’s just a personality issue.”

If it affects professional boundaries, it must be recorded.

❌ “There’s no proof of harm.”

Safeguarding is about risk... not proof.

Practical Decision Framework for Staff

If you’re unsure which category applies, ask:

1. Does this relate to adult behaviour toward a child?

2. Does it breach our code of conduct?

3. Is there potential risk of harm?

4. Is this part of a pattern?

5. Would I regret not recording this?

If the issue involves possible harm to a child → Safeguarding concern.

If it involves minor boundary behaviour → Low-level concern.

If unsure → Escalate.

Recording Requirements (UK Best Practice)

Both low-level concerns and safeguarding concerns should be:

• Recorded in structured format

• Time-stamped

• Stored securely

• Accessible to safeguarding leadership

• Monitored for patterns

However:

Low-level concerns may remain internal.

Safeguarding concerns may require referral to:

• Local Authority / MASH

• Police

• LADO

• Social care

Clear documentation protects everyone involved.

Why This Distinction Matters for Inspection

Inspectors increasingly ask:

• Are low-level concerns recorded separately?

• Are patterns monitored?

• Are thresholds applied consistently?

• Is DSL oversight visible?

Failure to distinguish clearly between categories can indicate weak safeguarding governance.

Strong safeguarding systems:

• Define thresholds clearly

• Support consistent recording

• Enable pattern recognition

• Protect both children and staff

Is Your Organisation Clear on Thresholds?

Ask yourself:

• Do staff understand the difference?

• Are low-level concerns logged consistently?

• Are safeguarding concerns escalated immediately?

• Is there evidence of threshold decisions?

• Can leadership identify patterns?

If uncertainty exists, clarity is needed.

Strengthening Safeguarding Culture

The goal is not over-reporting. The goal is structured reporting.

When staff feel confident about:

• What qualifies

• Where to log it

• Who reviews it

• What happens next

Safeguarding becomes proactive, not reactive.

Take the Safeguarding Readiness Assessment (5 mins)

If you’re reviewing your safeguarding thresholds, escalation pathways or recording systems:

👉 Take the Safeguarding Readiness Assessment

Clarity reduces hesitation.

Structure builds trust.

Trust protects communities.

Forward together.