An Assistant Principal asked for a more consistent approach to curriculum planning, without losing sight of individual learner needs.
Course information was the starting point. The design challenge was to bring relevant sources together and create useful planning outputs that staff could check.
Understand. Build. Refine.
- 01
Version 1 used curriculum and course information to generate a more limited set of planning outputs.
- 02
Version 2 incorporated Gemini and a more closed, grounded knowledge environment using Notebook-style information.
- 03
Google Sheets and Apps Script connected the workflow. AI-assisted scripting supported experimentation; debugging and checks were still essential.
- 04
BRAG-style learner indicators could inform suggested stretch challenges or support activities, with professional review before use.
Curriculum specifications establish the source material.
What changed.
A functioning prototype emerged after approximately a week of experimentation, debugging and iteration. This is prototype evidence; an organisation-wide rollout has not been confirmed.
What I would carry forward.
Grounded sources and clear output structures matter more than a clever prompt alone. Adaptive suggestions still need a knowledgeable person to check relevance and accuracy.
What I’d test next
Test output quality against agreed planning criteria, assess data governance and compare staff effort before considering a wider pilot.
Beyond education
The same discovery-to-prototype approach applies to knowledge workflows, enterprise learning and operational guidance.