The Teacher Programs section in the Admin menu has 4 pages — Orientation Admin, Induction Admin, Competency Admin, AI Maturity Admin — that sit in timeline order. Together they cover a teacher's whole growth journey from "applying to join the network" through "running a department". On a first read this can look like a lot. This page walks you through it in plain English. If a word looks new, Section 7 — Glossary explains it.

A short promise
You do not need to know all 4 systems by heart today. The 4 pages live on a shared Cambridge anchor (Cambridge Teacher Standards 2023, the 27 CTS items). Once you understand that anchor, the 4 pages all click into place — each one just measures growth at a different point in the teacher's career.
🎯
What is the Teacher Programs section?
A small workspace for the people running Eduversal's teacher development pipeline. Orientation is the front door (pre-approval). Induction is the year-1 mentored journey. Competency is the lifelong 4-level CPD ladder. AI Maturity is the network-wide AI fluency cycle.
👥
Who uses it?
The Admin dropdown is gated to central_admin. In practice the Teacher Programs section is read and used by HQ Directors and the central_admin team. The teachers themselves engage with the four systems on the Teachers Hub side (their own dashboards) — these admin pages are the HQ-side review + triage surfaces.
The four pages are independent systems, not a workflow. A teacher can be on Orientation today, Induction next year, Competency for the rest of their career, and AI Maturity every annual cycle — all at once or in sequence. Don't expect data to flow automatically from one page to the next. Each system has its own collection, its own rubric, and its own Charter rules.

The 4 pages were reordered 2026-05-20 to match the order a new teacher actually moves through them. Read left-to-right — that's the same order they live in the navbar.

1
🎓
Stage 1 · Pre-approval
Orientation
A teacher applies via the public /orientation form. HQ reviews their answers + Cambridge familiarity self-rating before approving.
Orientation Admin →
2
📕
Stage 2 · Year 1
Induction
Approved teacher gets a mentor + a year-1 handbook + 4 windows of walkthroughs. HQ assigns the mentor here.
Induction Admin →
3
🧗
Stage 3 · Lifelong
Competency
Year 2 onwards. Teacher claims a level (1-4) per competency by submitting evidence. HQ reviews + issues certificates.
Competency Admin →
4
🤖
Stage 4 · Annual
AI Maturity
Each annual cycle, teachers self-assess on the AI Competency Framework v1.0. HQ triages institutional-level submissions here.
AI Maturity Admin →
This is the new-hire timeline, not a strict rule. A 10-year-veteran joining Eduversal still goes through Orientation (HQ approval) but may skip past Induction's mentee experience and go straight to Competency claims at Level 3 or 4. AI Maturity runs annually for every staff member regardless of where they sit on the timeline. The four pages are independent surfaces — use whichever one fits the person in front of you.

Four pages — one card each. The cards follow the same order they appear in the Admin dropdown (the 2026-05-20 timeline ordering).

🎓
Orientation Admin
/orientation-admin
Open page →
What it is
The HQ-side triage queue for partner-school teachers who fill out the public /orientation questionnaire before they get full Teachers Hub access. Three tabs: Registrations (incoming submissions to review / mark reviewed / reject) · Resources (the handbook + video + book + link library every candidate sees) · Competency Questions (the multiple-choice quiz with optional Cambridge Teacher Standards refs).
Why we built it
Partner schools nominate teachers; Eduversal vets them. Before this page, that vetting happened in spreadsheets + email. The Orientation page captures the candidate's profile, Cambridge familiarity self-rating, and quiz answers in one place — so HQ can decide approve / reject with the same evidence base for every candidate.
Day 1 view
A list of registrations grouped by status (pending → reviewed → approved → rejected). Each row shows name + school + subjects + submission date. Open a row to see the full questionnaire + quiz scores + per-question Cambridge anchor chips.
What to do
Work the Registrations tab first. For each pending submission: read the questionnaire, check the quiz score, decide approve / reject. Approving here does NOT create a Teachers Hub login — it just marks the candidate ready for the next step (the school formally adds them in /staff, which triggers the staff↔users bridge on their first sign-in).
  • Resources tab — curate what every candidate sees in their orientation packet. Use the order field to control display sequence.
  • Competency Questions tab — each quiz item can carry CTS refs (e.g. CTS 1.4, 3.1) so the same Cambridge anchor used by KPI / Appraisal / Competency also threads through onboarding. Valid CTS range: 1.1–1.5, 2.1–2.5, 3.1–3.8, 4.1–4.5, 5.1–5.4.
