NexusInnovation Hub Ltd
Sign in
Sign in
← Young Builders Hackathon

School information

What needs to be agreed before young people take part.

This is a planning guide for schools. It is not a direct sign-up page for children and it does not replace a school’s own safeguarding policies.

Before places are confirmed

One clear plan, shared by Nexus and the school.

The event is designed for school-led teams aged 12–16. Every participating school must nominate a lead adult and use its own safeguarding, consent and risk-assessment processes.

01School

Name the responsible adults

Confirm the school lead, accompanying staff, safeguarding contact, supervision ratio, arrival and departure arrangements.

02Parents

Use clear, separate permissions

Ask parents or carers about attendance, photographs or video, emergency information and any off-site arrangements. Keep this information with the school.

03Nexus

Confirm the event setup

Before the day, Nexus will confirm the event safeguarding lead, reporting route, adult code of conduct, venue risk controls and arrangements for mentors and judges.

Non-negotiables

Simple rules that protect children and adults.

  1. 01

    No direct child registration

    Register through the school only. Nexus will not collect child email addresses, home addresses, parent contacts or medical information through the public site.

  2. 02

    Visible, shared working spaces

    Mentors and judges do not work alone with a child, privately message them or exchange personal contact details. Any concern is reported immediately through the agreed safeguarding route.

  3. 03

    Privacy-first AI use

    Teams must not enter real pupil data, personal stories that identify someone, school records, photographs, medical information or confidential documents into AI tools. Use made-up or anonymised examples instead.

  4. 04

    Projects stay with the teams

    Teams keep ownership of what they make. Nexus may only share a project name, short description, image or demonstration where the school and parent or carer permissions allow it.

Parent or carer consent template

Use this as a starting point, through the school.

The school should adapt this to its own policies and keep the completed forms. Do not send completed consent forms to Nexus unless we have specifically agreed a secure process.

Nexus Young Builders Hackathon, Saturday 17 April 2027

My child has permission to take part as part of a school-led team. I understand that the event involves supervised group work to create a simple AI prototype. The school remains my main point of contact.

Please choose separately:

  • My child may attend the event.
  • My child may be photographed or filmed for school records.
  • My child may be photographed or filmed for Nexus event reporting, website or social media.
  • My child’s first name, team name or project may be mentioned publicly.
  • My child may receive the prize through the school or another school-approved route, if their team wins.

Contact details for parent/carer, emergency arrangements, medical needs and travel permissions should stay with the school.

Next step

Start with a school-led conversation.

Once the lead adult has read this information, they can register school interest. We will then agree the practical and safeguarding details before confirming any places.

Register school interest