SETTING GLOBAL STANDARDS FOR TRUSTED AI CREDENTIALSAI Competence Framework v1.29 · current release
Commentary

Verifying AI output is a competence, and almost nobody teaches it

Courses teach people to produce output and stop there. The competence that determines whether the output is usable is left to be picked up on the job, if at all.

This is commentary. It comes out of reading course syllabuses while drafting D6, and the pattern was consistent enough to be worth stating plainly.

Almost every course we looked at teaches production: how to get output, how to get better output, how to get output faster. Almost none teaches verification: how to establish, before relying on it, whether the output is correct for the purpose. The syllabus ends at the point where the professional obligation begins.

Why the gap persists

Production is demonstrable and satisfying to teach. Verification is slow, produces no artefact the learner can show, and frequently concludes that the impressive output from the previous module should not be used. It is a harder sell and a less pleasant lesson.

It is also the competence that separates someone who can be trusted with an AI system from someone who cannot. Fluent, confident and wrong is the characteristic failure mode of these tools, and the whole of D6 L1 exists to establish that a person recognises it.

What a course could do about it cheaply

Give learners output that is wrong in ways they must detect, with criteria to apply, and mark them on the detection rather than the production. Require the evaluation record, not the verdict. Assess at least one statement about documenting a judgement so that another person can reproduce it, because a verification nobody can reproduce is an opinion.

None of that requires new tooling or a longer course. It requires deciding that the learner’s ability to distrust the output is part of what the credential asserts.

What this article discusses

Framework material referenced

These links run one way. The article points at the specification; the specification does not cite the article as guidance.

D6Evaluation and assurance
D6.L1.01Describe why AI output requires evaluation before it is relied upon.
D6.L1.02Distinguish a system that has been demonstrated from one that has been evaluated.
D6.L2.01Apply defined acceptance criteria to judge whether an AI output meets a stated requirement.

Discusses framework version 0.1 · the article itself carries no version

Revision history

No revision since publication

22.08.2026First published.

A notice is never edited. An article may be, and every substantive change appears above with the date it was made.

The author

Sofia Lindqvist

Editorial lead, D6 Evaluation and assurance

Leads the editorial group for D6 and drafted the twenty-two statements entered at version 0.1, with two technical reviewers per statement.

Works in assurance outside this organisation; that employment is declared below because a reader is entitled to know whose practice shaped the wording.

Declared interests, in full
Osei Assurance PartnersDeclared

Employed as lead assurance consultant. Osei Assurance Partners neither awards nor delivers credentials against this framework and holds no listing on the register.

AI Certification StandardsDeclared

Unpaid appointment to the editorial group. No economic interest.

Cite this article

Sofia Lindqvist (2026) “Verifying AI output is a competence, and almost nobody teaches it”, Commentary, AI Certification Standards. Non-normative. Available at aicertificationstandards.org/articles/verifying-output-is-a-competence (accessed date).

Cite the article as an article. If you need to cite the competence itself, cite the statement: a credential specification or coverage map should reference statement identifiers, never this page.

Article last updated 22.08.2026 · page last reviewed 30.08.2026 · non-normative, not part of any framework version