The School Leaders Workspace has many pages. On your first visit, this is normal — but it can feel like a lot. We made this page to help you get comfortable, step by step. The language is plain. If a word looks new, you will find it explained in Section 7 — Glossary.
What is Academic Hub?
The portal for partner school leadership — Foundation Reps, School Principals, Academic Coordinators, and Cambridge Coordinators. We use it to track assessment, appraisal, KPI, induction, and school-quality work across the network.
What is the School Leaders Workspace?
A group of 7 pages where the leadership team at your school runs the operational week — meetings, decisions, activities, artifacts, plus the directory. The school-scoped counterpart to HQ's Coordinators workspace at Central Hub.
🔒 Same-school visibility. Every row this workspace creates carries a
schoolId. Only the leadership team at this school can read it. Other partner schools cannot. HQ admin can — but that is an audit path, not a daily one.
The pages tell one story: meetings raise topics, proposals debate the big ones, decisions make them binding, activities do the work, artifacts anchor it. The directory keeps track of who is in the room.
1
Step 1 · Meet
Meetings
Capture what was discussed. Tag each agenda item as decision, action, discussion, announcement, or red-text.
Open →
2
Step 2 · Discuss
Proposals
Debate the big "should we?" questions — KPI, assessment, curriculum — in phases before deciding. The Principal promotes the agreed ones.
Open →
3
Step 3 · Decide
Decisions
Binding rules from meetings or promoted proposals. Auditable across academic years. Supersede rather than edit — never lose the trail.
Open →
4
Step 4 · Do
Activities
Kanban work that flows from decisions. Action-tagged meeting items spawn cards here automatically.
Open →
5
Step 5 · Anchor
Artifacts
Living documents (Annual Plan, SoW, intervention plans) that decisions + activities point to.
Open →
Directory — the people side
The leadership team at your school. Curated — not auto-synced from the user database — so transitions are reflected immediately. Search by name, subject, or role.
Personal lenses. Three other pages — My Observations, Team Induction, and Weekly Checklist — are your personal views on the same school context. They do not change the flow; they show you your own slice of it.
Each card below tells you four things: what the page is, why we built it, what you will see on day 1, and what to do.
Operational Guide
/school-leadership-operational-guide
What it is
First-90-days handbooks for the four leadership sub-roles (Foundation Rep, Principal, Academic Coordinator, Cambridge Coordinator). Tells you why your role exists and how to ramp up.
Why we built it
Leadership work is not a tick-box. The Operational Guide answers the "why this role exists" question; the Weekly Checklist answers the "what to do this week" question. Together they give you both the rationale and the rhythm.
Day 1 view
If you hold a single sub-role, you go straight to your handbook (one click from the navbar). If you hold more than one — or you are an academic admin — you land on the picker page first, with all four cards visible and your active sub-role pinned at the top. Every handbook is 4 stages over 12 weeks: Stage 0 (pre-arrival) + 3 × 30-day windows. Foundation Rep / Academic Coord / Cambridge Coord use generic "Window 1-2-3" labels; the Principal handbook names them Stabilise → Diagnose → Steer.
What to do
Read Stage 0 + Window 1 (or Stabilise) for your sub-role this week. Skim Windows 2-3. You do not need to finish anything — just get the shape of your first 90 days. Append
?stay=1 to the URL if you want to land on the picker even with a single sub-role (useful for browsing sibling handbooks).Meetings
/school-leadership-meetings
What it is
Leadership team meeting minutes. Each meeting carries agenda items; items can be tagged decision, action, discussion, announcement, or red-text.
Why we built it
Most binding rules originate from leadership meetings. Capturing the discussion + tag pattern creates the audit trail Eduversal needs for school-quality reviews — and it lets us auto-spawn work into Activities + Decisions instead of someone copy-pasting manually.
Day 1 view
You will see recent meeting minutes for your school. Open the most recent one — the agenda items give you the live context for what is currently being discussed.
What to do
Read the most recent minute. Look at how items are tagged.
- Red-text items promote into the binding Decisions register.
- Action items spawn cards in Activities.
- Other tags stay as discussion — they shape the context but do not create downstream work.
Proposals (the discussion board)
/school-leadership-proposals
What it is
A discussion board for big ideas your leadership team is still talking about — before anyone decides. "Should we change how we weight KPIs?", "Should we trial a new diagnostic test?". You open a proposal, write the idea, and the team comments. When everyone agrees, the Principal turns it into a real decision. It sits one step before the Decisions page.
Why we built it
The old way was a shared doc where ideas got lost and you could not tell what stage anything was at. Here every idea has a clear phase and a searchable comment thread, so you always know what is just an idea, what is open for debate, and what has been decided.
The four phases
Each proposal moves left to right. The coloured pill on every card tells you where it is:
- Draft — the author is still writing it. Not yet open for the team.
- Open for comment — the discussion is live. Read it and add your view.
- Decided — agreed and promoted to the Decisions register, with a back-link.
- Parked — shelved for now, kept on the record so it can be re-opened later.
Who can do what
- Any leadership-team member can open a proposal, write the body, and add comments.
- Only the Principal sets the phase (Open / Parked) and promotes a proposal to a binding decision. The team shapes the idea; the Principal makes the call.
- Everything is scoped to your own school — other schools never see your proposals. The page carries a "How proposals work" panel at the top with the full phase legend + roles table.
What to do
Open the Open for comment tab and read what the team is debating. If you have a view, say it in the thread — that is the whole point. New idea worth raising school-wide? Hit "+ New proposal", write the problem, the options, and your recommendation.
Decisions
/school-leadership-decisions
What it is
The auditable register of binding school-level rules — "the dress code is X", "Year 7-8 observation feedback rooms have a third person present". Status:
active, draft, or superseded.Why we built it
When a school rule changes, the old version must stay visible so new staff understand the history. The supersede-rather-than-edit pattern keeps the trail intact. Auditors (and your future self) can answer "when did this become the rule, and what was the version before".
Day 1 view
Filter by Active. These are the binding rules at your school today. Know them.
What to do
Read the active register once. When a Decision changes, you create a new row that supersedes the old one — never edit a published decision in place. The old row stays visible, marked superseded.
Directory
/school-leadership-directory
What it is
The leadership team at your school. Curated — not auto-synced from the user database — so departures and transitions can be reflected immediately. Search by name, subject, or role.
Why we built it
A team transitions faster than user-account housekeeping. The directory carries the people-side of the workspace; if someone steps down or rotates, the directory reflects it the same day even if their user account stays active for a few weeks longer.
Day 1 view
You will see the current leadership team. Add yourself if you are not present; glance at the other leaders so the names + faces stick.
What to do
Make sure your own entry is correct. If a colleague is missing, add them. If someone has left, mark them inactive — do not delete (the audit trail keeps historical decisions readable).
Artifacts (School Resources)
/school-artifacts
What it is
Per-subject living documents — Annual Plan, Scheme of Work, lesson plans, internal assessments, intervention plans. Each subject card collects what is current; superseded versions stay archived.
Why we built it
Decisions + activities are abstract. Artifacts are the concrete things they point to. "Adopt the new SoW for Year 8 Maths" only means something when there is a real document at the end of the link.
Day 1 view
A grid of subject cards. Each card shows what is current. Empty cards mean nothing has been uploaded yet — that is normal for a brand-new term.
What to do
If you are an Academic Coordinator, check that the Annual Plan + SoW links work for the subjects in your scope. Other sub-roles: skim only — your daily work usually lives elsewhere.
Activities
/school-activities
What it is
School-scoped kanban. Mirrors the network-wide Activities surface but constrained to your school. Action-tagged meeting items can spawn cards here automatically; you can also create direct projects + tasks.
Why we built it
"What did we decide last meeting?" usually means "what work fell out of last meeting?". The kanban is the answer. Cards carry the meeting + decision they came from, so the lineage is always visible.
Day 1 view
Three columns: To Do · In Progress · Done. Cards filter to your school automatically.
What to do
Look at the In Progress column. If a card is yours (owner = you), check the deadline. If a card is stale (no movement in 2 weeks), say so in the next meeting.
My Observations
/my-observations
What it is
Your personal lens on formal appraisals + walkthroughs you have submitted as a leader. Submissions written through Teacher Appraisal Entry / Walkthrough Entry land here automatically.
Why we built it
A leader who runs 30 observations per term should be able to see them all in one place — without filtering the whole school table. This is that view.
Day 1 view
Empty. Observations populate after you submit them from the Teacher Appraisal / Walkthrough Entry pages.
What to do
Nothing on day 1. Come back once you have completed an observation cycle. Then watch the list grow.
Weekly Checklist
/weekly-checklist
What it is
Your personal lens on the operational rhythm for this week, scoped to your active sub-role. Pairs with the Operational Guide handbook for your role.
Why we built it
Leadership work has a weekly heartbeat. The checklist gives you the same rhythm every week — predictable, simple, with room to skip what is not relevant. It is a soft guide, not a test.
Day 1 view
A per-sub-role tab (Foundation Rep / Principal / Academic Coordinator / Cambridge Coordinator). You see only the tabs matching your sub-roles.
What to do
Friday afternoon — open it, tick what is done, leave the rest for next week. That is the rhythm.
Team Induction
/team-induction
What it is
The first-year inductions at your school. As School Principal you have read access to the team's progress, observation cycles, and pulse roll-up.
Why we built it
Year-1 staff are the highest-risk + highest-leverage group. If you spot a low-pulse pattern early, you can support before they leave. The team view is your early-warning system.
Day 1 view
If your school has any first-year staff, you will see their induction cards with pulse + cycle progress. If not, an empty state.
Confidential
Charter NN2 applies — aggregate signals (pulse, low-pulse alarm) are visible. Named individual journal entries are not. Watch the pulses, not the journals.
This is a soft list, not a test. Tick them off in your head — or your own notes — over the first 5 working days.
1
Day 1 — Open the Operational Guide
Read the handbook for your sub-role (Foundation Rep / Principal / Academic Coordinator / Cambridge Coordinator). Skim the 4-stage timeline. You do not need to finish — just get the shape.
2
Day 2 — Open the Directory
Add yourself if you are not present. Glance at the other leaders so the names + faces start to stick.
3
Day 3 — Open Meetings
Find the most recent minute. Read the agenda items — that is the live context for what is being discussed right now.
4
Day 4 — Open Decisions
Filter by Active. These are the binding rules at your school. Know them — they shape every day going forward.
5
Day 5 — Open Artifacts
Check that the Annual Plan + SoW links work for the subjects in scope. If something is missing, raise it at the next meeting (and tag the item as action).
6
Ongoing — Friday afternoon = Weekly Checklist
Tick what is done, leave the rest for next week. The checklist is the weekly heartbeat of the leadership rhythm.
The workspace adapts to who you are. The boxes below show only the ones that apply to your sub-role(s) today. They may change later if Eduversal updates your assignment.
This workspace is the operational hub. The wider Academic Hub has many other surfaces — you do not need them all today, but it helps to know they exist.
EASE I/II/III, Cambridge dashboards, school appraisals, KPI, accreditation, network audit, satisfaction surveys, Rapor Pendidikan 2025 — the dashboard suite under the Dashboards dropdown.
If you joined this school in the last 12 months as a Principal, the mentor-led year-1 induction handbook lives here. Listen → Diagnose → Act → Anchor windows over 365 days with an HQ-assigned external mentor. Complements (does not replace) the Operational Guide's 90-day operational ramp.
6 leadership domains × 24 competencies anchored in Cambridge School Leader Standards 2023. The handbooks point into specific competencies; this is where you track your evidence over time via My Portfolio + earn domain certificates.
Your personal CPD surface — Learning Path (24 leadership skills × 4 stages), My Portfolio (submit evidence), My Certificates (track earned domains). Pair with the Competency Framework above.
A library of all role guides + policy-topic books + AI playbooks. Each one explains a role in plain language and a 90-day ramp plan. Pair with your Weekly Checklist.
Every framework, every Cambridge standard, every Indonesian regulation we use — searchable. Click a code like
CSLS 4.1 or ES 7.3 anywhere in the hub to deep-link in.Short, plain meanings for the terms that show up most often in the School Leaders Workspace.
CSLSCambridge School Leader Standards 2023
The 6-domain × 25-competency Cambridge framework that anchors leadership development. Visible as mor chips throughout the hub. Click any
CSLS X.Y chip to read the verbatim source text.ESEduversal Academic Standards
Our 23-section, 393-madde network policy manual. Cyan chips. Example:
ES 7.3 means madde 7.3. Verbatim source in /references.AICFAI Competency Framework
Eduversal's AI literacy framework. Orange chips. Sits alongside CSLS / ES as a 3rd reference family for AI policy + classroom AI use.
schoolIdschool binding
A hidden field on your profile that says which partner school you belong to. Every row this workspace creates carries it; the rule layer uses it to enforce same-school visibility. Set by Eduversal, not by you.
Sub-roleon your profile
Your specific leadership lane:
foundation_representative, school_principal, academic_coordinator, or cambridge_coordinator. You can hold more than one.Stage 0in every Operational Guide handbook
Pre-arrival phase. The two weeks before Day 1 — outgoing handover, data-pack read, calendar slots protected, safeguarding pre-read. Negative-day numbering: Day -14 to Day 0.
Windowin every Operational Guide handbook
A 30-day phase of the 90-day ramp. Foundation Rep / Academic Coord / Cambridge Coord handbooks use generic Window 1 → 2 → 3. The Principal handbook names its three windows Stabilise → Diagnose → Steer — same length, more semantic labels for an operational leader.
Stabilise / Diagnose / SteerPrincipal handbook windows
Stabilise (Days 1-30) — inherit before you act; listening mode, no new policies. Diagnose (Days 31-60) — move from inheriting to interpreting; self-assess against the 8-foci Operating Cadence; surface 3 priority hypotheses. Steer (Days 61-90) — pick the one priority that moves first, anchor the other two in a 6-month plan, deliver the term-opening staff address.
8-foci Operating CadenceP1-P8 — Principal-only
An 8-domain framework that anchors the Principal role: P1 Strategic Vision · P2 Teaching & Learning · P3 Culture & Environment · P4 People & Leadership · P5 Resources & Operations · P6 Community & Stakeholders · P7 Safeguarding & Wellbeing · P8 Quality Assurance & Accountability. Source:
principal-operating-cadence.json. The Diagnose window includes a self-assessment task against all 8.Director-NetworkHQ peer role
The HQ Primary or Secondary Director (CH-side). Not your line manager (you report to the Foundation Rep), but the senior peer who runs the network cohort meetings, provides cross-school benchmarks, and co-signs Principal 90-day readiness reports. Welcomes new Principals during Window 1 and makes an informational in-school visit during Window 2.
Proposalin Proposals
An idea still being discussed — before it becomes a Decision. Moves through four phases: Draft → Open for comment → Decided → Parked. Any leadership-team member can open one and comment; only the Principal sets the phase and promotes it to a binding decision. The deliberation layer that sits before /school-leadership-decisions.
Supersedeaudit-trail discipline
When a Decision changes, you create a new row that supersedes the old one — the old stays visible (marked superseded). Never edit a published decision in place.
Action vs Decisionmeeting-item tags
A meeting item tagged action spawns a kanban card in Activities. A meeting item tagged decision (or red-text) promotes into the binding Decisions register.
NN2Charter Non-Negotiable 2
HQ never reads named induction journal entries. Aggregate signals (pulse, low-pulse alarm) are read; individual entries are private. Applies to Team Induction.
NN5Charter Non-Negotiable 5
Principal Coaching session confidentiality — Foundation Reps are excluded from coaching reads. Coaching stays between the Principal and the HQ Director mentor.
Artifactin /school-artifacts
A living document the decisions + activities point to. Annual Plan, SoW, lesson plans, intervention plans. Per subject. Superseded versions stay archived.
Red-textmeeting-item tag
A way to mark a binding rule born in a meeting. Promotes the item into the Decisions register on submit. Used sparingly — most items stay tagged as discussion or action.
Pulsein Team Induction
A weekly mood check from year-1 staff. The roll-up is visible to the Principal + mentor; individual entries are not. Two consecutive lows triggers an alarm.
⚠ Don't share screenshots of student data in feedback. If a bug involves student records, describe the structure of the issue ("attempt N for student M in class X shows wrong score band") without pasting names or IDs. The feedback collection is admin-readable.