Low-level concerns are not minor. They are early indicators.

Under UK safeguarding guidance (including KCSIE), organisations must record and review low-level concerns relating to adult conduct, even when the behaviour does not meet the harm threshold.

Failing to record them weakens safeguarding culture.

Overreacting to them creates confusion.

This guide provides:

• A compliant Low-Level Concern Recording Template (UK)

• Clear staff guidance notes

• Escalation framework

• Secure storage advice

• Best practice for DSL oversight

What Is a Low-Level Concern?

A low-level concern refers to behaviour by an adult that:

• Is inconsistent with the staff code of conduct

• Does not meet the threshold for harm

• Does not require immediate referral

• May indicate boundary drift

Examples include:

• Over-familiar tone

• Inappropriate jokes

• Unnecessary one-to-one isolation

• Minor boundary crossings

• Policy breaches (e.g. personal device use)

Low-level does not mean insignificant.

It means below harm threshold... for now.

Low-Level Concern Recording Template (UK)

Below is a compliant template structure designed for schools, clubs, churches and charities.

Staff Guidance Notes (To Accompany the Template)

1️⃣ Record Facts Only

Write:

• What was seen

• What was heard

• Exact words (if relevant)

• Time and place

Do not:

• Diagnose

• Speculate

• Add emotional commentary

• Investigate

Low-level recording must remain objective.

2️⃣ Record Promptly

Low-level concerns should be logged:

• On the same day where possible

• Even if the issue feels minor

• Even if informal feedback was given

Delay weakens oversight.

3️⃣ Escalate If Patterns Emerge

A single boundary slip may remain low-level.

However, escalation is required if:

• Behaviour repeats

• The pattern escalates

• There is grooming-style behaviour

• A child feels unsafe

• Harm risk increases

The DSL should determine threshold shift.

4️⃣ Store Separately from Child Files

Low-level concerns relate to adult conduct.

They should:

• Be stored securely

• Have restricted leadership access

• Be kept separate from child safeguarding files

• Be monitored for patterns

Improper storage creates GDPR and governance risk.

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

Escalation is required if:

• Risk of harm is identified

• Boundary drift becomes persistent

• Secrecy increases

• Behaviour becomes isolating or manipulative

• A child discloses discomfort

The DSL should formally record threshold decisions.

Low-level concerns are about prevention.

Safeguarding concerns are about protection.

Why Recording Low-Level Concerns Matters

Inspectors increasingly examine:

• Whether low-level concerns are logged

• Whether patterns are reviewed

• Whether staff feel confident reporting

• Whether escalation thresholds are clear

A strong safeguarding culture records early signals.

A weak one waits for harm.

Leadership Oversight Best Practice

Safeguarding leads should:

• Review low-level logs regularly

• Look for repetition

• Identify staff training needs

• Ensure consistent threshold decisions

• Document outcomes

Structured recording protects:

• Children

• Staff

• Leadership

• Trustees

• The organisation

Downloadable Version + Toolkit

If you would like this template formatted into:

• A printable PDF

• An editable Word document

• A structured digital workflow

• A full safeguarding toolkit

👉 Get the Safeguarding Toolkit

Is Your Low-Level Concern Process Inspection-Ready?

Ask yourself:

• Are low-level concerns logged consistently?

• Is DSL review documented?

• Are patterns monitored?

• Are threshold shifts recorded?

• Is access restricted appropriately?

If you are unsure, it may be time to review your safeguarding systems.

👉 Take the Safeguarding Readiness Assessment (5 mins)

Early recording prevents escalation.

Clear thresholds build confidence.

Structure strengthens safeguarding.

Forward together.