Twelve recommendations for universities, in two lists. The first covers what to issue: badges, EDC, or both. It follows the six recommendations of the Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education, in their original order. The second covers which technical format to issue it in, following the six recommendations of the VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC. Items marked also cross-sector appear in general form among the cross-sector recommendations.
Choosing what to issue
- Clarify purpose before format. Do not ask “badge or EDC?” first. Ask what the recognition has to achieve, and for whom; the format follows from that answer. See Decision framework. Also cross-sector.
- Do not wait for EDC infrastructure to be fully mature before acting on Open Badges. They solve different problems, and the Open Badge ecosystem is ready for production today. Waiting conflates two independent workstreams.
- Align with the EU Council Recommendation before choosing a platform. If you plan to issue microcredentials, define learning outcomes, assessment criteria and the QA reference first. The pedagogical layer cannot be added afterwards. Also cross-sector.
- Choose your EDC lineage deliberately. Europass/EDCI is in production today. The DC4EU/EBSI lineage is built for wallet delivery, but its pilot concluded in 2025 and EUDI Wallet support for W3C VCDM in education is foreseen rather than binding (see EUDI Wallet). Know which data transfer model (LE→NP, LE→LE, LE→NP→LE) your primary use case requires before selecting technical architecture.
- Plan for both formats from the same learning record. The institutions best positioned in the medium term will be those that build processes capable of outputting either format. Avoid architecture decisions that create lock-in to a single output format. Also cross-sector.
- Governance before technology, every time. Before choosing any platform or standard, set down what a credential means in your institution: its required content, legal basis and academic value. Review the internal regulations, workflows and policies written on the assumption of paper certificates, and identify those that block or complicate digital issuance. Define the legal entity, awarding authority, QA framework and GDPR controller. Governance cannot be fitted around a platform after the fact. Also cross-sector.
Choosing the format
- Governance before technology, every time. For each credential, settle its legal basis, awarding authority, QA reference and GDPR controller before any format is chosen. This avoids the institution that picks a wallet vendor first and only then finds that nobody has decided who may issue what in its name. Also cross-sector.
- Characterise the credential before comparing the formats. Describe every credential type in the portfolio by lifespan, audience, semantic density, status complexity and regulatory exposure before any format conversation starts (see Choosing a stack). The most common error is extending the pilot stack to the diploma because the pilot went well. Also cross-sector.
- Anchor the decision to your Member State wallet, in writing. Students will hold what the national EUDI Wallet supports. Ask formally for your Member State’s committed roadmap for credential formats and proof suites, and treat it as a versioned planning input, not as something heard at a conference. Also cross-sector.
- Plan for two lanes, not one winner. Most universities will run both stacks: a fast lane (SD-JWT VC) for high-volume, short-lived, semantically light credentials and a formal lane (W3C-VC) for long-lived, regulated ones. Budget, staff and govern for both from the start; a single winner-takes-all choice leaves one class of credential in a format that does not fit it. Also cross-sector.
- Design for the credential’s lifetime, not its issuance. Require every project to state in writing what happens to the credentials already issued when the signing algorithm is deprecated. If the answer is a reissuance campaign, put a figure on it in the business case (see Credential lifecycle). Also cross-sector.
- Where the use case is regulated, let the regulation decide. Inside the perimeter of eIDAS 2.0 and the GDPR, properties such as unlinkability, data protection by design, demonstrable accountability and suspension are obligations the institution already carries, not criteria to be traded off against ease of integration in a scoring matrix. Weight the decision towards the stack that meets them as properties of the format. Regulation also decides what the EUDI Wallet must accept: today SD-JWT VC and mdoc (see EUDI Wallet). Also cross-sector.
← Implications by function · Higher education · EAA catalogue →
