Share with your students, and their parents →

Safeguarding

How safeguarding concerns are reported at Tute

All safeguarding concerns raised are reported through our secure, built-in safeguarding system on the Tute platform. This ensures that every concern is captured accurately, reviewed promptly, and handled in line with statutory guidance.

How staff report a concern
When a staff member becomes aware of a safeguarding issue, they:

Our platform ensures a consistent standard of reporting and creates a clear, traceable audit trail for every concern raised.

Why this matters for partners

This process gives partners confidence that teachers follow a structured, accountable reporting pathway that supports timely intervention and multi-agency working.

What happens after a concern is reported

When a teacher submits a safeguarding concern through the Tute platform, the following process takes place.

  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7

Step 1: Concern submitted by the teacher

  • The teacher completes the safeguarding form in the platform as soon as possible after the incident. 
  • They include factual details only and attach any relevant evidence, for example chat logs, screenshots, or playback timestamps. 
  • The concern is automatically sent to Tute’s safeguarding team and logged in our safeguarding system.

Step 2: Initial review by Tute’s safeguarding team 

  • The DSL or Deputy DSL reviews the concern the same working day, and often much sooner during core hours. 
  • They check the content of the report, any attached evidence, and the student’s profile, including previous concerns, attendance and any known risks. 
  • The concern is then given a response level (1 to 5) in line with Tute’s safeguarding framework.

Step 3: Decision on action and who needs to be informed 

Based on the response level, the DSL decides what needs to happen next. This may include: 

  • internal monitoring only (for very low-level issues) 
  • sharing the concern with the student’s nominated safeguarding contact at the partner 
  • urgent phone contact with the partner where there is increased or immediate risk 
  • contact with local safeguarding partners such as MASH, social care, police or LADO for high-risk situations. 

For all Level 3 and all Level 4 and 5 concerns, the partner will be informed.

Step 4: Report shared with the partner safeguarding contact 

  • The concern is shared securely with the partner safeguarding contact, usually by encrypted email and recorded in the partner portal. 
  • The information provided will normally include: 
    • a factual summary of what has happened 
    • the date and time of the incident and report 
    • any immediate actions taken by Tute 
    • what we are asking the partner to do, for example welfare check, contact with home, referral to local services. 
  • For higher risk concerns, the DSL or DDSL will also follow up with a phone call to ensure the message has been received and understood.

Step 5: Partner acknowledgement 

To maintain a clear safeguarding audit trail and avoid delay, partners are expected to: 

  • acknowledge receipt of the concern in the partner portal or confirm from safeguarding report email 
  • confirm who will be taking ownership of the concern within the school or local authority team 
  • indicate any immediate actions they plan to take. 

Best practice is for this acknowledgement to happen the same day wherever possible and within one working day as a maximum.

Step 6: Partner action and feedback 

Once the concern has been acknowledged, the partner should: 

  • carry out appropriate action in line with local procedures, for example speaking to the child, contacting parents or carers, consulting with social care, updating existing plans or making a new referral 
  • record these actions on their own safeguarding system 
  • provide feedback to Tute on what has been done and any outcomes or next steps. 

Feedback can be provided by secure email or through the agreed communication route for that partnership. 

 

Providing feedback is best practice because it: 

  • helps Tute staff understand how the concern is being managed 
  • informs any further adjustments to teaching, communication or support in lessons 
  • supports multi agency working and a shared understanding of risk.

Step 7: Ongoing monitoring and follow up 

  • Tute’s safeguarding team records partner acknowledgement, actions and outcomes on our system. 
  • Where there is ongoing risk or concern, the DSL may request further updates from the partner and continue to monitor the situation. 
  • Repeated or linked concerns may lead to additional contact with the partner to review support, attendance or the student’s timetable.
  • Patterns and trends are reviewed weekly by the safeguarding team and monthly as part of wider safeguarding reporting. 
  • Learning from serious or repeated incidents may be used to update guidance for teachers, partners or students.

Step 1: Concern submitted by the teacher 

  • The teacher completes the safeguarding form in the platform as soon as possible after the incident. 
  • They include factual details only and attach any relevant evidence, for example chat logs, screenshots, or playback timestamps. 
  • The concern is automatically sent to Tute’s safeguarding team and logged in our safeguarding system. 

