Referral to children’s social care
The Early Help plan wasn’t making a difference, so the DSL referred to the local authority’s front door. Mum was told about the referral the same day.
MASH referral.pdf attached. Read by 4 of 4.Any adult in your school can record a worry about a child. Your designated safeguarding lead (DSL) and their team are alerted, see everything that came before, and decide what happens next. SEND, behaviour, attendance and health are part of the same record.
The form asks for what you saw and heard, when and where, and what the child said in their own words. It takes a couple of minutes, so it gets done while the detail is fresh.
If something is urgent, the form says so plainly: find a DSL in person now, and call 999 if a child is in immediate danger. It also reminds staff not to promise to keep a secret.
Writing help can tidy rough or dictated notes and point out opinions. It never changes anything inside quotation marks, and nothing changes unless the member of staff applies it.
If there’s a visible injury, staff mark it on a body map with numbered markers. Children’s injuries are never photographed.
Pupils can add a worry themselves, in their own words. Anyone else, including parents and people in your community, can report anonymously by scanning a QR code on a poster or your website.
Every report reaches the DSL team as an alert, just like a concern from staff. The DSL reviews it and decides what happens next.
The DSL group is alerted as soon as a concern is sent, along with the child’s DSL lead and anyone else the member of staff chooses, such as a Head of Year. Alerts arrive as an in-app notification, an email or a text message.
On the concern, the DSL can see who was alerted and who has opened it. Alert emails and texts say only that there is an alert and its category. Names and details stay inside Pupil Protect.
Every concern, action, contact, meeting and document lands on the child’s chronology as it happens. Here are six entries from one example record.
The Early Help plan wasn’t making a difference, so the DSL referred to the local authority’s front door. Mum was told about the referral the same day.
MASH referral.pdf attached. Read by 4 of 4.At the initial conference, Amelia and her brother were made subject to child protection plans under the category of neglect. The school’s support plan started the next day.
ICPC report.pdf attached. Read by 4 of 4.She told her tutor the power had been off for two days. She seemed tired, and her uniform was unwashed.
Logged by her form tutor. Linked to 2 Oct.She said she was looking after her younger brother because mum had an early shift. The pastoral lead added an action: refer to the attendance officer and raise a young carers assessment with the social worker.
Logged by the attendance officer. Read by 2 of 2.The plan continues. Home conditions have improved, but food and missed health appointments are still a worry. The next review is set for 9 October.
Minutes.pdf attached. Read by 4 of 4.Her tutor and a teaching assistant each logged a concern. The DSL merged them into one entry and linked it to the concerns from 1 October and 4 September. Both accounts are kept word for word, and the merge can be split again.
“mum was at work late and there wasn’t anything in”
“mum was working late and there was nothing in”
Filter by entry type or category, or show key events only. A family timeline puts brothers’ and sisters’ chronologies side by side.
Every entry shows who wrote it, who has read it and which files are attached. Restricted entries stay with the DSL team.
Plans are built around outcomes for the child, each with actions, owners from school and other agencies, and due dates. Overdue actions show up on the DSL’s dashboard.
The child’s voice has its own place on every plan, in their own words.
On each concern, Safeguard looks across the record and suggests next steps, with the reason. The DSL decides whether to use them.
“I like coming to breakfast club because I can see my friends. I don’t like being late because people look at me.”Recorded by her Head of Year, 20 September
Pattern: this is the third food- or clothing-related concern in 30 days, attendance is 86.4%, and she has a child protection plan for neglect.
Your SEND register, support plans and EHCPs, provision maps and reviews are part of Safeguard. Each one lands on the child’s chronology, so what you know about a child’s needs sits next to everything else.
It’s included in Safeguard at no extra cost. [Who can see SEND records, for example the SENCO and the DSL team]
Log incidents and rewards, set consequences and detentions, and send reports to parents. Behaviour lands on the child’s chronology too, so a change in behaviour is seen alongside everything else you know.
It’s included in Safeguard at no extra cost.
Attendance comes from your MIS and health records are kept in Safeguard, so a run of absences or a new medical need is seen next to everything else you know about a child.
Both are included in Safeguard at no extra cost.
Set up a core group, child in need review or internal DSL meeting from the plan. The agenda is taken from the plan’s outcomes. If everyone agrees, Pupil Protect records and transcribes it and drafts the minutes.
Choose the meeting type, the people coming and the agenda. Suggested agenda items come from the chronology, and nothing is added unless you choose it.
The chair reads a short script and records who agreed and when. If anyone says no, nothing is recorded and the chair takes notes instead.
A live transcript shows who said what. Names of children who aren’t part of the meeting are replaced automatically. The chair can mark decisions and actions as they happen.
The draft minutes, decisions and actions are checked against the transcript. Nothing is saved to the chronology or shared until the chair approves them. Then the audio is deleted.
The audio is deleted once the minutes are approved, and the transcript is kept. Schools can switch meeting notes off entirely.
“She mentioned a friend, [name hidden], who’s been helping her with homework at lunch.”
1 other child’s name hidden in the transcript.Safeguard can draft a referral summary or an update for a social worker from the record. The DSL checks it, ticks that it’s accurate and chooses to send it.
Updates and plans go through Connect, so the social worker reads them inside Pupil Protect and you can see when they opened them. A shared plan doesn’t include concern records or the chronology.
Before anything leaves the school, a confirmation says who will see it and that it can’t be recalled. Sending is logged on the child’s record.
Today (2 Oct) Amelia arrived without a coat and told her tutor she hadn’t eaten since lunch the previous day, saying “mum was at work late and there wasn’t anything in”. This is the third food- or clothing-related concern since 4 September. School has provided breakfast, a coat and uniform, and a breakfast club place from 5 October. We would like to discuss this at the core group on 9 October.
Mistakes happen: the wrong pupil, a wrong date, a detail that turns out to be wrong. A DSL corrects the entry and gives a reason, and the original stays in the history.
Choose what the export is for, and the options follow. Every page is marked OFFICIAL-SENSITIVE and shows who exported it and when. Every export is logged on the child’s record.
For an inspection, the evidence is already in place: chronologies, plans, referrals, who saw each record and when, and staff training and policy sign-off from the compliance area.
Safeguarding work happens in shared spaces. Two controls sit at the top of every screen.
On duty at lunch or on a trip, staff can log a concern from their phone, dictate it rather than type, and send it straight to the safeguarding team. They can add more detail on a computer later.
If it’s urgent, the DSL team gets a phone alert, and the screen reminds the member of staff to find a DSL in person as well.
A 30-minute demo shaped around how your staff record concerns today. Every plan includes the other Pupil Protect products too, so turn them on when you’re ready.