Pilot principles

A serious pilot proves fit before scale.

Last updated: 16 June 2026

Plant Bot Computing pilot conversations are designed to test curriculum fit, workload, assessment discipline and pupil response before any wider licence or deployment decision.

What a pilot can cover

• A sample unit or age-range slice.
• Lesson-pack quality and teacher workload.
• Assessment blueprint, rubric and feedback model.
• Standards mapping for England, Wales or an international route.
• Google ecosystem deployment readiness.

What a pilot does not claim

• No awarding-body endorsement is claimed unless separately confirmed by the awarding body.
• No GCSE result, grade or progression outcome is guaranteed.
• No live exam papers, mark schemes or private assessment material should be uploaded into public tools.
• No learner accounts, Google Classroom access or Silica Lab access are created from the public enquiry form.

Data boundary

The first pilot enquiry should use organisational context only. Pupil names, pupil work, safeguarding details, medical information and private school files should stay out of the public form. If a pilot progresses, a separate data and access route must be agreed.

AI boundary

G-Root and any public AI assistant can explain the curriculum and pilot route. They do not replace teacher judgement, safeguarding processes, data-protection review or formal assessment moderation.

Human decision points

A human should confirm pilot scope, success criteria, timetable, staff owner, evidence pack, price if relevant and any deployment route before a pilot starts.

Professional review

Schools and partners should run their own safeguarding, procurement, data-protection and AI-use checks before adopting any curriculum, platform or AI-assisted workflow.