Use-case scenarios: Open Badges and EDC in practice

← Higher education

Decision rules are easier to apply once you see them at work. The seven scenarios on this page follow a credential through a typical university process twice, once as an Open Badge and once as a European Digital Credential (EDC), and note where each holds up and where it breaks. They complement the Decision framework: find the scenario closest to your own case, then use the framework to confirm the choice.

The scenarios are adapted from the use cases in the Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education. Two adjustments apply throughout. Where the original speaks of Open Badges in general, this page separates mostly hosted 2.x badges from signed 3.0 credentials, because 3.0 closes several verification gaps while leaving the gaps in semantics, accredited issuers and legal standing (see Open Badges). And statements about wallets follow Implementing Regulation (EU) 2026/1731.

Where a scenario says “wallet”, read: the Europass wallet, an EBSI-conformant wallet, or a national EUDI Wallet only where it supports the W3C VCDM format. A qualified attestation delivered to an EUDI Wallet travels as SD-JWT VC or mdoc today; EUDI Wallet sets out the current position.

Badges come out of these comparisons as the weaker tool for recognition, but not as a useless one. They remain valuable for visibility and engagement, and the Combination model shows how to use both.

The seven scenarios at a glance

ScenarioQuestionKey finding
A.1 Formal microcredential issuanceCan a short-course credential be formally recognised by other EU institutions?The 2022 Council Recommendation is non-binding and format-neutral. EDC carries its standard elements as structured ELM fields; a badge can hold most of them only as free text or extensions that receivers cannot process consistently.
A.2 Credit recognition and ECTS transferCan the receiving institution automate the credit evaluation?Structured ECTS, EQF and outcome fields in EDC allow pre-recognition rules; badges leave every case to manual review.
A.3 Erasmus mobility and cross-border recognitionDoes the credential plug into EU mobility infrastructure?The Badges guide sees EDC as the natural format for Europass, Erasmus Without Paper and EMREX; Open Badges are not part of that infrastructure.
A.4 Admissions to a postgraduate programmeCan the credential support an admissions decision that stands up to challenge?Badges offer claims; an EDC from a registered issuer, bound to its holder (in the wallet-oriented lineage), offers evidence.
A.5 Diploma and degree issuanceWill the degree stay independently verifiable for decades?EDC from an accredited issuer, with a status mechanism and a re-issuance plan; a hosted badge lasts only as long as its platform.
A.6 Employer verificationCan an employer’s systems verify a qualification without contacting the university?EDC delivers machine-readable, tamper-evident data; badges help visibility, not verification.
A.7 Alliance-internal recognition and skills portfolioCan an alliance build one coherent learning record across its partners?Only shared EDC profiles produce one record; badges derived from them keep the skills visible.
Source: Badges guide v1.1 (EUNIS SIG, July 2026), EUPLv2, adapted.

A.1 Formal microcredential issuance

A university certifies a structured short course of 15 to 60 hours. The learner wants to use it for recognition, credit transfer or a job application, so it must say more than “completed”.

Open BadgesEuropean Digital Credentials
1. Instructor writes the criteria in free text1. Course described in the European Learning Model (ELM)
2. Badge sent to a backpack or profile2. Outcomes, workload, EQF level, assessment, quality assurance and awarding body recorded as fields
3. Learner shares a link or image3. Sealed credential delivered to the learner’s wallet and presented from it
4. Recipient reads the metadata by hand4. Recipient checks the seal and reads the fields directly
Source: Badges guide v1.1 (EUNIS SIG, July 2026), EUPLv2, adapted.

Where badges fall short. Open Badges 3.0 offers generic fields such as fieldOfStudy and alignment, but no agreed EQF level, assessment or quality assurance reference that receivers can rely on, so similar badges from two universities cannot be compared and recognition stays informal.

What EDC adds. Comparable, machine-readable records that carry the elements of the 2022 Council Recommendation on micro-credentials as agreed fields.

Key takeaways

  • A badge records that something happened; an EDC states what was learned, how it was assessed and who assures its quality.
  • Without the Recommendation’s mandatory elements, a microcredential does not meet the EU standard and is hard for others to recognise.
  • EDC lets the receiver pre-screen automatically; badges need academic judgement case by case.

Value for alliances: One shared EDC microcredential profile makes partners’ microcredentials comparable by design, so mutual recognition can become largely automatic.

A.2 Credit recognition and ECTS transfer

A student passes a module in Spain and asks a German university to recognise the ECTS credits. The receiving registrar must judge equivalence.

