← Blog

Multi-jurisdictional legal AI — Swedish + Norwegian law without shortcuts

Published 4 May 2026 · 8 min read · By GD · LexCodex

"Are we doing this in Swedish or Norwegian?" When a lawyer handles clients in both countries, that isn't a UI choice — it's a legal one. Statutes are named differently, citation systems look different, the court hierarchy isn't the same, and the travaux préparatoires live in different places.

A global LLM with language toggling can translate the words but not the law. For a legal AI platform to be genuinely usable for both Swedish and Norwegian law, it has to understand which jurisdiction the question belongs to and adapt everything — primary sources, citation format, court hierarchy, terminology — accordingly.

This article walks through what LexCodex actually does differently compared to a "PDF chat with AI". Those details are what separate a useful legal AI from a dangerous one.

Why "language toggling" isn't enough

Suppose you ask a general-purpose LLM (ChatGPT, Claude, Gemini) in Norwegian about a Swedish contract clause. You get an answer — in Norwegian — but it will reference Norwegian legislation, because the model associates "Norwegian" with "Norwegian law". Wrong jurisdiction.

Or: you ask in Swedish about a Norwegian employment law question. The model answers with Swedish LAS reasoning instead of Norwegian arbeidsmiljølov. Again — language is not the same as jurisdiction.

To handle this correctly, the system needs:

  1. Explicit jurisdiction selection — not just language
  2. Per-jurisdiction primary sources — so citations actually go to the right country
  3. Per-jurisdiction terminology — "skadestånd" vs "skadeerstatning", "preskription" vs "foreldelse"
  4. Per-jurisdiction procedural rules — Swedish litigation differs from Norwegian on important points

The citation systems are not compatible

This is the most underrated difference. Swedish and Norwegian lawyers have grown up with their respective systems, so it feels obvious from the inside — but for an AI tasked with producing correct citations, the differences are critical.

AspectSwedenNorway
Statutes Avtalslagen (1915:218), AvtL § 36 Avtaleloven (1918), avtl. § 36
Supreme Court case law NJA 2018 p. 423 HR-2018-1234-A or Rt. 2018 p. 423
Travaux préparatoires Prop. 1975/76:81, SOU 1974:83 Prop. 145 L (2017–2018), NOU 2018:7
Data Protection Authority IMY (Integritetsskyddsmyndigheten) Datatilsynet
Competition Authority Konkurrensverket (KKV) Konkurransetilsynet
Financial Supervision Finansinspektionen (FI) Finanstilsynet
Ombudsmen JO, DO, etc. Sivilombudet
Primary source database lagen.nu, Sveriges Domstolar Lovdata, Stortinget

For an AI to produce a citation like "Rt. 2018 p. 423" it must both know the format and have access to the actual URL on Lovdata. Neither of these happens by itself — it's the result of per-jurisdiction mapping fed into the system.

LexCodex's per-jurisdiction architecture

Concretely, this is how LexCodex handles Swedish vs Norwegian law:

Swedish jurisdiction (/)

Norwegian jurisdiction (/no/)

The system prompt that controls the AI is jurisdiction-aware. When you ask a question on /no/, the prompt is constructed so the model knows the question concerns Norwegian law and cites accordingly. It's not the model's own "intuition" steering — it's an explicit framework.

EU law as common ground

Sweden is an EU member, Norway is an EEA member via EFTA. That means GDPR, the EU AI Act, MiFID II, DORA, the AML directives etc. apply equivalently in both countries — but the implementations look different.

For legal AI used in both countries, this means the system has to understand both implementations — not just the EU regulation's text, but how it interacts with Swedish and Norwegian implementing law.

Practical consequences for lawyers

If you handle Swedish + Norwegian clients (or even a single cross-border deal), the differences are concrete:

  1. Choice of law between SE and NO buyers/sellers: Which law applies (CISG? Swedish avtaleloven? Norwegian avtaleloven?). LexCodex distinguishes between the three.
  2. Confidentiality agreements with employees who relocate: Swedish LAS vs Norwegian arbeidsmiljølov have different rules on non-compete clauses.
  3. GDPR notification of a data incident: IMY (SE) or Datatilsynet (NO) — depending on where data was, where the affected individual is.
  4. Competition law notification: KKV (SE) or Konkurransetilsynet (NO), or ESA if EEA aspects are triggered.

That an AI analysing such questions must know the difference — not just linguistically, but at the legal-system level — should be obvious. But it's surprisingly common to find "legal AI" services that just run a multilingual LLM without a jurisdiction-aware framework.

Roadmap: Denmark, Finland, Iceland

Norway is the first country beyond Sweden with a full LexCodex implementation (since May 2026). The next Nordic countries follow the same template:

Timeline: full Nordic launch before summer 2026. Each country gets a dedicated subdirectory (/dk/, /fi/, /is/) with the same per-jurisdiction architecture as Sweden and Norway.

Summary

Multi-jurisdictional legal AI is not a language question — it's an architecture question. It requires per-jurisdiction primary sources, citation formats, terminology and supervisory structure — not just translated output. LexCodex has this for Swedish + Norwegian law today, and is expanding to Denmark, Finland and Iceland during 2026.

For lawyers handling Nordic clients, that's the difference between an AI that genuinely helps and one that produces plausible-looking but wrong answers.

Want to test both jurisdictions? Create a free account and switch between Swedish (/) and Norwegian (/no/) in the menu. Same user account, two jurisdictions.

Read more

How LexCodex avoids hallucinations · Zero Data Retention for lawyers

Our Nordic focus → Back to blog

⚠ AI-assisted analysis — verify against the primary source before deciding. For specific choice-of-law questions in international contracts, consult a qualified lawyer in each jurisdiction.