English LGR22 Translation: What It Means

A practical implementation guide for bilingual teams

A bilingual school team aligning curriculum documents using a shared English reference

What Skolverket published

Skolverket’s official English translation of LGR22 is a genuinely useful milestone for international schools and bilingual teams. It provides an authoritative, shared reference for the national curriculum’s intent, structure and key wording. For non-Swedish-speaking staff, that matters: it reduces reliance on informal “corridor translations” and makes induction conversations more precise.

It is also important to be clear about what it is not. An English translation does not replace the Swedish original as the legal and interpretive baseline, and it does not automatically solve the day-to-day problem of working with the wider ecosystem of Swedish support materials. Many schools will still be using Swedish kommentarmaterial, bedömningsstöd, local routines and inspection-facing documentation. The opportunity, then, is not to “switch to English”, but to use the official translation as a stable anchor while you build a bilingual working set around it. If you are already mapping requirements into classroom routines, you may find it helpful to connect this work to practical throughlines in LGR22 Section 2 cross-curricular planning.

Who benefits most

International schools in Sweden benefit most obviously, especially those recruiting teachers who arrive with strong pedagogy but limited Swedish. However, the translation is equally valuable for bilingual teams where Swedish-speaking staff have been acting as ad hoc interpreters. In those contexts, the translation can reduce invisible workload and remove the awkward dynamic where one colleague becomes the “curriculum gatekeeper”.

It also supports leaders who need consistent language across classrooms. When a subject team meets to plan assessment, a shared English reference helps everyone discuss the same sentence, rather than relying on memory. That is particularly helpful for new ECT/NQT colleagues who are learning school routines at speed; pairing the translation with clear operating habits can make induction calmer and safer, as explored in first-term AI micro-routines for new teachers.

Implications for practice

In practice, the biggest gain is fewer “curriculum telephone” errors. These happen when curriculum intent is passed along in paraphrase: first in Swedish, then summarised verbally, then re-summarised into a planning template. The final version can be subtly different from the original. Over time, small shifts become “the way we do it here”.

Using Skolverket’s English LGR22 as a shared reference allows you to standardise three moments where misinterpretation often creeps in: onboarding conversations, planning meetings and assessment moderation. A simple example is a new teacher planning a unit and asking, “Is this knowledge requirement about content coverage or demonstration?” If the team can point to the official translation and then cross-check the Swedish line, you avoid debate based on hunches. This aligns well with the broader aim of turning curriculum intent into usable routines; see LGR22 three years on: from gaps to tool maps for ways schools are operationalising that shift.

Build a bilingual working pack

The official LGR22 translation is a foundation, but most schools need a “curriculum working pack” that sits one layer closer to classroom practice. Think of it as the set of documents teachers actually use when planning, teaching, assessing and communicating with families.

Your pack will vary by school, but it typically includes the Swedish kommentarmaterial (because it clarifies intent and common interpretations), relevant bedömningsstöd (because it shapes assessment decisions) and your local policies (because they define how you enact the curriculum in your context). The key is to keep these as one bilingual pack, not two parallel systems. You want staff to move between Swedish and English confidently, with clear signposts and consistent terminology.

A workable approach is to organise the pack by subject and year band, then include a short “how to use this pack” page at the front. That page should state: the Swedish wording remains the source of truth; the English version supports shared understanding; and any AI-assisted translations are draft supports that require verification.

AI translation workflow

Translation is where schools often lose formatting, references and traceability. A teacher ends up with a wall of text, missing headings, and no way to check what changed. If you use AI translation for supplementary documents, your workflow should prioritise fidelity and auditability.

Start by translating in chunks that match the document structure: headings, paragraphs and tables as separate units. This makes it easier to preserve layout and verify meaning. Keep references intact, including document titles, section numbers and any quoted Swedish phrases. Where a table includes key terms (for example, assessment descriptors), keep the Swedish term in brackets the first time it appears in English.

Tool choice matters here, particularly if you need an audit trail and predictable handling of sensitive material. If you are building school-wide routines, it helps to align translation workflows with your wider compliance and safety approach, such as the guidance in EU AI Act and LGR22 compliance.

Two-way translation example

A practical way to reduce risk is to use two-way translation for high-stakes passages. For example, you translate a paragraph from Swedish to English for your pack. Then you translate your English version back into Swedish and compare it to the original. You are not looking for identical phrasing; you are looking for meaning drift.

