How to create a certification programme: criteria first
How to create a certification programme: write the criteria down first, issue only on a signed result, and record every revocation and re-issue.
How to create a certification programme comes down to an order of work: write down what earns the credential, assess against it, have a named educator sign every result, and issue only on a signed result. Most guides treat the credential as the last design task. This one is for exam officers at certification bodies and the programme directors who sign off their rules, and it starts where defensibility starts: with criteria written down before the first sitting. Everything issued afterwards points back to them.
How to create a certification programme in seven steps
Seven steps, and the first one decides whether the last one holds up when someone asks how a credential was earned.
- Define what earns the credential, in writing, in the system.
- Author items against a rubric, with a named approver on every item.
- Build comparable forms from item banking with calibration statistics.
- Match the integrity controls to the stakes, one explicit choice at a time.
- Have a named educator review and sign every result.
- Issue the credential on the signed result, from your own template.
- Keep the credential current: verification, revocation, re-issue, validity.
Steps two to five are the assessment itself, and each has its own pillar on NUADU. Steps one, six and seven turn a passed exam into a credential that means something outside the exam room. They are also the steps most often left implicit: the definition held in a regulations document, the issuance done by hand, the correction done by email.
The Certification path states the stakes in one sentence: high-stakes certification lives or dies on defensibility — evidenced item quality, documented marker agreement, proportionate integrity measures, and a record of who decided what and when. The rest of this guide covers the three steps that decide where that record starts and how it ends.
What are certification criteria?
Certification criteria are the written conditions a candidate must meet before a credential is issued: the definition of what the credential means. On NUADU they are the first step in Certify, the pillar for verifiable certificates, and they are set in the system before anything is issued. They come in four shapes:
- Simple thresholds — the Certify page's own example is "score ≥ 80%".
- Composite criteria — "pass all + integrity", in the page's words.
- Competency-based requirements — tied to demonstrated competencies, not one total.
- Time-based validity — a credential that holds for a defined period.
Ask a certification body what a candidate must do and the answer comes quickly. Ask where it is written and it is often in three places at once: the regulations document, the exam officer's spreadsheet, and the memory of whoever ran the last session. The three usually agree. The gap shows when a result is challenged and someone has to reconstruct which rule applied.
Writing the criteria into the system changes two things. The rule is the same for every candidate in every session, because NUADU applies the rule the exam officer set rather than the one someone remembers. And the rule is visible before the first credential exists, which is when a reviewer should see it.
A licensing body that certifies practitioners every year might set a composite rule for the written exam, a competency rule for the practical component, and a validity period that matches its own regulations. Each is a programme decision. NUADU records it and applies it; it does not make it.
Write the criteria down before the first sitting, not during the first appeal.
How is the passing score for a certification exam determined?
By the programme, not by the platform. A cut score is the point on the score scale that separates a pass from a fail, and deciding where it sits is a judgement your programme and its subject experts make and document. NUADU records the outcome of that judgement as a criterion before the sitting and applies it to every signed result.
If you are asking how to determine a passing score, the useful answer is about ownership. The method belongs to the programme, and the decision should be written down in the same place as the rest of the criteria. What a platform can do is narrower: hold the threshold, apply it the same way in every session, and show on each credential which criteria were met.
A threshold is rarely the whole rule. A composite criterion adds conditions to the score, such as every component passed plus integrity. A competency-based requirement may replace a single total altogether. And where candidates sit different forms, a passing score means the same thing across them only if the forms are comparable. That is why parallel forms on NUADU come from a bank with calibration statistics and use equating logic, so difficulty stays comparable from one form to the next.
Issue on the signature, not on the score
A credential is issued automatically once the result is signed, and the signature belongs to a named educator. A score on its own triggers nothing. The marker reviews, overrides where the rubric requires it and signs off, which is the sign-off described under rubric marking; only then is the signed result checked against the criteria.
This is where "automatic" and "defensible" stop pulling against each other. Issuance is automatic in the sense that nobody re-keys a result into a certificate template. It is defensible because what gets checked against the criteria is a reviewed, signed result with a named person behind it. Where AI assistance is switched on in marking, it drafts scores for essays and speaking; the marker still reviews, overrides and signs off before anything is issued.
The credential then carries what earned it — the criteria met, the assessments completed and the integrity controls used — which is the practical difference between a certificate and a credential. The template is your institution's: logo, colours, authorised signatories and credential fields, reusable and versioned, so this year's credential can be told apart from last year's. Each credential can then be checked by URL or QR code; what the person checking it sees is covered in QR code verification for certificates.
What happens when a certificate is revoked?
It is withdrawn, and the withdrawal is part of the record. NUADU supports revocation and re-issuance, with the change recorded in the audit trail, so whoever reads the file later sees the correction as well as the original.
Results are overturned on appeal. A credential is issued in error. Criteria change between sessions. In each case the record keeps what was revoked and what replaced it. When a candidate contests a result, that history, the criteria and the signed result are what the exam appeals process works through.
Time-based validity works the same way. The validity period is part of the criteria, written down with the rest. What happens when it ends is your programme's policy; the platform's job is to have recorded the period in the first place.
One boundary belongs in every certification conversation. NUADU is the platform on which exams are authored, delivered, marked and reported. It does not issue state-recognised certificates. The credential is issued by your institution, under your name and your signatories.
Where to start is the first step. If the criteria already exist in a regulations document, the work is translation, not invention. If they exist in three places, the work is reconciliation, and it is easier now than in the middle of a dispute.