What Does the Designated Safeguarding Lead Actually Do? A Guide for Staff

A child says something in the lunch queue that doesn’t quite sit right. A colleague mentions a bruise, or that a pupil has started flinching when a certain adult raises their voice. You’ve probably had a moment like this already, and if you haven’t, you will. Most teachers know they’re supposed to “tell the DSL” when something feels off, but a surprising number of staff — including experienced ones — have never actually sat down and worked out what that person does once you’ve told them, or what you’re expected to do yourself in the meantime. This is a plain guide to both.

What the DSL’s job actually covers

Every school and college in England is required to have a designated safeguarding lead. It’s not a title given lightly: under the current statutory guidance, Keeping Children Safe in Education (KCSIE), the DSL has to be a senior member of the school’s leadership team, and it’s explicitly not appropriate for the proprietor of a school to hold the role. The DSL takes lead responsibility for safeguarding and child protection, including online safety and understanding the school’s filtering and monitoring systems, and this has to be written into their job description rather than left as an informal add-on to someone’s timetable.

Governing bodies and proprietors are required to give the DSL “the appropriate status and authority” to do the job, along with the time, funding, training, resources and support needed to carry it out properly. In practice, that means a DSL isn’t just the person you happen to bump into in the corridor who seems approachable about this sort of thing. They’re the person the school has formally decided has the standing to make difficult calls, liaise with children’s social care and the police, sit in strategy meetings, and advise the headteacher when something serious comes up.

Day to day, the DSL is expected to be the point of contact for staff, parents and outside agencies on anything safeguarding-related; to manage referrals to children’s social care, the police, or the Disclosure and Barring Service where needed; to keep the school’s child protection file for each child up to date and transfer it securely when a pupil moves school; and to make sure every member of staff, including part-time and new starters, actually understands the child protection policy rather than just having signed to say they’ve read it. They’re also expected to know the local threshold and referral process well enough to use it under pressure, not just in theory.

DSL or deputy DSL — does it actually matter which one you speak to?

It’s entirely up to a school whether it has one deputy DSL or several, and there’s no legal requirement to have any at all, although in practice almost every school does, simply because a DSL can’t be everywhere at once. Deputies have to be trained to exactly the same standard as the DSL themselves, and during school hours a trained DSL or deputy should always be available for staff to speak to.

What deputies can’t do is inherit the DSL’s ultimate accountability. Day-to-day activity can be delegated to a properly trained deputy, but lead responsibility for child protection stays with the named DSL and can’t be handed off. For you as a member of staff, the practical point is simpler: if the DSL isn’t around, go to a deputy. If neither is available and something needs acting on straight away, speak to a member of the senior leadership team or take advice directly from local authority children’s social care — the guidance is clear that you should never let unavailability delay action, and whatever you do should be passed to the DSL or a deputy as soon as it’s practically possible afterwards.

What KCSIE expects of you, not just your DSL

It’s easy to think of safeguarding as “the DSL’s job” and everyone else’s job as simply noticing things and handing them over. That’s roughly right, but the guidance is specific about what “everyone else” actually has to know and do, and it’s worth being clear-eyed about it rather than assuming common sense will fill the gaps.

• Recognise the signs. All staff are expected to understand the indicators of physical, emotional and sexual abuse, neglect, and exploitation, and to know that these rarely turn up as one clean, obvious sign — they overlap, and they can happen online as easily as offline. You’re not expected to diagnose anything. You are expected to notice and act with “professional curiosity” rather than assuming there’s an innocent explanation and moving on.
• Know how to record and report a concern. This means knowing who your DSL and deputies actually are (not just that a policy document names one somewhere), and knowing the school’s process well enough to follow it without having to go and find the policy first.
• Never promise a child confidentiality. This is one of the clearest lines in the whole of KCSIE, and it’s the one staff most often get uncomfortable with in the moment. If a child is disclosing something to you and asks you not to tell anyone, you cannot agree to that. The guidance is direct about why: promising secrecy is unlikely to be in the best interests of the child, however kind it feels in the moment. What you can promise is that you’ll only involve the people who need to be involved — normally the DSL, a deputy, and children’s social care if it goes that far — and that you’ll tell the child what happens next.
• Reassure, don’t judge. A child or young person should never be left with the impression that they’ve created a problem by speaking up, and they should never be made to feel ashamed for it. That applies just as much to a disclosure of sexual harassment between pupils as it does to a disclosure about home.

The guidance sums this up with a phrase that’s worth keeping in mind whenever a term or a half-term goes by without anything happening: staff should maintain an attitude of “it could happen here.” Not because it’s likely on any given day, but because the schools that get this wrong are usually the ones that had quietly stopped believing it could.

Raising a concern: what to actually do, and how fast

If you have any concern about a child’s welfare, the expectation is that you act on it immediately, not once you’ve seen it happen twice, and not once you’ve had a chance to think it over at home. In practice that means:

