AlgoPath for schools

Teach Computer Science with clearer evidence and better support.

Students combine independent study with assigned GCSE or A-level work. Teachers can manage classes, assign activities, review evidence and collaborate on hosted code.

Teaching support at a glance

Plan, assign, review and help.

Keep teaching actions in the correct class context, from adding learners to reviewing a practical trace and recording an attributed Help session.

See how the class is progressing

Review topic completion, exam-skill progress, assignments and practical evidence without turning learning into a public ranking.

Assign the right next activity

Assign a concept breakthrough, combined mark booster, mock or full topic to a class, group or individual learner.

Support code collaboratively

Observe a learner's AlgoPath Notebook and use an authorised Help session with visible attribution and before-and-after evidence.

Designed around membership contexts

One person can learn and teach in more than one place.

Permissions come from the selected school and class membership. Personal learning remains distinct from school assignments without forcing separate accounts.

Teachers can

  • See individual and class progress
  • Assign topics and focused revision journeys
  • Manage classes and student membership
  • Observe and Help in authorised AlgoPath Notebooks
  • Keep attributed notes and collaboration evidence
  • Download the reports available to their school

Students remain in control

  • Keep personal study beside assigned work
  • Open any course included in their access
  • See which context owns an assignment or Help event
  • Work inside their own learner workspace
  • Keep their information private from other schools

Questions from schools

Clear answers before you begin.

Can teachers assign work?

Yes. Teachers can assign journeys, topics and activities to the relevant class or learner while independent study remains available according to the learner's plan.

How is our school's data protected?

Teachers only see students who belong to their school and classes. Other schools cannot see your students, support notes, or reports.

How do students join a class?

A teacher gives students a secure class code. The code expires and can be replaced whenever the school needs a new one.

Can one account belong to several classes or schools?

This is the production target. A learner will keep personal and school contexts, while a teacher can hold authorised memberships for several classes or schools. The normalized membership migration remains a release gate for this first implementation slice.