Six recommendations for any institution adopting digital credentials, whether in higher education, public services, health or workforce mobility. They draw on the Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education, and the VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC, and are listed in the order an institution tends to meet them.
- Governance before technology, every time. Before a platform, standard or wallet vendor is chosen, settle what each credential means for your institution: what it must contain, on what legal basis, and what value it carries. Name the legal entity, the awarding authority, the quality assurance framework and the GDPR data controller. Then review the internal regulations, workflows and policies written with paper documents in mind, and find those that block or complicate digital issuance without anyone intending it. No technology makes up for an undefined issuing authority, and governance is very hard to fit around a platform that is already in place.
- Clarify the purpose, then characterise the credential, before comparing formats. The useful question is not “which format?” but “what must this recognition achieve, and for whom?”. Once that is clear, describe each credential type on five dimensions: how long it must live, who will rely on it, how much meaning it carries, how complex its status is (revocation, suspension), and how much regulation applies to it. The format follows from those answers; see Choosing a stack. The common mistake is extending whatever worked in a pilot to every credential.
- Where regulation applies, let it decide. For microcredentials, define outcomes, assessment criteria and the quality assurance reference first, as the EU Council Recommendation (2022) requires; the pedagogical layer cannot be added afterwards. Inside the scope of eIDAS 2.0 and the GDPR, properties such as unlinkability, data protection by design and the ability to suspend are obligations the institution already carries, not criteria to trade against ease of integration in a scoring matrix.
- Get the Member State wallet roadmap in writing. Holders will keep what their national EUDI Wallet supports. Ask formally for the committed roadmap on credential formats and proof suites, and treat it as a versioned planning input rather than something heard at a conference. Today the binding wallet formats are SD-JWT VC and mdoc; see EUDI Wallet.
- Design for the credential’s lifetime, not its issuance. Ask every credential project what happens to everything already issued when the signing algorithm is deprecated. If the answer is a reissuance campaign, put a cost on it in the business case. See Credential lifecycle.
- Plan two lanes, from one record. Most institutions will end up running two lanes: a fast one for simple attestations issued in volume and needed for a short time, and a formal one for regulated credentials that must last for decades. Budget and govern for both from the start, and build processes that can produce more than one output format from the same underlying record, so that no class of credential is forced into a container that does not fit it.
For the higher-education detail, including Open Badges adoption, the choice between EDC lineages and the recommendations on choosing a credential format, see HE recommendations.