📕
Induction Admin
/induction-admin
Open page →
What it is
The HQ-side console for Eduversal's year-1 mentee system. Four tabs: Assignments (create + monitor each new hire's induction) · Mentor Certifications (issue + expire mentor_certifications) · Programs (a bookshelf grid of the 10 handbooks — 3 induction + 7 role-operational) · Alarms (Cloud-Function-maintained low-pulse alerts).
Why we built it
The first 12 months of a new hire's career set the tone for everything after. Eduversal pairs every Year-1 teacher / specialist / principal with a certified mentor, a year-1 handbook, and a 4-window walkthrough cycle. The Charter Non-Negotiables (see Section 4) enforce the rules — you can't accidentally assign an uncertified mentor or shortcut the three-party assignment.
Day 1 view
Assignments tab shows every active mentee with their stage (window 1-4), pulse trend, and mentor name. Programs tab shows the 10 handbooks as spine cards on a bookshelf — click any to view in the /handbook reader.
What to do
For a new mentee: first verify their mentor has an active mentor_certifications doc (issue one if not), THEN create the assignment with the three named parties (mentee uid + mentor uid + school leader uid). The rule blocks any other shape.
  • Handbooks are JSON-first. Don't edit induction_programs/{id} directly in Firestore — edit docs/induction/handbook-*.json, bump version, then run node scripts/induction/seed-induction-programs.js --apply. Direct Firestore edits get reverted on the next seed.
  • The Alarms tab is read-only — it surfaces the induction_alarms docs written by the onPulseWritten Cloud Function when a mentee logs ≤1 pulse in 2 weeks. Reach out to the mentor; don't try to clear the alarm from here.
🧗
Competency Admin
/competency-admin
Open page →
What it is
The HQ-side review surface for all 3 competency tracks — Teachers (TH), Leaders (AH), Specialists (CH). Tabs: Evidence (review submissions, approve or reject) · Heatmap (cohort coverage by domain × level) · Cohort (per-user progress) · Certificates (issue official competency certs). Track filter chip switches between the 3 tracks.
Why we built it
Competency is the lifelong CPD ladder — 4 levels (Foundation → Developing → Effective → Lead) per Cambridge-aligned competency. Teachers (and Leaders and Specialists) submit evidence to claim a level. HQ reviews, decides, and on approval the user_competencies/{uid}.earned* field flips. This page is where that review happens for the whole network.
Day 1 view
Evidence tab shows pending submissions across all 3 tracks. Each row: claimer name + track + competency + level + evidence link. Open to read the evidence, then approve (which writes the right earned* field by track) or reject (with reviewer note).
What to do
Pick a track filter (Teachers / Leaders / Specialists), work the Evidence queue from oldest to newest, decide approve / reject for each. Approving writes the per-platform earned* field automatically (earned for TH, earned_academic for AH, earned_central for CH) — don't try to write it yourself.
  • Evidence files live at competency_evidence/{platform}/{uid}/{ts}_{filename} in Cloud Storage (≤25 MB). Don't move them.
  • The Heatmap tab is for spotting cohort-level gaps (e.g. "no English teacher in our network has claimed the Assessment-for-Learning Lead level"). Use it for HQ-side professional development planning.
  • Issue certificates from the Certificates tab once a level is locked in.
