Stackable credentials and the team dashboard

Stackable credentials are module credentials that combine into a programme credential. Each layer needs a signed result and its evidence, not a completion tick.

Stackable credentials are module-level credentials that stand on their own and also combine into a larger, programme-level credential. For an L&D lead the useful question is not whether to stack but what each layer proves, because a stack of completion records still only proves completion. The corporate case the Certify page sketches is the alternative: a credential per module, a programme-level credential at completion and a manager view of team certification status; a separate case adds a portfolio the learner controls. Underneath sits one rule: patterns for the team, never automated labels on a named employee.

What are stackable credentials?

A stackable credential is a credential that has value on its own and also counts towards a larger one. Stacking credentials means earning them in sequence, module by module or level by level, so each step is recognised when it is completed and the steps together add up to a qualification.

Most explanations describe a learner's ladder in education: a short certificate first, a larger award later. A workplace programme reads the same idea differently. The holder is an employee, and the readers of the stack are a line manager, an auditor and, one day, the next employer. Each of them asks what the stack proves.

That is where completion fails. A completion record shows that someone finished a module; it does not show what they can do. The Enterprise path puts the alternative in three words — capability, not completion — and a stack built from completion records simply repeats the gap at every level.

A stack of completions is still completion.

What is a stackable credential programme?

A stackable credential programme defines a credential for each module and a credential for the whole programme, each with its own criteria and each issued on a signed result. The Certify page's corporate example is exactly this shape: a programme might issue stackable credentials for each module and a programme-level credential at completion.

Every credential in the stack, module or programme, goes through the same workflow as any of NUADU's verifiable certificates. It is issued once a named approver has signed the result, and it is tied to the evidence behind it: criteria met, assessments completed, integrity controls used. In the Enterprise path's examples, the markers are line managers or internal assessors, and they sign off. Branding is yours too, with logos, colours and branded credentials.

The criteria do the stacking. A module credential might rest on a simple threshold or on competency-based requirements; the programme credential might combine them — every module passed, plus integrity — with a validity period where the role calls for renewal. Which shapes apply is a programme decision, set before the first module credential is issued.

What sits behind each module matters more than the label on top. The assessment behind a module can be a constructed response, a simulation or a spoken response, mapped to your competence framework, so the credential rests on rubric-based evidence rather than a completion record. That is what gives a module credential something to carry.

What are examples of stackable credentials?

In a workplace setting, the clearest examples are programmes built from modules that are each assessed and signed on their own. Three illustrative shapes a programme might use:

  • A role-based capability programme: one credential per competence area, each signed by a line manager or internal assessor.
  • A compliance programme: one credential per regulation-specific module, so a rule change touches one module.
  • A leadership programme: case analysis, presentation and strategic reasoning assessed separately, each with assessor sign-off.

In each, the programme credential is issued at completion and the module credentials remain separate records. How the items behind a compliance module are refreshed when a rule changes is the subject of assessing compliance training after a regulation change.

Module credentials of this kind are sometimes called stackable micro-credentials. The label matters less than the content: each one should say which criteria were met, in which assessments, under which integrity controls, and who signed.

What the manager sees, and what it never shows

Team certification status: who on the team holds which credential, and who does not yet. Manager dashboards show exactly that. It is a status view, not a judgement about a person; the Enterprise page's phrase for the stance is visibility without surveillance.

If you arrived looking for employee certification tracking, this is the narrow version of it. It shows status per credential and makes no forecasts. Where an individual signal does appear, it goes into a development conversation and is never turned into an automated prediction. Skill gaps are surfaced for development planning rather than for automated routing, and named employees are not labelled automatically.

Patterns belong in the aggregate. Per-employee capability profiles feed conversations; team-level patterns feed planning, and the programme-level picture lives in assessment analytics, not in a dashboard about named people.

When a works council or a DPO asks how an employee contests a result, the answers are written down: the documentation pack, the DPIA template, the sub-processor list and the retention policy are prepared for exactly those readers.

The portfolio belongs to the employee

Credentials outlast the job that produced them, so the employee decides who sees them. The Certify page's lifelong portfolio case describes a multi-issuer portfolio with learner-controlled sharing, in which the learner controls who sees which credential. Learner-owned where it should be.

That is one reason a stack is built from separate credentials rather than one summary document. The employee can share the programme credential with one reader and a single module credential with another, and the choice stays with the employee.

Credentials are portable beyond your systems, and a receiving employer can verify one independently, without a NUADU account, using the check described in how to verify a certificate by its QR code. That portability rests on open verifiable-credential standards, chosen per institution, and it is part of what separates a credential from a certificate. A module credential can also be revoked and re-issued, after an overturned result for instance, with the change kept in the audit trail.

A credential that stacks is still a credential: criteria, a named approver and a record behind every layer. The dashboard shows who holds what. The employee decides who else gets to see it.

→ Talk to us about your competence evidence (30 min)