Preparing for the 10-Year Grundskola

A now-to-2028 checklist for leaders

A school leadership team reviewing curriculum drafts and timetables with AI support

What is changing

The headline is simple: the system is moving towards a 10-year grundskola, and that will reshape how schools describe stages, plan progression, and package curriculum expectations. The quieter truth is just as important: most of what makes learning work day-to-day will not change overnight. Your classroom routines, your existing professional judgement, and much of your current Lgr22-informed planning can remain stable for a while yet.

A useful way to think about the period from now to 2028 is “translation rather than reinvention”. You are not trying to pre-empt Skolverket by rewriting everything early. You are building the organisational capacity to interpret new text quickly when it lands, and to keep teaching coherent in the meantime. If you are already using small AI routines for curriculum reading and evidence-ready documentation, you can repurpose those habits here; the approach in Lgr22 Section 2 cross-curricular throughlines is a good example of using micro-tools to make decisions without creating busywork.

What is not changing

It helps leaders to name what will stay steady, because it reduces unhelpful churn. Your current schemes of work are still valuable. Your assessment evidence still matters. Your safeguarding and data protection obligations are unchanged, and, if anything, they become more visible when staff start experimenting with “helpful” tools during a period of uncertainty. If you want a quick way to sanity-check AI use while the curriculum is in flux, keep an eye on the principles in the EU AI Act and Lgr22 compliance explainer.

In practical terms, “not changing” means you can keep your current curriculum spine in place and focus on organisational readiness: stage boundaries, timetable models, and how you document progression so it can be relabelled later.

Structural shifts

Most schools will feel the impact first in structure, not content. Start age is the obvious one, but the bigger operational question is what happens to stage divisions and how curriculum requirements are packaged. When stages shift, everything that depends on them shifts too: reporting cycles, parent communication, staffing patterns, and how you describe “expected progression” across years.

Curriculum packaging matters because it changes how teachers find what they need. If the new model becomes more “sammanhållen”, you may see fewer disconnected documents and more integrated expectations. That can be positive, but it also means your internal documents need to be easier to map to whatever Skolverket publishes. This is where leaders can make 2025–27 calmer by standardising how teams label learning intentions, knowledge requirements, and evidence—without rewriting the learning itself.

Now vs freeze

The safest stance for 2025–27 is: freeze what is expensive to rewrite, prototype what is expensive to change later, and document what will be hard to remember under pressure.

Freeze your schemes of work as “teaching sequences”, and resist the urge to reformat them to match rumours of future headings. Instead, prototype the organisational wrappers: stage descriptors, timetable options, and progression maps that can be retagged quickly. Document your current decisions and rationales, because the hardest part of a curriculum transition is not writing new plans; it is explaining why you changed something and ensuring consistency across teams.

If you want a simple mental model, treat your curriculum materials like code. You do not refactor everything before the specification is final. You put tests around it, you clarify interfaces, and you keep a change log. The same logic underpins the time-saving workflows in Lgr22 three years on: gap-to-tool map—small routines that reduce rework later.

Tool demo 1 — Summariser

A summariser is not for “doing the thinking for you”. It is for turning long draft text into a brief that a leadership team can actually use in a meeting. The trick is to constrain the output so it becomes organisationally actionable: what decisions might we need to make, what data do we need, and what can we safely ignore for now?

Below is a template prompt you can reuse with your chosen tool. It produces a one-page brief with a “decision register” and a “watch list”, which stops staff leaping into premature rewriting.

Use exactly three anchor quotes from the draft, copied verbatim, to keep the brief grounded:

“Införandet av en tioårig grundskola”

“sammanhållen läroplan”

“tidigare skolstart”

Then ask the tool to (a) summarise in plain Swedish for staff and families, (b) list likely organisational decisions (stages, timetables, reporting), and (c) separate “confirmed”, “proposed”, and “unknown”. Your leadership team can then add a human judgement layer: which decisions have long lead times in your context, and which can wait.

Tool demo 2 — Concept explainer

“Sammanhållen läroplan” will sound reassuring to some staff and threatening to others. A concept explainer tool is useful here because it can generate multiple interpretations quickly, which you then choose between. Ask it to explain the concept in three ways: one for teachers, one for middle leaders, and one for families. Then add a fourth output: “what this does not mean”, because that is where anxiety often lives.

