I’ve been involved in quite a few conversations recently about micro-credential frameworks, quality assurance and how we decide what should be recognised. Some have been through my work with the Commonwealth of Learning, particularly in Mauritius, where the Higher Education Commission now has an approved framework for recognising higher education micro-credentials. Similar questions have come up during a regional workshop with the South African Qualifications Authority (SAQA), where we explored what a national approach might look like, and in conversations with colleagues in the Australasian Micro-credential Network.
One of the questions that kept coming up was who should actually be allowed to issue a micro-credential. Should it only be universities and registered training providers? Should industry and professional associations be included? What about private training companies or employers issuing credentials for their own workforce? And if we establish a national definition, what happens to everything that doesn’t meet it?
I found myself challenging the idea that we could decide who was allowed to use the term “micro-credential”.
One example I used was an international company offering micro-credentials in South Africa. If someone has a micro-credential issued by an overseas provider, we can’t necessarily tell them it isn’t a micro-credential simply because it doesn’t meet the requirements of the South African system. We can say it isn’t recognised within a particular national framework, or that it doesn’t meet the requirements for a particular type of approval. But that’s quite different from saying it isn’t a micro-credential at all.
What exactly are we trying to regulate?
We already distinguish between different kinds of learning and qualifications. In Australia, for example, you can’t simply decide to start issuing bachelor’s or master’s degrees. There are regulatory requirements around who can award those qualifications, and the qualifications themselves have to meet established standards.
But we also have masterclasses and master series. Nobody assumes that attending a masterclass gives you a master’s degree. We understand that a formal qualification carries a particular status because of the accreditation and recognition behind it.
So where do micro-credentials fit?
Universities are developing credit-bearing micro-credentials, industry bodies are recognising occupational capabilities, employers are issuing credentials for workplace learning, and private providers are offering all sorts of short courses and assessments. Some carry academic credit, some have professional recognition, and others are primarily valuable within a particular organisation or industry. So I’m not sure they all need to fit within the same regulatory arrangements.
There’s also a distinction that I think gets lost in these discussions, and that’s the difference between a micro-credential and a digital credential. A digital credential is a way of representing and communicating a claim. That claim might be about a degree, a short course, a professional certification or a workplace capability. The fact that it’s digital doesn’t tell us whether the learning was accredited, how it was assessed or what recognition it carries.
We could issue a bachelor’s degree as a digital credential, just as we could issue a badge recognising someone’s contribution to a community project. The technology can support both, but they’re making very different claims.
What about organic food?
This might seem like an odd comparison, but I’ve been thinking about how certification works in other areas.
Take organic food. In Australia, a producer can describe something as organic, provided they can substantiate the claim, without necessarily having it formally certified for the domestic market. But if they want to use a recognised certified organic mark, they need to meet the requirements of that certification scheme.
The certification tells us something additional. It identifies a set of standards and an organisation responsible for assessing whether those standards have been met.

We see something similar with the Australian Made logo. A manufacturer can’t simply add it to a product because they think it looks Australian. There are criteria governing its use, and the mark communicates a particular claim about the product’s origin.
Neither mark tells us everything about the product. Certified organic doesn’t necessarily mean the food tastes better, and Australian Made doesn’t tell us whether something is good value. But they do tell us something specific that we can check.
And I wonder whether we could think about micro-credentials in a similar way.
What we’re doing in Mauritius
This is quite close to the approach of the Higher Education Commission in Mauritius, where the framework for approving and recognising higher education micro-credentials is now operating.
The framework establishes standards against which micro-credentials can be assessed. Those standards are publicly available, so all stakeholders can understand what’s expected, and the intention is that approved micro-credentials will be identifiable through the HEC recognition arrangements and repository.
That doesn’t mean someone else in Mauritius couldn’t offer a short course and call it a micro-credential. But it wouldn’t become an HEC-approved micro-credential or be included in the repository without going through the approval and recognition process.
I think that’s an important distinction. The approval establishes what the recognition means, what standards have been met and who is standing behind that decision.
But what about a micro-credential developed by the mining industry to recognise a workplace capability? Or one issued by a professional association in finance? Would we expect those to meet exactly the same requirements as a credit-bearing university micro-credential?
Different purposes, different kinds of recognition?
If a micro-credential is intended to carry academic credit and contribute towards a formal qualification, then we need enough consistency for another institution to understand what the learner has achieved. Learning outcomes, assessment, level, volume of learning and credit arrangements all become important. And if we want learners to move between institutions, we need some common approaches, even if individual institutions still make their own credit decisions.
But in an industry setting, the requirements might be different. A mining company or industry association might be far more interested in whether someone can safely and competently perform a particular task, and whether the assessment reflects actual workplace conditions. The credential might be highly valued within that industry without ever being intended to carry university credit.
Of course, some credentials might sit across more than one setting. An industry credential could also be recognised for academic credit if it met the relevant requirements.
So perhaps we need different forms of approval for different purposes, rather than one universal standard that every micro-credential must meet.
That raises another question. If different organisations establish their own approval or certification schemes, how do we know which organisations to trust? Who assesses the assessors? Do we need some common principles for how these schemes operate, even if the standards they apply to individual credentials are different?
And where do digital credentials fit?
This is where I think digital credentials could become particularly useful.
We already have technical standards that allow digital credentials to carry structured information about the issuer, the achievement, the criteria and, where relevant, the evidence behind it. But verifying that a credential was issued by a particular organisation isn’t the same as knowing whether that organisation is authorised, accredited or recognised for the purpose being claimed. Could we do more to make that additional layer of recognition visible?
Could a credential carry verifiable information showing that the learning has been approved by a national quality assurance body, recognised by a professional association or accepted within an industry certification scheme? And could someone looking at that credential find out what the approval actually means, rather than simply seeing another logo or tick?
There are complications, of course. Recognition can change, approvals can expire or be withdrawn, and different bodies might recognise different aspects of the same credential. But I think there’s something worth exploring here.
Can we actually standardise trust?
I’m not sure trust itself is something we can standardise, at least not in any universal sense.
A credential that’s highly trusted within the mining industry might have very little meaning to a university admissions officer. A university micro-credential might meet rigorous academic standards and carry credit, but that doesn’t necessarily mean an employer will value it.
So when we say we want trusted micro-credentials, perhaps we need to be more specific. Trusted by whom? For what purpose? And what is that trust based on?
I keep coming back to the food certification example. We have different standards and certification arrangements for different purposes, whether that’s organic production, food safety or country of origin. Each tells us something different about the product. We don’t expect one certification to cover everything, but we do need to understand what each certification means, who is responsible for it and what standards have been met.
Perhaps something similar could work for micro-credentials. Different recognition arrangements for different purposes, with common ways of communicating what has been approved, against which standards and by whom. And perhaps the digital credential becomes the vehicle for carrying that information, rather than being confused with the recognition itself.
I’m still working through what this might look like, particularly how we avoid creating another complicated collection of labels and approval schemes that nobody understands.
But the more conversations I have about national micro-credential frameworks, the more I wonder whether we’re spending too much time trying to decide who can use the term “micro-credential”, and not enough time thinking about what we actually want people to be able to trust.
Maybe the question isn’t who gets to call something a micro-credential. Maybe it’s who gets to say it’s approved, and what that approval actually means.


