How to Set Up a “Concern → DSL Review → Outcome” Workflow That’s Audit-Ready (UK)

In UK safeguarding guidance, clarity of process is not optional.

Both Keeping Children Safe in Education (KCSIE) and Working Together to Safeguard Children emphasise the importance of:

• Early identification

• Clear reporting pathways

• Prompt DSL review

• Recorded decision-making

• Secure information sharing

An audit-ready safeguarding workflow must demonstrate how concerns move from:

Concern → DSL Review → Outcome

Without ambiguity.

Without delay.

Without gaps in documentation.

This article outlines how to structure that workflow in alignment with UK safeguarding expectations.

Why Structured Safeguarding Workflows Matter

KCSIE requires that:

• All staff know how to identify concerns

• Concerns are reported immediately

• Designated Safeguarding Leads (DSLs) take responsibility for referrals

• Safeguarding records are maintained securely and separately from pupil files

Ofsted inspections assess whether safeguarding is:

• Effective

• Consistent

• Well-led

• Properly recorded

An audit-ready workflow demonstrates:

• Clear reporting routes

• Threshold application

• Evidence of decision-making

• Follow-up tracking

This is governance, not administration.

Step 1: Concern, Clear and Immediate Recording

According to KCSIE, staff must report any safeguarding concern immediately to the DSL (or deputy).

A concern may include:

• Disclosure

• Physical indicators

• Behavioural change

• Online risk

• Low-level adult conduct escalation

• Welfare indicators

Best Practice for Recording (Evidence-Based)

Research from the NSPCC and statutory guidance emphasises:

• Record as soon as possible

• Record facts only (not opinion)

• Include dates and times

• Use the child’s exact words where possible

• Do not investigate

An audit-ready recording stage must include:

• Date and time of incident

• Date and time of report

• Reporter name and role

• Location

• Factual description

• Immediate actions taken

KCSIE explicitly states that safeguarding information must be recorded accurately and securely.

Step 2: DSL Review, Threshold Assessment

Under KCSIE and Working Together, the DSL is responsible for:

• Assessing the information

• Determining next steps

• Making referrals where appropriate

• Recording rationale

This stage is critical for audit readiness.

What the DSL Review Must Demonstrate

An audit-ready DSL review should document:

• Date/time reviewed

• Threshold decision

• Rationale for decision

• Whether referral was considered

• Whether advice was sought (e.g. LA/MASH)

• Follow-up plan

Working Together to Safeguard Children (HM Government) stresses that safeguarding decisions must be:

• Timely

• Proportionate

• Recorded

• Shared appropriately

Without recorded rationale, inspection bodies may question safeguarding effectiveness.

Step 3: Outcome, Action, Referral or Monitoring

The outcome stage must clearly show what happened next.

Possible outcomes include:

• Log and monitor

• Early help referral

• Referral to Local Authority / MASH

• Referral to Police

• Referral to LADO (adult conduct concern)

• Internal support plan

• No further action (with rationale recorded)

KCSIE emphasises that decisions and actions must be recorded and followed up.

An audit-ready workflow includes:

• Outcome category

• Date action taken

• Case reference (if external referral made)

• Follow-up date

• Outcome review

• Sign-off

This protects:

• The child

• The staff member

• The DSL

• The governing body

What Makes a Workflow “Audit-Ready”?

Based on Ofsted safeguarding evaluation principles and statutory guidance, an audit-ready workflow should demonstrate:

1️⃣ Clear Escalation Pathway

Staff know exactly where to report concerns.

2️⃣ Timely DSL Oversight

Review happens without delay.

3️⃣ Documented Threshold Decisions

Not just action, rationale.

4️⃣ Secure Record Storage

KCSIE requires safeguarding files to be:

• Kept separately from pupil records

• Stored securely

• Accessible only to appropriate staff

This aligns with UK GDPR data protection principles.

5️⃣ Pattern Recognition

Working Together highlights the importance of recognising cumulative risk.

This requires:

• Central visibility

• Ability to link repeated concerns

• Regular safeguarding review

Common Audit Failures (Based on Inspection Feedback Themes)

Inspection reports frequently identify weaknesses such as:

• Concerns recorded but not reviewed

• DSL decisions undocumented

• Delayed escalation

• Lack of follow-up evidence

• Inconsistent threshold application

• Poor record storage

These are workflow issues, not policy issues.

Example of an Audit-Ready Workflow Structure

Below is a simplified structural model.

Stage 1: Concern Logged

• Staff member records concern

• Timestamp created

• DSL automatically notified

Stage 2: DSL Review

• Review date/time logged

• Threshold applied

• Decision recorded

• Referral considered

Stage 3: Outcome Recorded

• Action taken documented

• External agency noted (if applicable)

• Follow-up scheduled

• Case closed with rationale

Each stage must be:

• Traceable

• Time-stamped

• Defensible

Governance and Oversight

The governing body is responsible for ensuring safeguarding is effective.

KCSIE states that governing bodies must:

• Ensure appropriate policies are in place

• Ensure safeguarding arrangements are effective

• Receive appropriate safeguarding reports

An audit-ready workflow allows leadership to:

• Monitor patterns

• Review low-level concerns

• Track referrals

• Demonstrate oversight

Without structured workflow, governance visibility is weakened.

Digital vs Manual Systems

While statutory guidance does not mandate digital systems, it does require:

• Accurate recording

• Secure storage

• Restricted access

• Clear oversight

Manual systems can meet this standard, but only if they:

• Prevent unauthorised access

• Track decisions clearly

• Maintain consistent review

• Avoid email-based reporting

Digital systems may reduce administrative risk, but structure not format, determines compliance.

Final Audit-Ready Checklist

Before considering your workflow inspection-ready, confirm:

• Are concerns logged immediately?

• Is DSL review time-stamped?

• Is threshold rationale recorded?

• Are referrals documented?

• Is follow-up tracked?

• Are records stored securely?

• Can leadership demonstrate oversight?

If any answer is unclear, your workflow may need strengthening.

Strengthening Safeguarding Through Structure

Research and statutory guidance consistently emphasise:

• Early reporting

• Clear thresholds

• Recorded decisions

• Secure storage

• Leadership oversight

A Concern → DSL Review → Outcome workflow ensures safeguarding is:

• Proactive

• Transparent

• Accountable

• Defensible

Safeguarding is not strengthened by volume of paperwork.

It is strengthened by clarity of process.