The Commission published an assessment calculator alongside the framework, and it is more honest than most vendor claim charts. It rewards specific evidence, penalises weak objectives without mercy, and does not let a single strong area rescue a workload with a serious gap.
This post walks through one worked example, small enough to be readable, realistic enough to be useful. The whitepaper accompanying this series contains three larger examples across UC, CC and networking.
The worked example
A mid-sized European financial services firm, headquartered in Frankfurt, running a hybrid contact centre. The vendor is US-headquartered, the tenant is hosted in an EU region, transcription and summarisation are AI features running on the vendor default configuration, the recording archive uses vendor-managed keys, and support is provided from an EU delivery centre with overnight escalation to a US team.
On paper, the buyer has been telling the board this is a European deployment. The calculator disagrees.
Scoring the eight SOV objectives
- SOV-1, strategic. The vendor is US-owned and US-financed. Ultimate decision-making authority sits outside the EU. Score: low.
- SOV-2, legal and jurisdictional. The contract is with an EU subsidiary, but the parent is exposed to the US CLOUD Act. Score: low.
- SOV-3, data and AI. Keys are vendor-managed, AI inference runs outside the EU on the default configuration, and there is no documented per-call AI audit log. Score: very low.
- SOV-4, operational. Overnight escalation sits in the US. If the vendor withdrew EU support, the estate could not be operated by the customer alone. Score: low to medium.
- SOV-5, supply chain. Handsets, gateways and session border controllers ship with firmware signed outside the EU. Score: low.
- SOV-6, technology. The media plane uses SIP and WebRTC. Some APIs are documented and open, some are proprietary. Score: medium.
- SOV-7, security and compliance. SOC operates 24 by 7 with a US handover. Score: low to medium.
- SOV-8, environmental. The EU region uses renewable energy sourcing and the vendor reports on scope 2 emissions. Score: medium to high.
The Global Sovereignty Score
The calculator combines the eight scores. SOV-3 alone drags the overall score into SEAL-1 territory. The good SOV-8 score does not lift it. The medium SOV-6 score does not lift it. The workload is a SEAL-1 workload the day the calculator is run, regardless of what the marketing said the week before.
What the calculator rewards, in plain terms
- Customer-held keys. Not vendor-held keys with an EU escrow. The calculator distinguishes.
- EU-only inference paths for AI features, with the route documented.
- Per-interaction audit logs, including AI interactions, with verifiable deletion.
- EU-employed support with a written EU-only escalation path.
- Firmware update pipelines under EU control, with a documented signing chain.
- Contract language that names the SOV objectives and reserves a right to re-score.
The traps
Three scoring traps show up in almost every real assessment.
- Confusing data residency with data sovereignty.
The calculator treats them as different. Residency answers where the file sits. Sovereignty answers who could compel access to it. A file in Frankfurt owned by a US parent is resident, not sovereign.
- Treating a European legal entity as a shield against parent-company jurisdiction.
The calculator does not accept this. A European subsidiary of a US company still exposes its European contracts to the parent-company jurisdiction under US law.
- Counting an ISO 27001 certificate as evidence for SOV-7.
The calculator asks about the geography of the SOC, the jurisdiction of the incident response process, and the exposure of operational telemetry. An ISO 27001 report answers none of those questions on its own.
The evidence pack you should require
The framework is evidence-driven. A serious pre-tender pack asks for:
- Ownership records for the contracting entity and every parent up to the ultimate beneficial owner.
- A written statement of exposure to non-EU laws with cross-border reach, with legal opinion.
- Data flow diagrams for every category of content, including AI processing paths.
- A key management architecture document, naming the key custodian for each data category.
- A deletion attestation process, with a sample deletion report.
- A staff geography statement for each support tier, refreshed annually.
- A signed firmware and software update chain, including the countries of origin and signing.
- An open standards inventory, listing every proprietary API in the delivery path.
What this means for buyers
The calculator is a governance tool, not a compliance tick-box. Score your own estate against it before you write your next tender. The results will change the questions you ask, the clauses you insist on, and the vendors you invite.
Post six covers the clauses to add to your next master services agreement, so the calculator results turn into contract obligations rather than slides.