🤖
AI Maturity Admin
/ai-maturity-admin
Open page →
What it is
The HQ triage queue for the network-wide AI fluency cycle. Teachers (AH side) self-assess on the AI Competency Framework v1.0 once per cycle; this page lets HQ validate institutional-level submissions, cohort-aggregate the responses (via the rebuildAiCompetencyAggregates Cloud Function), and read the readiness curve for the whole network.
Why we built it
AI literacy went from "nice to have" to "core competency" inside 18 months. The AICF v1.0 (Eduversal's own framework, anchored to UNESCO AI-CFT 2024 + Cambridge GenAI policy + EEF 2024 + Permendikdasmen 1/2026 + SKB 7 Menteri 2026) gives the network a shared vocabulary. This page is the HQ-side rolling read of where the network is — by school, by sub-role, by AICF block.
Day 1 view
A submission queue + cohort aggregate cards by school. Filter by sub-role (Teacher / Leader / Specialist). The Cloud Function rebuild runs on write, so opening the page on a fresh cycle shows the live up-to-date roll-up.
What to do
Once per cycle: read the cohort aggregates, look for under-attended cohorts (e.g. one school's principals haven't submitted), nudge those users via Mail Composer.
  • This admin page surfaces in the Admin dropdown's Teacher Programs column (moved here 2026-05-18 from its earlier location). The same Cloud Function maintains the AH-side /ai-maturity-self-assessment dashboards.
  • The AICF chip family (orange) shows the verbatim framework text on click — same wiring as CTS / SKL / PIGP / ES. Look for refs like aicf-teacher-practitioner-A.2 in the source canonicals.
  • Source-of-truth: docs/research/eduversal/ai-competency-framework/manifest.json + the practical/reference subfolders.

The Induction Charter has 5 rules that are rule-enforced at the Firestore level — not "we should follow these" but "the database physically rejects writes that break them". You'll bump into them on Induction Admin most often, but they shape what's possible across the whole Teacher Programs section. Memorise these 5.

NN1
Induction data NEVER feeds appraisal scoring
Year-1 mentee observations + journal + pulses live in their own collections. They never propagate into teacher_appraisals. Mentoring needs psychological safety; appraisal needs evidence. Two streams, by design.
NN2
HQ NEVER reads named journal entries
The induction_journal rule blocks list:false; get is gated by a visibility field the mentee controls. Aggregate counts go through induction_journal_aggregates (anonymised). Don't ask for a workaround.
NN3
Mentor must hold active certification
You can't create an induction_assignments row pointing at a mentor uid without an active mentor_certifications/{uid}_mentor_base doc. Issue the cert first via the Mentor Certifications tab.
NN4
Every assignment needs 3 named parties
induction_assignments create requires three uids: mentee + mentor + school leader. The rule blocks any other shape. No anonymous mentors, no missing leader — induction is a tripartite relationship by Charter.
NN5
Induction Completion Certificate is binary
No numeric scoring on the year-1 cert — completed or not completed. Platform-neutral (no "induction grade"). The competency ladder + appraisal are where ranked outcomes live; induction is pass/no-pass.
📁 Where this comes from. The full charter text — every rule, verbatim — lives at docs/induction/INDUCTION_CHARTER.json and is mirrored to dist/research/induction/INDUCTION_CHARTER.json on each build. The 5 rules are also rule-enforced in Central Hub/firestore.rules in the "INDUCTION MODULE" block. Don't loosen those rules client-side.

The 4 systems share a Cambridge anchor but otherwise stay separate. This is on purpose — different feedback streams need different rules. Read this once so you don't try to wire them together.

🔗
What they share
All 4 systems anchor to Cambridge Teacher Standards 2023 (the 27 CTS). Orientation quiz items can be CTS-tagged · Induction handbook tasks carry CTS chips · Competency framework has CTS refs per competency · AI Maturity (AICF) cross-references CTS in its practitioner blocks. Click any CTS chip anywhere in the system for the verbatim popover.
🚧
What they don't share
Data does not flow between the 4 systems. Approving a competency claim does NOT mark an induction task done. Submitting an AICF self-assessment does NOT update the orientation profile. Each system has its own Firestore collection, its own rubric, its own approval path. By Charter (NN1) induction data is also blocked from reaching the formal appraisal score.
🆚
Teacher Programs vs Performance Management
Teacher Programs (this section) is formative — it helps people grow. Performance Management (the Network Insights column: School / Teacher KPI Admin) and Appraisals (the previous section) are summative — they rate performance. Don't mix the metaphors. A teacher's growth in Competency is celebrated; their grade in Appraisal is what goes on the record.
🌐
Where teachers see the same 4 systems
Teachers Hub (TH) has the mirror surfaces: /orientation (the public form) · /my-induction (mentee dashboard) · /competency-framework + /my-portfolio (lifelong CPD) · /ai-maturity-self-assessment (cycle submission). The CH admin pages are HQ's review side; the TH pages are the teacher's growth side. Same systems, two lenses.

Pick the card that matches your role. The page detects your profile and reveals only the relevant card — but you can also read the others to understand what your colleagues see.

Every teacher-programs-flavoured word, defined in one sentence. If a word here still isn't clear, it's a candidate to bring up in the next Coordinators meeting.

Orientation— pre-approval
The public questionnaire at /orientation that partner-school teachers fill in before HQ formally approves them. Triaged on /orientation-admin. Not the same as Induction.
Induction— year-1 mentee journey
Eduversal's first-year mentored programme. 1 mentor + 1 handbook + 4 windows + walkthroughs + a journal + pulses. Governed by the 5 Charter Non-Negotiables. Distinct from Appraisal (NN1).
Competency— lifelong CPD ladder
The 4-level ladder (Foundation → Developing → Effective → Lead) per Cambridge-aligned competency. 3 tracks: Teachers (TH) · Leaders (AH) · Specialists (CH). Teacher-led; HQ reviews evidence.
AICF v1.0— AI Competency Framework
Eduversal's own AI fluency framework, anchored to UNESCO AI-CFT 2024 + Cambridge GenAI policy + EEF 2024 + Permendikdasmen 1/2026 + SKB 7 Menteri 2026. Lives at docs/research/eduversal/ai-competency-framework/.
CTS— Cambridge Teacher Standards
The 2023 27-item teacher standards. Every system in this section anchors to CTS. Click any CTS chip for the verbatim popover. Valid range: 1.1–1.5, 2.1–2.5, 3.1–3.8, 4.1–4.5, 5.1–5.4.
Charter NN1-NN5— Induction Non-Negotiables
5 rule-enforced guarantees on the Induction system (see Section 4). Source-of-truth: docs/induction/INDUCTION_CHARTER.json. Mirrored into firestore.rules.
Mentor Certification— prerequisite for assignment
A mentor_certifications/{uid}_mentor_base doc issued by central_admin via Induction Admin. NN3 blocks creating an induction_assignments row that points at an uncertified mentor.
Evidence— Competency claim attachment
The file or link a teacher attaches to claim a competency level. Lives at competency_evidence/{platform}/{uid}/{ts}_{filename} in Cloud Storage (≤25 MB). Reviewed on Competency Admin.
earned* field— per-platform
Three parallel fields on user_competencies/{uid}: earned (TH), earned_academic (AH), earned_central (CH). On approval, Competency Admin writes the right field by track.
Track— Competency audience
One of teachers (TH), leaders (AH), specialists (CH). Each has 6 domains × 24-29 competencies × 4 levels. Same shape, different content.
Pulse— mentee heartbeat
A short 1-5 weekly check-in a mentee logs during induction. Cloud Function watches for 2-week-low patterns and writes an induction_alarms doc — surfaced in Induction Admin's Alarms tab.
Window— Induction stage
One of 4 induction phases (Pre-arrival / Listen / Diagnose / Act+Anchor depending on handbook). The 4 windows structure the year-1 mentee timeline.
Cycle— AI Maturity cadence
The annual rhythm on which teachers self-assess on AICF v1.0. Cloud Function rebuildAiCompetencyAggregates rolls submissions up to cohort aggregates as they land.
No shame in asking.
If a page surprises you, a Charter rule doesn't make sense, or a Cambridge cross-reference looks off, raise it at the next Coordinators meeting or message the central_admin team directly. The whole point of the 4 systems being separate is that each one is independently auditable and questionable.
📁 Open all references 📚 Browse handbooks 🗣️ Raise it at the next meeting 💬 Submit feedback to HQ