Step 2: Initial review by Tute’s safeguarding team 

  • The DSL or Deputy DSL reviews the concern the same working day, and often much sooner during core hours. 
  • They check the content of the report, any attached evidence, and the student’s profile, including previous concerns, attendance and any known risks. 
  • The concern is then given a response level (1 to 5) in line with Tute’s safeguarding framework.

Step 3: Decision on action and who needs to be informed 

Based on the response level, the DSL decides what needs to happen next. This may include: 

  • internal monitoring only (for very low-level issues) 
  • sharing the concern with the student’s nominated safeguarding contact at the partner 
  • urgent phone contact with the partner where there is increased or immediate risk 
  • contact with local safeguarding partners such as MASH, social care, police or LADO for high-risk situations. 

For all Level 3 and all Level 4 and 5 concerns, the partner will be informed.

Step 4: Report shared with the partner safeguarding contact 

  • The concern is shared securely with the partner safeguarding contact, usually by encrypted email and recorded in the partner portal. 
  • The information provided will normally include: 
    • a factual summary of what has happened 
    • the date and time of the incident and report 
    • any immediate actions taken by Tute 
    • what we are asking the partner to do, for example welfare check, contact with home, referral to local services. 
  • For higher risk concerns, the DSL or DDSL will also follow up with a phone call to ensure the message has been received and understood.

Step 5: Partner acknowledgement 

To maintain a clear safeguarding audit trail and avoid delay, partners are expected to: 

  • acknowledge receipt of the concern in the partner portal or confirm from safeguarding report email 
  • confirm who will be taking ownership of the concern within the school or local authority team 
  • indicate any immediate actions they plan to take. 

Best practice is for this acknowledgement to happen the same day wherever possible and within one working day as a maximum.

Step 6: Partner action and feedback 

Once the concern has been acknowledged, the partner should: 

  • carry out appropriate action in line with local procedures, for example speaking to the child, contacting parents or carers, consulting with social care, updating existing plans or making a new referral 
  • record these actions on their own safeguarding system 
  • provide feedback to Tute on what has been done and any outcomes or next steps. 

Feedback can be provided by secure email or through the agreed communication route for that partnership. 

 

Providing feedback is best practice because it: 

  • helps Tute staff understand how the concern is being managed 
  • informs any further adjustments to teaching, communication or support in lessons 
  • supports multi agency working and a shared understanding of risk.

Step 7: Ongoing monitoring and follow up 

  • Tute’s safeguarding team records partner acknowledgement, actions and outcomes on our system. 
  • Where there is ongoing risk or concern, the DSL may request further updates from the partner and continue to monitor the situation. 
  • Repeated or linked concerns may lead to additional contact with the partner to review support, attendance or the student’s timetable.
  • Patterns and trends are reviewed weekly by the safeguarding team and monthly as part of wider safeguarding reporting. 
  • Learning from serious or repeated incidents may be used to update guidance for teachers, partners or students.

Partner responsibilities

text

Safeguarding categories

Safeguarding categories and response levels

Every concern is assigned a response level to determine the appropriate action:

Level 1 – No action

Invalid, duplicate or error submissions.

Level 2 – Monitoring

Low-level concern, monitored internally.

Level 3 – Shared

Concern sent to the student’s safeguarding contact(s)

Level 4 – Escalated

Concern shared and followed up via phone call due to urgency or increased risk.

Level 5 – Critical

Immediate danger / significant harm. Involves emergency services, MASH, police or LADO

Additional guidance and resources

Key contacts

Tute Safeguarding Team – safeguarding@tute.com

DSL: Rob Hughes – rob.hughes@tute.com

DDSL: Hollie McFarlane – hollie.mcfarlane@tute.com

Safeguarding policies

  • Safeguarding policy
  • Safeguarding letter of assurance
  • Safeguarding training and development policy
  • Safer recruitment policy

Got a question? Need some help?

Visit our FAQs and how-to videos page for instant answers to our partners’ most asked questions

Can’t find an answer to your question?

Speak to your dedicated account manager who will be happy to help with any of your queries