How to map assessment to a unit of competency without leaving gaps
To map assessment to a unit of competency, unpack every requirement (elements, performance criteria, performance evidence, knowledge evidence and assessment conditions), build a matrix with a row for each, then point each row to the specific page that teaches it and the specific task that assesses it. Map to the page and question, never the whole document. Then check that nothing is unassessed and nothing is assessed that proves nothing.
Mapping is where good assessment is won or lost. Done well, it is the fastest way to prove your assessment is complete. Done loosely, it hides the very gaps an auditor is trained to find. Here is a method that holds up.
What does it mean to map assessment to a unit?
Mapping means tracing every component of a unit of competency to the exact place each is taught in the learning content and the exact task that assesses it. The output is a matrix: one row per requirement, columns showing where it is delivered and where evidence is gathered. It is the proof that your assessment covers the whole unit, not just the convenient parts.
A unit of competency is not one requirement; it is many, layered. Before you can map, you have to see them all.
Step 1 — Unpack the unit completely
List every assessable component from the unit, not just the elements. That means the elements and performance criteria, the performance evidence, the knowledge evidence, and the assessment conditions. Each is a separate obligation, and each must be mapped.
| Component | What it requires |
|---|---|
| Elements | The broad tasks that make up the unit. |
| Performance criteria | The specific, observable actions under each element. |
| Performance evidence | What the learner must do to demonstrate skill, often more than once. |
| Knowledge evidence | What the learner must know and understand. |
| Assessment conditions | The environment, resources and supervision assessment must occur under. |
Step 2 — Build the matrix
Create one row for every requirement you unpacked, with at least two columns: where it is taught, and where it is assessed. A third column for the evidence type (knowledge, performance, observation) makes gaps visible at a glance.
Step 3 — Map to the page and the task, never the document
Always reference the specific page, section or question — never the whole document. "Learner Guide" tells an auditor nothing. "Learner Guide p.14, Activity 3" lets them verify coverage in seconds. Precise references are faster to defend and far less likely to conceal a gap.
This is the single biggest difference between mapping that survives an audit and mapping that invites one. Vague references are read as a sign that the coverage was never really checked.
Step 4 — Match the evidence type to the requirement
A performance requirement needs a performance demonstration — you cannot satisfy a "must do" with a written question. Check that each row is assessed in a way that genuinely gathers the right kind of evidence: observation for skills, questioning for knowledge, projects and case studies for applied judgement.
Step 5 — Check for gaps and over-assessment
Confirm two things: every requirement is taught and assessed at least once, and no assessment task exists that proves nothing. Gaps fail the rules of evidence on sufficiency; padding wastes the learner's time and yours. Both are worth cutting.
- Mapping to a whole document instead of a specific page or question.
- Claiming coverage a task does not actually deliver.
- Assessing a performance requirement with knowledge questions only.
- Leaving assessment conditions unmapped and unaddressed.
- Mapping the first draft, then editing the tools and never updating the matrix.
Good mapping is not a document you produce at the end. It is the discipline you build the pack around — and the reason a well-built pack can be picked up and defended on day one.
Let us do the mapping — to the line.
Every Quillon pack is mapped element by element to the training package, so the evidence trail is clear long before an auditor asks for it.
Mapping means tracing every component of a unit — its elements, performance criteria, performance evidence, knowledge evidence and assessment conditions — to the exact place each is taught in the learning content and the exact task that assesses it. The result is a matrix that proves the assessment covers the whole unit.
The most common mistakes are mapping to a whole document instead of a specific page or question, claiming coverage a task does not actually deliver, assessing a requirement only in knowledge questions when it needs a performance demonstration, and leaving assessment conditions unaddressed. Each creates a gap an auditor can find.
Always map to the specific page, section or question, not the whole document. A reference like "Learner Guide" tells an auditor nothing; "Learner Guide p.14, Activity 3" lets them verify coverage in seconds. Precise mapping is faster to defend and far less likely to hide a gap.
Last updated 19 May 2026