BridgeBack prepares
A concept map linked to the lesson sources, a short check-in, a catch-up route, and small learning activities.
Explore the complete product journey, then see how BridgeBack fits lesson planning, teacher review, and pupil support in school.
Built for a school rollout
One workspace connects the next lesson to the support a pupil needs.
Teachers keep control of the route while school leaders set the privacy, safeguarding, and security requirements.
A complete class, lesson, diagnostic, and catch-up route that a school can explore from both sides of the experience.
One-click teacher and pupil entry
Prepared state for presentation reliability
Live model actions use the product workflow
Reset the journey and try it again
A secure place for classes, lesson resources, teacher checks, and pupil learning routes.
Clerk sign-in with access checked again in Convex
Private lesson storage for each school
Teacher review before pupils see AI-written content
A record of important admin actions
The school provides curriculum intent and oversight. BridgeBack performs the repetitive transformation work and keeps each proposal inspectable. Whether this saves teacher time is a pilot question, not a claim we make today.
Upcoming lesson materials and learning objectives
Relevant scheme of work, slides, and worksheets
The class, pupil invitation, and teaching context
A teacher responsible for reviewing the route
A concept map linked to the lesson sources, a short check-in, a catch-up route, and small learning activities.
The earlier concepts, correct answers, pupil assignment, and how the route is used alongside classroom support.
A good pilot needs more than an IT setup. Schools need people responsible for teaching quality, safeguarding, privacy, and the pupil experience.
Check the lesson sources, make sure the concept map is accurate, and agree how readiness will be judged.
Review the graph, approve the route, and provide human support when the pupil needs it.
Check why data is needed, complete the DPIA, agree how long data is kept, and set clear routes for help or concerns.
Check sign-in, separation between schools, file handling, logs, deletion, service settings, and what happens if something goes wrong.
Help test clarity, accessibility, agency, and whether the experience feels supportive rather than punitive.
Each service has a defined responsibility. Secrets and access checks stay server-side.
Server-rendered product and marketing routes, API boundaries, and secure response headers.
Identity and sessions for teachers, pupils, and organisation access.
Organisation-scoped records, private resources, realtime state, mutations, and audit events.
Reads lesson material when an analysis is requested and returns the draft in a set format. Store is set to false.
Allowed fields, references, questions, and learning-module shapes validated before storage.
Shows the concept map in a form that teachers can review and correct.
Sol handles the hardest lesson analysis. Terra creates the check-in. Luna writes short pupil activities quickly and efficiently.
Read the model guidanceLesson mapping
Read several lesson resources, find the main lesson idea, map the earlier ideas, and link each one to its source.
It cannot approve its own concept map.
Check-in questions
Create short multiple-choice questions from the teacher-approved concept map.
It cannot mark answers or choose the pupil's route.
Pupil support
Write short explanations and checks for one to three concepts.
It cannot see the pupil's name or reason for absence.
Optional visual
Create a clear educational illustration for up to two pupil activities when a picture would help.
It cannot receive pupil identity, attendance context, marks, or grades.
Review the complete teacher and pupil journey, including the concept map, diagnostic, pathway, and progress view.
Add the school's scheme of work, lesson resources, classes, and the teachers responsible for checking each route.
Complete the DPIA, contracts, access checks, retention settings, security review, and named safeguarding ownership.
Review teaching quality, accessibility, fairness, incidents, teacher effort, and whether pupils can rejoin the target lesson.
The first evaluation should test whether the workflow is useful and safe before making claims about attendance or attainment.
Time to upload, review, correct, and assign a route.
How often teachers accept, edit, add, or remove earlier concepts.
Clarity, anxiety, agency, accessibility, stopping, and requests for teacher help.
Whether teachers judge that the pupil can participate in the target lesson.
See the teacher and pupil journeys together, then plan how BridgeBack could fit your school.