In planning and documentation, a more coherent curriculum usually pushes schools towards fewer parallel documents and clearer linking. For example, rather than separate files for “aims”, “content”, and “assessment”, you might move towards a single unit overview that links these elements in one place. The aim is not a new template for its own sake; it is a format that can survive relabelling. If you are revisiting templates anyway, build in privacy-by-default habits from resources like the minimum viable back-to-school AI toolkit so experimentation does not create data risks.

Tool demo 3 — Unit planner

A unit planner can help you practise “transferable planning habits”: writing units that remain valid even when headings change. The key is to plan around durable learning, not fragile labels. Ask the tool for a 10-lesson unit that is explicit about knowledge building, vocabulary, and formative checks, but light on curriculum-specific wording. A science unit on forces, a Swedish unit on argumentation, or a maths unit on proportional reasoning can all be written in a way that survives a rewrite.

The most transferable habit is to separate the learning journey from the compliance mapping. Keep the teaching sequence stable, and keep the mapping in a thin layer you can regenerate later. If you want an example of a unit that is already designed to be “mapped” rather than constantly rewritten, look at the structure used in the Gy25–Lgr22 bridge guide unit and notice how the learning steps can be retagged without changing the lessons.

Ready to Revolutionise Your Teaching Experience?

Discover the power of Automated Education by joining out community of educators who are reclaiming their time whilst enriching their classrooms. With our intuitive platform, you can automate administrative tasks, personalise student learning, and engage with your class like never before.

Don’t let administrative tasks overshadow your passion for teaching. Sign up today and transform your educational environment with Automated Education.

🎓 Register for FREE!

Organisation-first implications

Timetabling will surface early because stage changes ripple into contact time, grouping models, and specialist allocation. If you wait until the final text lands, you may find you are modelling timetables under time pressure, with staffing already committed. A sensible 2025–26 move is to build two or three timetable prototypes that differ in only one variable each, such as lesson length or stage grouping, so you can see what breaks.

Staffing implications are often more about expertise distribution than headcount. If earlier years shift, you may need to rethink how subject specialists support generalist colleagues, and how you protect planning time for transition cohorts. Progression mapping becomes your stabiliser here: a clear, school-owned map of what “getting better” looks like across years, written in teacher language, will help you absorb new curriculum packaging without losing coherence.

Communication with families should start earlier than you think, but it should be calm and factual. A short, termly update that explains what is known, what is being explored, and what will not change for pupils reduces rumour-driven anxiety. If you want to make those updates consistent and safe when AI is involved, it is worth aligning with an annual AI acceptable use policy refresh checklist so staff know what they can and cannot paste into tools.

Keeping the platform current

Curriculum transitions fail when schools treat updates as one giant event. A better approach is an update cadence: small, predictable check-ins where you re-read the latest drafts, update your decision register, and regenerate only the thin mapping layer. That means templates matter. If your unit overviews, progression maps, and reporting language are modular, you can update the “labels” without disturbing the teaching sequence.

When the final text lands, the items that should be regenerated are the ones designed for it: curriculum mapping tables, stage descriptors, and any family-facing summaries. The items you should not automatically regenerate are teacher-created lesson sequences and resources, unless the learning itself is no longer aligned. This distinction is what keeps workload humane.

One-page action plan

In 2025–26, schedule a light but regular rhythm: one half-termly “draft-to-decisions” meeting where you produce a one-page brief, update a decision register, and log unknowns. Use this year to prototype two timetable models and to standardise a unit overview template that separates teaching sequence from mapping. Ask each subject team for one progression map that describes learning in teacher language, not policy language.

In 2026–27, widen the prototypes. Run a small internal pilot of your documentation approach in one phase or year group, focusing on how quickly you can retag units when headings change. Build a communication pack for families that can be updated in minutes, not hours. Stress-test your staffing and cover assumptions using a constraints-first approach, borrowing ideas from the AI copilot playbook for timetabling.

In 2027–28, shift from prototyping to implementation readiness. Lock in your preferred timetable model, confirm training needs, and prepare a “mapping sprint” plan for when the final curriculum is published. Ensure every team has a short, documented rationale for its progression map and assessment approach, so changes are explainable and consistent. If you do only one thing, make it this: keep teaching sequences stable, and make mapping layers easy to regenerate.

May your transition planning stay calm, coherent, and kind to staff workload. The Automated Education Team

Table of Contents

Categories

Administration

Tags

Administration Grundskola Curriculum change

Latest

Alternative Languages