A confident school community
Give pupils regular, age-appropriate practice and staff time to learn. Use games and online scenarios as teaching contexts, including for children who do not game.
#PLAY4GOOD / SCHOOLS
Build digital confidence across pupils, staff and families — with practical lessons, safer school systems and a trusted response when something goes wrong.
Co-founded by ESPORTS.NGO and Valvur.AI · With Passport.GG as ecosystem partner
01 / A WHOLE-SCHOOL APPROACH
Give pupils regular, age-appropriate practice and staff time to learn. Use games and online scenarios as teaching contexts, including for children who do not game.
Name a safeguarding contact and a backup. Offer an accessible reporting route that pupils can actually find. Explain confidentiality limits before a disclosure.
Give IT a clear owner for access, updates, backups and suppliers. Safeguarding tools and a secure network solve different parts of the problem.
02 / SUGGESTED FIRST 30 DAYS
A suggested starting plan, adapted to your school’s age groups, local duties and existing policies. A pilot’s scope and support would be agreed with your team.
| When | Who owns it | What to do | Useful output |
|---|---|---|---|
| Week 1 · Organise | Headteacher + safeguarding lead | Name accountable leads; map reporting routes and approved apps; ask pupils and families what feels difficult. Keep surveys anonymous where possible. | A one-page contact and escalation map. |
| Week 2 · Secure | IT lead + service providers | Review account access, staff MFA, updates, protected backups and restoration. Practice a phishing report without blame. | An owned list of priority technical fixes. |
| Week 3 · Learn together | Teachers + pupil voice + families | Run one practical lesson per age group; invite parents to a settings workshop. Teach reporting, scam awareness and AI scepticism through fictional examples. | A lesson log and one family conversation prompt. |
| Week 4 · Rehearse & improve | Leadership + safeguarding + IT | Walk through a fictional bullying or account-takeover incident. Check the handoff between welfare and technical teams. Review what pupils can now do. | A revised response plan and a next-term schedule. |
03 / FROM AWARENESS TO PRACTICE
| Suggested learning stage | Activity | What pupils should be able to do |
|---|---|---|
| Younger pupils · around 7–10 | Use fictional messages to spot a suspicious prize, decide what stays private and practise asking an adult for help. | Pause before a link; name a trusted adult; show where to get help. |
| Early teens · around 11–13 | Explore chat settings, pressure to move to a private app, manipulated media and respectful team play. | Set a contact boundary; report unwanted contact; check a claim outside the chat. |
| Older teens · around 14–17 | Discuss account theft, coercion, fake tournaments, AI companions and consent using fictional scenarios. | Explain a reporting choice, protect an account and support a friend without sharing harmful material. |
| Staff & families | Run a short reporting drill and a joint settings session. Discuss how to respond calmly to a disclosure. | Know the school contact, the escalation route and the boundary between family support and investigation. |
Age ranges are teaching suggestions, not platform access permissions. Adapt to pupils’ development, disability, language and individual support needs. Never ask pupils to disclose incidents in class or create harmful material for an exercise.
04 / RECOMMENDED BASELINE
Your next actions0 of 8 marked for planning
Optional planning aid. Ticks are saved only in this browser; they are not a safety score, audit or badge approval. Do not enter personal or incident data.
05 / WHEN SOMETHING HAPPENS
Thank the pupil for telling you. Do not promise complete secrecy or make access to help depend on a perfect account of events. Use local emergency services if there is immediate danger.
Follow the school’s child-protection process. Record only necessary facts in the approved system. Decide family contact with the lead; it may be unsafe to contact a particular adult.
Record usernames, URLs, times and non-explicit threats when safe. Do not download, copy or circulate sexual images of under-18s, including to a parent group or workshop.
Use platform reports and appropriate local authorities. Let authorised IT staff handle account recovery or cyber incidents. Restrict access to records and arrange a follow-up with the pupil.
06 / HOW WE CAN WORK TOGETHER
Explore a school programme connecting age-relevant learning, staff and family participation, progress views and practical protection. For a VYBE pilot, agree the features, deployment, data handling and human response responsibilities before rollout.
Help shape community engagement, workshops and partnerships around positive gaming and digital participation.
Explore age-relevant learning, family engagement and technical protection in an agreed pilot. Confirm hosting, access, integrations and human oversight during scoping.
Own safeguarding decisions, curriculum fit and supplier due diligence. Treat AI signals as prompts for human review; a flag is not evidence that a child has done something wrong.
A school taking part in learning activities does not automatically receive a VYBE service badge. The public resources are free to read.
TAKE THE NEXT STEP
Tell us your age groups, country and whether you represent a school, network or education authority. We can scope a practical pilot with agreed responsibilities.
Discuss a school pilot →Opens your email app. No application is submitted on this page. Please do not include children’s personal information or incident evidence.
SOURCES & REVIEW
These recommendations combine VYBE’s proposed programme design with the official guidance below. Sources inform the content; the organisations linked here have not endorsed VYBE. Guidance reviewed 13 November 2026.
ONE CONNECTED COMMUNITY