Evidence across the process
Distributed assurance
SAGE treats assurance as something that can be distributed across selected points in the learning process and mapped to the learning outcomes that require confirmation.
Rather than assuming that every activity requires the same level or form of verification, distributed assurance asks where meaningful evidence of a particular capability can be gathered as learning develops.
Example: outcome-mapped assurance points
The columns represent selected points in a learning sequence, not a weekly assessment schedule.
| Learning outcome |
Early learning |
Developing |
Later learning |
Confirmation |
| Outcome A |
Corroborative |
Controlled |
Direct |
|
| Outcome B |
|
Corroborative |
|
Direct |
| Outcome C |
|
|
Controlled |
Direct |
Corroborative evidence Supports the evidentiary picture
Controlled condition Strengthens attribution
Direct assurance task Directly elicits capability
The assurance class describes the function contributed by an activity, not a fixed property of its format. The same format may provide corroborative evidence, strengthen controlled conditions, or directly elicit observable reasoning depending on how it is designed.
For example, a presentation may provide process evidence, operate under controlled conditions, or become a direct assurance task through individual learning-outcome-mapped questioning.
Three assurance functions
Corroborative evidence
SAGE AI records, source trails, accept–modify–reject decisions, portfolio or version histories and reflections make judgement more visible. They strengthen the evidentiary picture but do not alone confirm independent capability.
Controlled assurance conditions
Supervision, restricted computing environments, identity verification, controlled windows, personalised variants or supervised partial completion strengthen attribution. The condition is not the capability; the evidence produced remains what matters.
Direct assurance tasks
Interactive oral assessment, outcome-mapped questioning, practical demonstration, supervised challenge, scenario defence or live walkthrough and debugging can directly elicit capability. Defend is the SAGE design principle for this function, not a prescribed format.
Assurance is mapped, not repeated everywhere
Selected assurance points can be positioned across an assessment sequence, unit or course. A learning outcome may accumulate corroborative evidence at one point, encounter controlled conditions at another, and be directly demonstrated where stronger confirmation is warranted.
Learning outcome→
Selected assurance points→
Appropriate assurance function→
Sufficient evidence of capability
A blank assurance point simply means that the learning outcome is not being targeted for assurance at that point. It does not imply that the learning activity has no pedagogical value.
Why distribute assurance?
When assurance is concentrated in a small number of high-weight events, evidence of capability is correspondingly concentrated. Distributed assurance provides an alternative architecture in which appropriate evidence is gathered at selected points as learning develops.
The objective is not to maximise surveillance or assessment events. It is to build sufficient, proportionate and learning-outcome-aligned evidence of capability across the learning process.
SAGE principle: distribute assurance according to the learning outcomes, distinguish the function of different evidence, and directly elicit capability where stronger confirmation is required.