Test after an instruction change: preserve the version, questions, and result

Give the source and every release an identity

Separate the document's stable identifier from its release number. The stable identifier joins the history, while the release points to the exact content effective at a given time.

Record publication, effective date, owner and change reason. A version number alone does not explain whether the revision affected how work is performed.

Do not edit published material in place

Training material should have its own release connected to the source. A correction after publication creates a new release rather than silently changing content underneath existing confirmations.

Knowledge questions also belong to the release. A result then retains meaning even when a later check has a different scope or threshold.

• stable document identifier
• source release number and date
• training material version
• question set version and threshold
• confirmations assigned to that release

Make an explicit retraining decision

A new release does not need to invalidate every earlier confirmation automatically. The owner should assess impact and decide which groups require another assignment.

Record the rationale, group, deadline and effect on previous validity. This avoids both excessive retraining and leaving a material change without action.

Test the change, not general recall

Questions should check the activities, decisions, or risks changed in the new release. A generic definition quiz may score well while failing to show that a person understands the new way of working.

Record the question-set version, threshold, attempt limit, and action after failure. The result must point to the exact instruction release and the person who approved the test scope.