What it is
The Curriculum Intelligence Dashboard is a Google Apps Script web application that gives an entire IB World School a single, living view of its curriculum across Elementary, Middle, and High School. Instead of curriculum living in hundreds of disconnected documents, leaders get a navigable dashboard: a course Navigator, a Standards view with a Visible-for-Learning heatmap and gap analysis, a Head-of-Department view, a Gantt-style curriculum Calendar, and an AI tab for deeper queries.
Underneath it sits the AISC Curriculum Documentation Tracker, a structured system tracking 216 courses and 849 units across all three divisions, reaching 81% school-wide completion by June 2026.
Curriculum nobody could see
Like most schools, AISC's curriculum knowledge was real but invisible. It lived in individual planning documents, in teachers' heads, and in formats that varied by division and department. Leaders couldn't answer basic strategic questions, which standards are under-assessed, where are the gaps, how complete is our documentation, without weeks of manual auditing.
When documentation isn't visible, it doesn't get used, it doesn't stay consistent, and it walks out the door every time a teacher leaves. The school needed institutional knowledge to become an asset rather than a liability.
A live analytics layer over curriculum
I designed and built the whole system in Google Apps Script so it lived natively inside the school's existing Google Workspace, no new platform, no new login, no new vendor. The web app reads from the documentation tracker and surfaces it through purpose-built views:
- Navigator. Browse and search every course and unit across ES, MS, and HS from one place.
- Standards view. A Visible-for-Learning heatmap plus gap analysis that shows which standards are covered, over-covered, or missing.
- HoD view. A department-level lens so Heads of Department can see and steward their own area.
- Curriculum Calendar. A Gantt-style timeline of when units are taught across the year.
- AI tab. Natural-language querying over the curriculum data for deeper, ad-hoc analysis.
The system was in real, active use months before any formal launch, a curriculum coach was already flagging live bugs in August 2025, well ahead of the June 2026 rollout to the full leadership team.
From a project to onboarding infrastructure
The dashboard was deployed to 10 Senior Leadership Team members and 40+ Instructional Leadership Team members. But the clearest signal of impact came from how the underlying Shared Drive curriculum structure got used: in May 2026, the school director sent it to 26 incoming 2026–27 teachers as the very first onboarding resource they received, before they had even arrived.
"This is phenomenal work throughout this year that has provided extensive insight into our program."
"Over the past year, we have been working to move all of our curriculum documentation into a shared Google Drive structure to create greater consistency, accessibility, and alignment across the school."
What I'd carry forward
-
Build where people already are.
Living inside Google Workspace, no new platform, removed every adoption barrier. The best tool is one nobody has to be convinced to log into.
-
Ship before you launch.
Having a curriculum coach catch real bugs in August, ten months before the formal rollout, meant the June launch landed on something already battle-tested.
-
Make knowledge visible and it becomes infrastructure.
The moment curriculum became searchable and complete, it stopped being a documentation chore and became the thing a director hands new hires on day zero.