HCD.8:4.6 - Run an Operating Test

Observe the intended provider or environment deliver the contribution on a representative but safely bounded case. Preserve:

1. the provider, recipient, task, configuration, support, and direct owners;
2. the input, output, criteria, protected errors, timing, volume, handoffs, and access conditions;
3. the first operating result, any disagreement or failure, feedback, correction, and repeated result;
4. actual load, latency, escalation, fallback, and consequences; and
5. the exact claim supported, its limits, and the smallest change that reopens it.

A rehearsal against the same memorized example may show procedural compliance but not handling of the required variation. Use a new representative case when the provider must discriminate, adapt, or resolve a dispute. Test the intended support configuration; require unsupported performance only when the provider’s actual task needs it.

An operating test supports a bounded provider or environment contribution. It does not establish that learners received it, learned from it, transferred it to later Work, or retained capability. It also does not make the whole organization, platform, or programme operational when only one contribution was tested.