Open BadgesEuropean Digital Credentials
1. Registry reads free-text criteria and evidence links1. Registry checks the seal and the issuer
2. Registry asks the sending university what the module covered2. ECTS, EQF level, outcomes, assessment and QA body read as fields
3. Committee reviews the case by hand3. Pre-recognition rules applied to those fields
4. Decision weeks or months later4. Decision based on structured evidence that can be audited
Source: Badges guide v1.1 (EUNIS SIG, July 2026), EUPLv2, adapted.

Where badges fall short. Open Badges 3.0 has generic fields such as creditsAvailable, fieldOfStudy and alignment, but no agreed credit unit, EQF level or quality assurance reference, so receivers cannot rely on them. Every request is a one-off, and both offices pay for it.

What EDC adds. Standard fields for workload, level and outcomes, so part of the evaluation can be automated and documented.

Key takeaways

  • Badges ask the receiver to trust the sender’s reputation; EDC offers a verifiable signature from a recognised issuer.
  • ECTS credits are a defined field in EDC. A badge can state a number of credits, but not in an agreed unit that systems can process.
  • Badge-based recognition always needs a person in the loop, which caps scale.

Value for alliances: Partners with a shared EDC profile can fix recognition rules in advance, turning mobility into a procedure rather than a negotiation.

A.3 Erasmus mobility and cross-border recognition

A student applies for an Erasmus+ placement. Before departure the host must assess prior learning and agree the Learning Agreement.

Open BadgesEuropean Digital Credentials
1. Host reviews each badge separately1. Host checks the EDC transcript against the issuer registry
2. No common model, no trusted register of badge issuers2. ELM data can prepare the Learning Agreement where institutions’ Erasmus Without Paper systems accept it
3. Coordinators negotiate the Learning Agreement by hand3. Recognition by the home (sending) institution agreed in the Learning Agreement before departure
4. Weeks of exchanges; outcomes vary by institution pair4. Same infrastructure reused for recognition on return
Source: Badges guide v1.1 (EUNIS SIG, July 2026), EUPLv2, adapted.

Where badges fall short. No shared data model, uneven quality, no link to Erasmus Without Paper. The workload grows with every partner.

What EDC adds. A fit with Europass, Erasmus Without Paper, EMREX and the European Student Card Initiative, and a Learning Agreement prepared from data. In practice this depends on each institution’s Erasmus Without Paper connection, and EMREX still exchanges results in its own ELMO format, with alignment to ELM in progress.

Key takeaways

  • The bottleneck is usually the Learning Agreement, not travel or housing; EDC can make it a data exchange.
  • Hundreds of mobilities a year cannot be handled by reviewing badges by hand.

Value for alliances: A common EDC framework makes mobility between partners their easiest case instead of their hardest.

A.4 Admissions to a postgraduate programme

A graduate applies for a master’s programme in another EU country. Admissions must assess the degree, language of instruction and credit load, and the decision may be appealed.

Open BadgesEuropean Digital Credentials
1. Badges submitted alongside PDF transcripts1. EDC presented from the wallet; signature and issuer registration checked
2. Each badge weighed on issuer reputation and criteria text2. Level, EQF, ECTS, language and QA body read as fields
3. At most a recipient identifier (an email address or student number); nothing ties it to legal identity3. Credential bound to its holder (in the wallet-oriented lineage); identity confirmed with person identification data (PID) from an EUDI Wallet
4. Decision rests on the PDFs4. Automatic eligibility check; committee reviews a verified shortlist
Source: Badges guide v1.1 (EUNIS SIG, July 2026), EUPLv2, adapted.

Where badges fall short. Trust depends on the reader’s view of the issuer, with no identity guarantee. In regulated admissions a badge cannot replace official documents.

What EDC adds. A registered issuer, holder binding and comparable data: a faster, consistent decision that can be defended. PID is issued as SD-JWT VC or mdoc, so in practice the EDC and a separate identity credential are checked together.

Key takeaways

  • Admissions rarely lacks information; it lacks information it can trust. Badges add information, an identity-bound EDC adds evidence.
  • A 3.0 badge can prove control of an identifier, not the legal identity behind it.
  • For regulated programmes, an EDC from an accredited issuer can be the evidentiary basis where national rules accept it; a badge cannot.

Value for alliances: Common admission criteria tied to EDC fields spare partners from evaluating the same applicant several times.

A.5 Diploma and degree issuance

A university issues a bachelor’s or master’s degree, which the graduate will show to employers, professional bodies and recognition agencies for a whole career.

Open BadgesEuropean Digital Credentials
1. 2.x: usually a hosted assertion, so a platform outage breaks verification; 3.0: signed credential1. Sealed EDC held by the graduate; issuer listed in a trust registry
2. No standard degree data or legal identity2. Classification, EQF level, ECTS, title and QA body as fields
3. 2.x: online revocation list; 3.0: Bitstring Status List possible3. Bitstring Status List in the DC4EU/EBSI lineage; more limited mechanisms in Europass/EDCI
4. Verifier relies on the badge platform4. Verifier checks signature, registration and status without the university
Source: Badges guide v1.1 (EUNIS SIG, July 2026), EUPLv2, adapted.

