For schools
Give pupils a real brief, and give teachers a real say in what counts
Aurelia lets a teacher set a genuine task, watch the work take shape, give feedback that matters, and verify what a pupil can actually do — inside clear roles and a safeguarding workflow behind it.
The supported chain, end to end
Verified teacher, brief, pupil submission, review, verified Passport entry
This is the chain Aurelia supports today. Nothing skips a step, nothing is verified because it was popular, and a teacher can always send work back for revision rather than sign it off.
- 01
Verified teacher & cohort
A verified teacher is assigned to a class or cohort by the School Admin. Nothing below happens outside that assignment.
- 02
Educator brief
The teacher issues a brief with clear success criteria to that cohort — a real task, not a form to complete.
- 03
The child submits their own project
The pupil makes the work in the Creator Studio and chooses to submit an eligible project against the brief themselves.
- 04
Teacher review
The teacher reviews the submission and the evidence behind it, gives constructive feedback, and can request a revision instead of verifying.
- 05
Revision, if asked for
A revision request sends the work back to the pupil with specifics. The project keeps its history rather than starting again.
- 06
Evidence-backed verification
When the teacher is satisfied, they verify the skill demonstrated, and that evidence-backed achievement is written to the pupil's Achievement Passport.
What verification asks of a teacher
A professional act, not a button
Verifying an achievement means a named teacher is putting their judgement behind it — that they reviewed the evidence and genuinely believe the pupil demonstrated the skill. It is deliberately harder to earn than a badge, and it is written to the pupil's Achievement Passport for them to keep.
Class oversight
Scoped access, not blanket visibility
Oversight in Aurelia mirrors how a school actually works — a teacher sees their classes, a School Admin sees the school, and nobody sees more than their role requires.
- Teachers see only the pupils and classes they have been assigned, never the whole school by default.
- School Admins see aggregate and case-level information across their own school, with every access logged.
- There is no cross-school directory of children. A school cannot browse, search or contact pupils belonging to another school or group.
- Where a school belongs to an education group, group-level oversight is reporting and governance — it does not create a shared pupil directory.
- Guardian approval still governs whether a piece of work can be shared beyond the class, even once a teacher has reviewed it.
- Class rosters and staff assignments are set by the School Admin and enforced at the database level, not just in the interface.
Safeguarding and oversight
A clear route from concern to resolution
Every school using Aurelia operates the same underlying safeguarding workflow, in plain language: a concern raised by anyone — pupil, parent or staff — is triaged by the designated safeguarding lead, escalated where needed through the platform-wide reporting route, and recorded on an auditable trail the school can be held to account against. It is never left to informal handling.
Educator resource library
Brief templates and starters, ready to adapt
Educator briefs, project starters, constructive-feedback guidance and digital-wellbeing material — written for teachers to adapt to their own class rather than use as-is. All of it is example material, not pupil work.
- Educator starter-brief templates across podcast, film, story, design, invention and coding
- How to give constructive feedback on a child's project
- A one-page project-planning worksheet to hand out
Integration-ready architecture
Built to connect, honestly described
Aurelia does not currently integrate with any school MIS, LMS or timetabling system. The platform is built with an integration-ready architecture as a direction for the future, but nothing here should be read as a live integration claim — today, everything runs inside Aurelia itself.
Updates, events & visibility
One place for a school to keep track
For teachers and school admins, Aurelia is working toward a single, quiet view of what's coming up and what's already been verified.
- Class and brief calendars showing what's due, what's in review and what's been verified — product direction, not a description of what is live today.
- Reminders for upcoming brief deadlines and pending verifications, so nothing sits unreviewed by accident — planned, and not yet live.
- School-level visibility of pupil progress toward the Achievement Passport, scoped to the classes a teacher is actually assigned. Aurelia is designed for this; the parts that are live are the verification workflow itself.
- Anything described here is designed to run inside Aurelia itself — it does not read from or write to a school's existing MIS, timetable or messaging systems.
Staff roles and setup
Roles built around real school structure
Every member of staff who touches Aurelia is assigned a role that matches their actual responsibility, and access follows that role automatically.
Teacher
Sets briefs, reviews submitted work and verifies achievements for the classes they are assigned to — nothing outside that scope.
School Admin
Manages staff and class rosters, oversees safeguarding cases raised within the school, and reports to the education group where one exists.
Designated safeguarding lead
Receives escalated concerns, coordinates the school's response and maintains the audit trail of any case involving a pupil.
A school is set up through an invitation from Aurelia or from its education group, with a School Admin verified first. That admin then invites teaching staff, builds class rosters, and coordinates with families as pupils are added — each step verified before the next is unlocked.
Bring Aurelia into your school
We work with schools individually to set up staff roles, classes and safeguarding contacts before any pupil joins.