What is LEAP?
LEAP — the Learning, Execution and Acceleration Platform — turns a syllabus document into a taught, assessed, and measured course.
A syllabus is a statement of intent. Everything after it is execution. LEAP takes the document an institution has already approved and carries it all the way through — structure, lesson plans, teaching scripts, materials, assessments, marks and the evidence of who learned what.
What the name means
The three words are the three problems the platform was built to solve, in the order institutions hit them.
The problem it addresses
Institutions rarely lack a curriculum. What they lack is a reliable path from that curriculum to consistent delivery and honest evidence of outcomes.
- Preparation does not scale. Every faculty member rebuilds lesson plans, question banks and materials from the same syllabus, in isolation, each term.
- Delivery is uneven. Two sections of the same course diverge because nothing captures how the course is supposed to be taught, only what it is supposed to cover.
- Assessment is disconnected from the curriculum. A question paper rarely carries a machine-readable link back to the outcome it is testing, so attainment reporting becomes a manual reconstruction at term end.
- Intervention arrives too late. A student who has fallen behind is usually identified by a failed exam — after the point where anything could have been done about it.
- Evidence is assembled, not accumulated. Accreditation reporting is a scramble through spreadsheets, because nothing recorded outcome attainment as it happened.
LEAP is not a content library and not a replacement for a teacher. It generates a first draft grounded in your syllabus, and a faculty member approves, edits or rejects it. Nothing generated reaches a student without that approval.
How it works, end to end
One pass through the platform, from an uploaded document to a measured cohort.
- 1A syllabus is uploaded
A PDF, DOCX or pasted text. Scanned documents are OCR-ed first, with a confidence flag on low-quality pages.
- 2Extraction builds a structure
The document becomes strands, learning outcomes, and a sequenced set of gates, each mapped to a Bloom level and its prerequisites. This is the knowledge graph everything else hangs off.
- 3Faculty review and correct it
The Review Extracted screen is fully editable. Correcting a strand name or reordering gates cascades to dependent outcomes, lesson plans and quiz groups, with a preview before you commit.
- 4Generation fills in the course
Once approved, lesson plans, four-stage Socratic teaching scripts, question banks and study materials are generated per gate as background jobs.
- 5The course is taught
The lesson workspace carries the plan, the script, the materials, attendance and a recording for each session. Students work through gates in sequence.
- 6Assessment feeds mastery
Online quizzes, locked-down exams and scanned paper scripts all resolve to per-question attempts, which roll into per-gate mastery and a Bloom ceiling for every student.
- 7The gaps drive the next action
Class analytics surface where the cohort stalled; remediation assigns each student the prerequisite material that covers their actual gap, not a re-read of the gate they failed.
Who uses it
Four roles, four separate experiences. A user has one role per account, and the application they see is determined by it — there is no shared dashboard with hidden sections.
One platform, many institutions
LEAP is multi-tenant. Every institution is isolated at the data layer — every query is scoped by institution at the repository boundary rather than in route handlers — and each can have its own subdomain, branding and sign-in.
Institution name, tagline, logo and sign-in are all configuration, resolved from the host at runtime — a tenant on its own subdomain sees its own branding throughout the application.
This documentation is deliberately tenant-neutral. It describes the product, which is identical for every institution, so it carries no institution name of its own.