Where badges fall short. Even a signed 3.0 badge lacks degree semantics, identity binding and a register of accredited issuers, so a badge from an unrecognised provider looks like one from a reputable university.

What EDC adds. Issuer-independent verification, revocation and structured degree data. Durability still needs planning: keys, status lists and registries must stay resolvable, and re-issuance may follow as algorithms age (see Credential lifecycle).

Key takeaways

  • A platform change, merger or closure can leave a hosted badge unverifiable; an EDC needs resolvable keys and status, not an online issuer.
  • Revocation is a legal and reputational duty for degrees: choose the mechanism before issuing.
  • A degree is worth the authority behind it, and EDC anchors that authority in a recognised trust framework.

Value for alliances: Where national rules allow joint degrees, partners can issue them as EDCs with each issuer registered, carrying the alliance’s authority.

A.6 Employer verification

A graduate applies for a job. HR must confirm the qualification quickly, often without academic expertise and across countries.

Open BadgesEuropean Digital Credentials
1. Badges listed on a CV or profile; HR may not open them1. EDC presented via a verifier portal or API; signature and issuer checked
2. No standard link to applicant tracking systems (ATS)2. Degree, EQF level, field, date and institution passed to the ATS as data
3. Regulated roles: official documents requested separately3. Regulated roles: evidence a professional body can rely on where national rules accept it
4. Manual follow-up with the university4. Same procedure whatever the issuing country
Source: Badges guide v1.1 (EUNIS SIG, July 2026), EUPLv2, adapted.

Where badges fall short. Value depends on the platform and on HR knowing the issuer; little weight for regulated professions. Good for being seen, weak for being verified.

What EDC adds. Fast, automatable checks and tamper evidence instead of trust in a PDF or image.

Key takeaways

  • A badge image on a CV is easy to copy. Signed credentials (EDC or Open Badges 3.0) make tampering detectable, and EDC adds a registered issuer.
  • HR’s bottleneck is verifying qualifications, not seeing them. Badges help people see; EDC helps them verify, which is where cost and risk sit.
  • ATS ingestion needs predictable data; ELM provides it, badge metadata varies too much.

Value for alliances: Alliance graduates with EDC diplomas can be verified by employers anywhere in the EU that have verifier software, without contacting the university.

A.7 Alliance-internal recognition and skills portfolio

A student spends two years across several partners of a European university alliance, which wants the whole path recognised and portable, as formal credit and as visible skills.

Open BadgesEuropean Digital Credentials
1. Each partner issues its own badges in its own format1. Alliance agrees shared EDC profiles: common ELM fields, QA references, EQF alignment
2. Badges collected in a personal portfolio, not aggregated2. Partners issue to the profile; the coordination office verifies and aggregates automatically
3. Outsiders interpret each badge on its own3. Outsiders verify any credential, or the whole path as a structured portfolio
4. Skills visible, but no route to formal credit4. Optional badges derived from the EDCs for sharing
Source: Badges guide v1.1 (EUNIS SIG, July 2026), EUPLv2, adapted.

Where badges fall short. Five partners’ badges stay five separate claims. CLR 2.0 can bundle them into one record, but without shared European semantics the aggregation stays largely presentational. Badges do support engagement inside the alliance community.

What EDC adds. A common trust and data layer, formal credit accumulation and a portable record, with badges issued from the authoritative EDC.

Key takeaways

  • Badges make an alliance visible; shared EDC profiles make learning at one partner count at the others.
  • Skills visibility survives: badges derived from EDCs serve CVs and profiles, so the student gets both (see the Combination model).

Value for alliances: This is the core alliance case. A shared trust framework integrates partners academically; separate badge systems behind one website do not.

Key points

  • Map each institutional case to the nearest scenario, then confirm the choice with the Decision framework.
  • Where recognition, credit, admissions or verification by strangers is at stake, every scenario points to EDC.
  • Badges stay the right tool for visibility and engagement, ideally derived from the EDC (see the Combination model).
  • Open Badges 3.0 removes the dependence on a hosted assertion, but not the gaps in shared semantics, accredited issuers and legal standing.
  • An EDC reaches an EUDI Wallet today only where the national wallet supports W3C VCDM; qualified attestations travel as SD-JWT VC or mdoc. Check the national wallet roadmap before planning wallet delivery (see EUDI Wallet).
  • For alliances, shared EDC profiles are what turn several partners’ credentials into one learning record.

← Decision framework  ·  Higher education  ·  Combination model →