• Speak to the DSL or a deputy as soon as you reasonably can, following your school’s own child protection policy. Don’t assume a colleague has already flagged it — the guidance is explicit that staff shouldn’t assume someone else will take action, because that assumption is exactly how things get missed.
• Write it down. Your record should include a clear, factual summary of what was said or observed, details of how you followed it up (who you told, and when), and a note of any action taken or decision reached. Stick to what was actually said or seen rather than your interpretation of it — notes like this can end up supporting a statutory assessment or, occasionally, a criminal investigation, so opinion has no place in them.
• Don’t sit on it while you decide if it’s “serious enough.” That’s the DSL’s judgement to make, not yours, and making it is precisely what they’re trained and resourced to do.
• If a child is in immediate danger, that changes the pace entirely — the guidance is clear that where a child is suffering, or is likely to suffer, harm, a referral to children’s social care (and the police, where appropriate) should be made immediately, not queued up for the next available DSL meeting.

If you’re ever unsure whether something is “worth mentioning,” the honest answer from the guidance is: mention it anyway. A nagging doubt is a legitimate reason to speak to the DSL, even if it turns out to be nothing.

What happens after you’ve reported it

This is the part most staff have the least visibility into, partly because it happens above their day-to-day view, and partly because confidentiality quite rightly limits what gets shared back. Broadly, once a concern reaches the DSL, they’re weighing up three routes, and they’re not mutually exclusive.

Managing it internally. Some concerns don’t need outside agencies at all — a one-off incident that’s better handled through the school’s own pastoral support and behaviour policy, with everything still recorded and kept under review in case a pattern emerges later.

Early help. Early help means putting support in place as soon as a problem starts to emerge, rather than waiting for things to escalate to crisis point. It sits below the threshold for a statutory children’s social care response, and it’s meant for exactly the kind of situations that come up often in a normal school year: a child showing early signs of a mental health difficulty, a young carer quietly struggling, a family going through domestic abuse, drug or alcohol problems, or housing instability, a child at risk of criminal exploitation. Where early help is the right route, the DSL usually takes the lead on setting up an inter-agency assessment, though staff may be asked to support it. The important nuance, and one that NSPCC’s own guidance on early help is careful to flag, is that early help is not a substitute for a child protection response — if there’s real reason to believe a child is at risk of abuse or neglect, the school should go straight to child protection procedures rather than trying early help first and escalating later.

Referral to children’s social care. Where a child is suffering, or is likely to suffer, harm, this is where a case goes. Two pieces of the Children Act 1989 sit behind this: section 17, covering children “in need” who need extra services to reach a reasonable standard of health or development, and section 47, which is triggered where there’s reasonable cause to suspect a child is suffering, or likely to suffer, significant harm. Once a referral lands, the local authority’s social worker is expected to acknowledge it within one working day and decide the next steps — whether the child needs immediate protection, an assessment under section 17, enquiries under section 47, or further specialist input. If a school makes a referral and the child’s situation doesn’t seem to be improving afterwards, the guidance expects them to follow up and escalate again rather than assume the case has simply been closed.

Whichever route the DSL chooses, the case rarely just stops there. It gets kept under review — decisions are revisited if things change, referrals are made again if the picture worsens, and the child’s circumstances stay on someone’s radar rather than being filed and forgotten. That ongoing monitoring is as much a part of the DSL’s role as the initial decision.

The weight of this work, and where to get support

None of the above happens in a vacuum, and it’s worth saying plainly: being the person a child confides in, or the person who has to make a judgement call about whether a family is coping, carries a real emotional cost. That’s true whether you’re the DSL making the decision or the classroom teacher who took the disclosure in the first place and has been quietly turning it over ever since. KCSIE doesn’t say a great deal directly about supporting the staff member who raised a concern, but the culture it’s asking schools to build — one where concerns are taken seriously, shared responsibly, and never treated as an overreaction — depends on staff feeling supported enough to keep speaking up.

If you’re struggling with something you’ve been part of, a few concrete places to start: talk to your DSL or a trusted colleague, within the bounds of what should stay confidential; ask whether your school offers an employee assistance programme or access to counselling, which many do as standard; and know that NSPCC runs a helpline for professionals working with children (0808 800 5000, help@nspcc.org.uk) that can offer advice, not just to DSLs but to any member of staff who wants to talk something through. Separately, if you ever feel a genuine safeguarding concern isn’t being taken seriously within your own school, NSPCC’s whistleblowing advice line (0800 028 0285, available 8am–8pm weekdays and 9am–6pm at weekends) exists specifically for that situation.

If you want more plain-English explainers like this one for your own reading list, the free Inspire Hub section on Learnaroo Hub has others written for exactly this audience.

Before you go: check your own school’s policy

KCSIE is revised regularly — often annually — and the edition referred to throughout this article is Keeping Children Safe in Education 2025, which has applied in schools and colleges since 1 September 2025. A further edition, KCSIE 2026, has already been published by the Department for Education and is due to take effect from 1 September 2026, so depending on exactly when you’re reading this, your school may be working from a newer version with some details changed. This article is a general explainer, not a substitute for either document or for your own school’s safeguarding and child protection policy, which will set out your local process, your named DSL and deputies, and your local threshold arrangements in more detail than any general guide can. If anything here doesn’t match what your school tells you, follow your school’s policy and ask your DSL to clarify.