Skip to main content
Templates/Education/Handling a Safeguarding Disclosure
SCScenario

Handling a Safeguarding Disclosure

Branching scenario where school staff practise receiving a pupil's disclosure in line with KCSIE — listen, reassure, record, refer — with consequence feedback at every decision point.

7 sections
12 minutes
🎓 Education

Who this is for

Teachers, teaching assistants, and support staff in UK schools and colleges, and their DSLs running induction

Learners will be able to

  • Respond to a pupil's disclosure calmly, using open prompts rather than leading questions
  • Explain why staff must never promise confidentiality and what to say to the child instead
  • Record a disclosure accurately in the child's own words, with time, date, and factual detail
  • Refer to the Designated Safeguarding Lead without delay, including the fallback route when the DSL and deputy are unavailable
  • Recognise when a concern needs an immediate call to children's social care or the police

Template prompt

Create a branching scenario for school teaching and support staff on handling a pupil's safeguarding disclosure in line with Keeping Children Safe in Education (KCSIE). Cover receiving a disclosure calmly, listening without asking leading questions, what to say and what never to promise (confidentiality), recording the child's own words accurately, referring to the Designated Safeguarding Lead without delay, and what to do if the DSL is unavailable. Include decision points with consequence feedback showing how each choice affects the child and the quality of the referral.

This prompt is fully editable. Customise it to match your audience, regulations, and learning objectives before generating.

What the 7 sections cover

  1. 1

    The corridor conversation begins

    Scene-setting: a Year 8 pupil hangs back after class and says 'Can I tell you something, but you can't tell anyone?' — the first decision point tests the instinctive response.

  2. 2

    Never promise secrecy

    Consequence feedback on the confidentiality trap, showing what KCSIE expects staff to say instead and why honesty at this moment protects the child and the process.

  3. 3

    Listening without leading

    Branching decision comparing open prompts such as 'tell me what happened' with leading questions that could distress the child or compromise a later investigation.

  4. 4

    Scored decision points: what would you say?

    Scored decision set choosing the best response across four moments in the conversation, from first words to closing reassurance.

  5. 5

    Recording the disclosure

    Worked example of a strong written record — the child's own words, fact separated from opinion, time, date, and signature — presented as a visual do-and-don't comparison.

  6. 6

    Getting it to the DSL

    Decision point on referral routes and timescales, including the fallback when both the DSL and deputy are off site, and when to contact children's social care or police directly.

  7. 7

    Debrief and key takeaways

    Outcome summary reflecting the branches taken, a note on staff wellbeing after receiving a disclosure, and recap flashcards of the listen-reassure-record-refer sequence.

Structure is representative — the generator adapts sections to your edited prompt and passes every package through interactivity and visual-density quality gates.

See a real generated example

Year 9 Safeguarding Disclosure: Teacher Decision Path was generated with a prompt like this one — preview every section live and download the SCORM package.

Preview the live example

Topics covered

SafeguardingKCSIEDisclosure HandlingChild Protection

Make it yours

  • Upload your child protection policy so the scenario names your actual DSL, deputy, and recording system (for example CPOMS or MyConcern).
  • Change the pupil's age and setting — primary, secondary, or FE college — so the dialogue matches your staff's day-to-day context.
  • Add a strand on low-level concerns or allegations against staff if you want coverage beyond pupil disclosures.

Frequently asked questions

How often is safeguarding training required for school staff in the UK?

Keeping Children Safe in Education requires all staff to receive safeguarding and child protection training at induction, kept regularly updated, plus in-year safeguarding updates — for example via bulletins or staff meetings — as required and at least annually. Many schools also run a formal whole-staff refresher each year, and Designated Safeguarding Leads must update their own training at least every two years.

What is KCSIE and who has to follow it?

Keeping Children Safe in Education is the Department for Education's statutory guidance for schools and colleges in England, revised for most academic years — the KCSIE 2025 edition applies for 2025/26, with a consultation on 2026 revisions under way. All staff must read at least Part One (or, for staff who do not work directly with children, the condensed Annex where the school judges it appropriate), and governing bodies must ensure policies and training reflect it.

Should staff ask questions when a child discloses?

Only the minimum needed to understand enough to pass the concern on, and only open, non-leading questions. Investigation is the job of the DSL, children's social care, and where relevant the police — probing for detail at the point of disclosure can distress the child and undermine any later formal process.

Does this scenario replace full safeguarding training?

No. It is deliberate practice for one high-stakes moment — receiving and referring a disclosure — and is designed to sit alongside your whole-staff safeguarding training and your school's own child protection policy, not replace them.

Ready to make it yours?

Customise the prompt, generate a draft, then review the content and SCORM package before delivery.