A simple verification checklist helps teams do this consistently. Check that key curriculum verbs remain stable (for example, “analyse”, “describe”, “evaluate”). Check that scope words are preserved (“some”, “many”, “different”, “increasingly”). Check that any conditions are still there (“with guidance”, “independently”, “using relevant concepts”). Finally, check that no extra interpretation has been added, such as turning a neutral statement into a recommended method.

This is also a good place to adopt “quote-locking”: for a small number of crucial sentences, keep the Swedish original alongside the English, and require staff to cite those locked quotes in planning documents. That reduces accidental rewording over time.

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!

AI summariser workflow

Once translation is stable, summarisation becomes the time-saver. The goal is not to replace the text, but to create two practical layers: a five-minute read for day-to-day planning, and a one-page brief for induction and quick alignment.

A reliable workflow is to summarise one syllabus section at a time and ask for three direct quotes included verbatim (in both Swedish and the official English, where possible). Those quotes act as anchors. For example, a subject lead might hand new staff a one-page brief that includes: the purpose in two sentences, the main content as a short list of themes, and the three locked quotes that must guide assessment decisions. When a teacher later writes a unit overview, they can trace their choices back to a quote, not just a paraphrase.

If you want to embed this into CPD, you can build a short INSET routine where teams generate the brief, then spend ten minutes checking for drift and missing constraints. The structure pairs well with the kind of practical workshop model described in an INSET day AI workshop with micro-routines.

AI concept explainer workflow

Even with an official translation, certain pedagogical terms carry cultural and professional assumptions. Words such as formativ bedömning can be understood differently by teachers trained in different systems. A concept explainer workflow helps you unpack terms without changing intent.

The key is to request explanations that are definition-first, example-second and non-prescriptive. For instance, you might generate a short explainer that defines formativ bedömning, clarifies what it is not, and gives two classroom examples: one from a primary literacy lesson and one from a secondary science practical. Then you add a “link back” line that points to the relevant sentence in LGR22 (Swedish and English). This keeps the explainer grounded in curriculum wording rather than personal preference.

Quality assurance

Bilingual packs work when they are treated as living documents with clear ownership. A terminology glossary is the simplest stabiliser: one agreed translation for recurring terms, plus notes where multiple translations exist. Add “quote-locking” for the sentences you never want reinterpreted, and use version control so staff can see what changed and why.

Most importantly, assign human sign-off roles. A practical model is to have a Swedish-fluent curriculum owner verify meaning, a subject specialist verify disciplinary accuracy, and a leader verify that the output matches school policy. If you are formalising this across the year, it is sensible to align it with your annual review cycle; the approach in an annual AI acceptable use policy refresh can be adapted to include curriculum-pack governance.

Data protection and tools

International schools often handle sensitive information across multiple systems. Keep your prompts minimum-data by default: paste only what you must translate, remove pupil names, and avoid including safeguarding details, medical information, or internal incident descriptions. Store outputs in your approved document system with clear permissions, and label drafts as “AI-assisted, pending verification”.

A helpful rule is: never paste anything you would not feel comfortable printing and leaving on a staffroom table. If you need to translate a local policy that contains sensitive scenarios, rewrite those scenarios into anonymised placeholders before using any tool. When in doubt, choose tools that support organisational controls and clear retention settings, and document your decisions so staff do not improvise.

A 30-day rollout plan

A 30-day rollout works best when it is small, visible and repeatable. In week one, appoint owners, choose a storage location, and publish the “how to use this pack” page with the official English LGR22 as the anchor. In week two, pilot one subject pack with a translation-and-verification routine and a short glossary. In week three, run a CPD session where teams practise the summariser and concept explainer workflows using real upcoming units. In week four, collect evidence of impact: fewer clarification emails, faster onboarding conversations, and more consistent planning language across teams.

If you want a ready-made structure for the month, you can borrow the cadence from a minimum viable 30-day rollout toolkit and adapt it to curriculum alignment rather than general classroom workflows.

When the official translation becomes your shared reference point, the real win is cultural: staff stop apologising for language gaps and start collaborating around a common text. With a bilingual working pack and careful AI routines, you can reduce misinterpretation without slowing teachers down.

To clearer curriculum conversations and calmer onboarding meetings ahead, The Automated Education Team

Table of Contents

Categories

Strategies

Tags

Lgr22 Curriculum implementation International schools

Latest

Alternative Languages