CDLA · Module 3 — Outcomes and authentic assessment
Align each observable action to a claim, evidence, format, LTEM tier and signer before you author.
About 22 min
Practice in the lesson player
Sorting, matching, quizzes, and the module gate stay behind a free account so scored answers are not public. The teaching notes below are the same cited curriculum.
01
From Module 1 you have observable actions; from lesson 2 you have claims. Now add columns: the evidence you will accept, the activity format, the LTEM tier you are claiming, and who signs off. This table is what sponsors and subject-matter experts review, not a slide count.
02
Action | Claim | Evidence | Format | Tier | Signer
Isolate the machine before maintenance | Technician can isolate a press safely | Correct sequence in under 90 seconds; observed once on site | Order activity and timed simulation; site checklist | 6, then 7 | Safety lead
Refuse an unsafe verbal instruction | Technician escalates instead of complying | Chooses escalation in 2 of 2 branching cases | Branching dialogue | 5 | Operations manager
Report a near miss | Technician reports within the shift | Near-miss reports per team, before and after | Operational data | 7 to 8 | HSE manager
03
Criterion situation: The real context where performance must happen.
Claim: What you will say about the learner if the evidence is met.
Summative gate: A scored checkpoint that unlocks a credential.
Formative check: Practice with feedback; does not affect a credential.
04
A gate cannot test every action. Build a blueprint: list the actions, give each a weight by risk and frequency, and allocate items in proportion. A ten-item gate for a module with five actions might give four items to the highest-risk action and one or two to the others. Publish the blueprint to reviewers. It is the strongest evidence you can offer that the gate samples the job, and it lets you add items later without changing what the certificate means.
05
Turn your three claims into a full assessment map with all six columns. Add a gate blueprint: how many items per action and why. Ask the signer named in each row to confirm they will sign. This is the core of your module artifact.