If you’re newly qualified, new to Sweden, or moving between school systems, LGR22 can feel deceptively familiar. The headings look straightforward, yet the day-to-day translation into lessons, tasks, and fair grading takes practice. This guide is designed as a week-one companion: you’ll build a small, complete workflow that links purpose (syfte), content (centralt innehåll by stage), and evidence (betygskriterier E/C/A) without drowning in documents. If you want a wider “first term” operating rhythm, you may also find the routines in this first-term AI manual useful alongside the curriculum focus here.
In week 1, “good” rarely means perfect. It means you can explain what you’re teaching and why, you can point to the right stage-specific content, and you can describe what evidence you’ll accept for E, C, and A. It also means you’ve set boundaries for AI use: you are using it to clarify, map, and check — not to outsource professional judgement or generate assessment that compromises integrity.
LGR22 planning becomes manageable when you treat it as three linked layers.
Syfte is the “why”: the long-term aims of the subject. It helps you choose what to emphasise and what to leave out. When you’re unsure whether an activity is worth lesson time, syfte is the anchor.
Centralt innehåll is the “what”: the core content pupils should encounter, but crucially it is organised by stages. A common early-career mistake is to treat it as a cumulative checklist (“we must cover everything from earlier stages again”). In practice, you plan for the stage you teach, while using earlier content diagnostically when gaps appear. AI can help you spot when you’ve accidentally built a unit that reteaches a previous stage as if it were required content.
Betygskriterier E/C/A is the “evidence standard”: what quality looks like at different grade levels. The criteria are not a points system. They describe differences in quality, independence, accuracy, and reasoning. Your job is to design tasks that make those qualities visible, then to mark consistently.
If you want a broader map of where teachers tend to lose time when moving from LGR22 text to classroom practice, this “gap to tool” overview gives a helpful framing.
The term-start workflow below is intentionally small. You can run it in an afternoon, then iterate as you teach.
You move through four steps: Concept Explainer → Unit Planner (6 lessons) → Lesson Planner → Answer Key (calibration). Each step uses AI as a translation and checking tool, but you always supply the minimum curriculum inputs: the stage, the relevant centralt innehåll bullets, a short excerpt of syfte, and the betygskriterier you’ll assess against.
The aim is coherence. By the end, you should be able to answer three questions without hesitation: “Why this?”, “Why now (this stage)?”, and “What evidence will count?”
Start with one concept you know is coming early in the term. The goal is a pupil-facing explanation plus teacher-facing checks: key vocabulary, language supports, and misconceptions.
Example: Ekvationer (Åk 8). Ask AI to produce a Swedish explanation at an accessible reading level, then request a second version with language scaffolds for newly arrived pupils. The useful part is not the polished paragraph; it’s the structured clarity: definitions, examples, non-examples, and the “why we do this” link back to syfte.
You can also ask for misconception checks that you can turn into hinge questions. For equations, typical misconceptions include doing “the same thing to both sides” inconsistently, or treating the equals sign as an instruction rather than a relationship. A practical classroom move is to show two worked solutions — one correct, one with a subtle error — and ask pupils to identify where the balance breaks.
When you use AI here, keep it honest by requiring it to state uncertainty. For instance, you can ask it to label which misconceptions are “very common” versus “possible”, and to suggest what evidence would confirm each misconception in pupil work.
Now build a six-lesson mini-unit that maps cleanly to the centralt innehåll for the stage you teach and is justified through syfte. This is where the “not cumulative” check matters most.
Example: Bråk och decimaltal (Åk 4), 6 lessons. Provide AI with the relevant centralt innehåll bullets for the current stage and ask it to propose a sequence where each lesson has a clear learning intention, a short retrieval starter, guided practice, independent practice, and an exit check. Then ask it to produce a mapping table: each lesson → which centralt innehåll bullet(s) it addresses → which part of syfte it supports.
Your built-in safeguard is a second prompt: “Identify any lesson objectives that belong to an earlier stage’s centralt innehåll and mark them as diagnostic or support, not required coverage.” This prevents the classic overstuffed unit where you reteach everything “just in case”, leaving too little time for depth.
If you’re also trying to make your planning inspection-ready across subjects, the cross-curricular thinking in this LGR22 Section 2 guide can help you connect routines like language development and digital competence without forcing artificial links.
Choose lesson 1 and plan it tightly. A good AI-assisted lesson plan is not longer; it is clearer about structure, questioning, and adaptations.
Example: Introduktion till bråk (Åk 4, 50 minuter). Ask AI for a plan with timings, teacher talk cues, and three tiers of questioning: recall, reasoning, and extension. Then request adaptations for pupils who struggle with language, working memory, or number sense — without changing the learning goal. In practice, this might mean using visual fraction models, sentence stems (“Jag ser att… därför att…”), and worked examples with fading support.
The most valuable addition is a short “what I’ll listen for” section. For fractions, you might listen for whether pupils can describe a fraction as “equal parts of a whole” and whether they confuse numerator and denominator. You can then align your exit ticket to those exact ideas, making your later marking far faster.
Before pupils ever do the task, build the answer key and marking guide. This is where AI can reduce workload without reducing standards.
Start by asking AI to generate a model answer and a list of common wrong answers for each question. Then ask it to draft an E/C/A-aligned marking guide that describes quality in observable terms: accuracy, clarity of method, use of mathematical language, and reasoning. Finally, add moderation notes: “If a pupil does X, check Y before deciding the grade,” which helps you stay consistent when marking late at night.
If you’re unsure where the integrity line sits, it’s worth aligning with your school’s expectations and refreshing your own boundaries. This acceptable use policy refresh checklist is a practical reference for keeping AI support transparent and defensible.
A Year 6 rubric becomes manageable when you convert betygskriterier into “things you can actually see” in pupil work. Choose one assessment task, such as a short problem-solving set with an explanation question. Then ask AI to rewrite the E/C/A descriptors into evidence statements that fit the task.
For example, for an explanation item, you might define:
At E, the pupil shows a workable method and a brief explanation that is mostly correct, even if vocabulary is limited. You can see the main idea and follow their steps.
At C, the pupil’s method is correct and their explanation is clearer, using appropriate terms and linking steps logically. Errors are rare and they can justify choices.
At A, the pupil’s solution is not only correct but well-reasoned and efficient, with a precise explanation that anticipates misunderstandings (for instance, stating why another approach would fail). They generalise or connect ideas appropriately.
The calibration tool is a simple prompt you run after drafting the rubric: “What would change the grade from E to C, and from C to A, for this exact task?” This forces the rubric to be discriminating rather than aspirational. It also gives you language for feedback conferences: “Right now you’re at E because your method works, but your reasoning is too brief. To reach C, I need you to explain why you chose that step.”
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.
Before you teach, run a short quality check that keeps you faithful to LGR22 and fair to pupils. Check curriculum fidelity by confirming every lesson objective links to syfte and stage-specific centralt innehåll. Check stage alignment by labelling any earlier-stage content as diagnostic support rather than required coverage. Check language clarity by ensuring key terms are defined and sentence stems are available. Check accessibility by confirming that adaptations change the route, not the goal. Finally, check integrity boundaries by ensuring pupils are not assessed on AI-generated work and that your materials are transparent and explainable.
If your school is developing its compliance approach, particularly around data and procurement, this EU AI Act explainer for Swedish schools offers a sensible starting point for leaders and classroom teachers alike.
To keep inputs minimal, use a “minimum-data” approach: paste only the relevant syllabus excerpts and your local context (stage, time, class needs). You might use prompts such as: “Turn this syfte excerpt into three unit goals pupils can understand,” or “Map these centralt innehåll bullets to six lessons and flag anything that looks like earlier-stage content.” For assessment: “Draft an E/C/A marking guide for this task, then list borderline cases and what evidence would decide.”
For your first fortnight, a one-page onboarding checklist helps you stay calm: confirm your stage’s centralt innehåll, select one assessable focus area, build one six-lesson unit, prepare one calibrated marking guide, and schedule a short moderation chat with a colleague using two anonymised samples. If you want a ready-to-run staff approach to embed these routines safely, this INSET micro-routines plan can help you bring others along without turning it into a tech project.
May your first LGR22 term feel clearer with every lesson. The Automated Education Team
Black Friday can feel like a rare chance to “save” on AI subscriptions, but …
Three years after ChatGPT’s release, schools have enough experience to …
December in schools brings a familiar spike: cover changes, heightened …
Microsoft Ignite can feel like a firehose of AI updates, but schools need a …
Report writing in 2025 is less about “which chatbot is best” and more about …
Three years into LGR22, many schools report real gains in clarity and …
Anti-Bullying Week works best when it moves beyond awareness and into …
Remembrance teaching asks for careful language, accurate sources, and …
Mock season often fails for predictable reasons: revision plans are …
Uue õppeperioodi alustamine LGR22-ga võib tunduda nagu uue professionaalse keele õppimine, eriti …
Att starta en ny termin med LGR22 kan kännas som att lära sig ett nytt yrkesspråk, särskilt för …
Uuden lukukauden aloittaminen LGR22:n kanssa voi tuntua uuden ammatillisen kielen opettelulta, …